Object visible with a camera but invisible in the 3D World

[ahcorde]

Porting the ros_ign_gazebo_demos I found this issue. The cone is visible with the camera but it's invisible in the 3D world.

I'm compiling from source dome.

@iche033 or @chapulina any thoughts?

[iche033]

Not sure. The world is sensors_demo.sdf from ign-gazebo right? I just tested that world in ign-gazebo2, 3, 4 but the cone is shown in both 3d window and sensors. Is it visible for you if you just launch the world using ign instead of ros2?

[mcres]

I am facing the same problem in Ubuntu 18.04 after installing dome from source and launching the world with ign gazebo.

I've also tried to launch some more models and it happens exactly the same. It seems that meshes in .obj like this one will work, but .dae or .stl like this one won't. This happens as well with models from YCB, where those formats are available for the same downloaded object.

[chapulina]

I can't reproduce this issue using ros_ign_gazebo_demos with:

• Ubuntu Focal (Docker)
• Either Citadel from debs or Dome from source
• Foxy from debs

Do you see any errors / warnings when running verbose?

Also, when you expand the "Construction" entity on the tree, does it show that it has a visual?

[mcres]

I don't see any errors or warnings related. The Construction entity does have a visual in the tree, but I can't see any difference between visuals of the different models when using the Component Inspector.

[ahcorde]

Using this env variable fix the issue

export LC_NUMERIC="C"

can you confirm this @mcres ?

[chapulina]

export LC_NUMERIC="C"

Ohhhh locales strike back! Nice catch!

[ahcorde]

should we need to add any reference to this issue in the installation guide or the troubleshooting sections?

[chapulina]

I think we should be able to fix this programmatically. Were you able to pin-point the place where the locale made a difference? Is is when parsing the COLLADA files, when loading them into rendering...?