Open gauravbhosale opened 3 years ago
I don't see anything suspicious. Do you see any error messages if you run with --verbose
?
i think is just the noise, its not correctly indent.
I can not test this world right now but from what I see this is not 360 coverage if this what you mean by velodyne 3D.
Also the update rate is kind of high, not to mention it is not gpy_ray. Which also make it suspicious with the collision you are using in the model.
I can not say why it would crash but it would be better to have it right to make sure it is not your model issue!
Try to reduce the update rate, and reduce the size of the collision to something like
Hi,
I am able to resolve this issue. To resolve this issue, 1] I need to update Gazebo to latest version 2] I need to change VM setting and increase RAM to 4 GB ( previously it was 2 GB)
This means, when I use Velodyne sensor, the VM should have 4GB RAM. Is this make sense? Is Gazebo needs 4 GB RAM always?
comparing
Hi,
When I run attached world file as 'gazebo velodyneSensorTest.world --verbose', Gazebo 9.16 waits for some time and crashes after few seconds. Is there anything wrong in .world file? I have attached '.txt' version as unable to load '.world' file. Please change extension and try to reproduce the issue.
velodyneSensorTest.txt