search

gazebosim / gazebo-classic

Gazebo classic. For the latest version, see https://github.com/gazebosim/gz-sim
http://classic.gazebosim.org/
Other
1.17k stars 477 forks source link

Lights not rendered for same scene on GPUs, working on CPUs though #2693

Open osrf-migration opened 4 years ago

osrf-migration commented 4 years ago

Original report (archived issue) by Sam Gundry (Bitbucket: Sam Gundry).

The original report had attachments: image002.png, image001.png

Reproduce:

  1. Use the small house world scene: https://github.com/aws-robotics/aws-robomaker-small-house-world
  2. Load the scene in Gazebo 9 on a computer WITH a dedicated GPU and observed there are NO lights rendered
  3. Load the scene in Gazebo 9 on a computer WITHOUT a dedicated GPU and observed there are ARE lights rendered

See images attached.

image001.png: lights on the wall are not working when using a GPU

image002.png: lights on the wall are turned on when not using a GPU

‌

‌

osrf-migration commented 4 years ago

Original comment by Sam Gundry (Bitbucket: Sam Gundry).

zark-zeugan commented 3 years ago

I would like to work on this how can I get started?

peci1 commented 3 years ago

@zark-zeugan You can try replicating this issue first on a machine with NVidia GPU and on a machine with Intel GPU only.

zark-zeugan commented 3 years ago

I use a system with NVIDIA 1050Ti and and an Intel i5 processor. With Ubuntu 18.04 dual boot and have already installed ros melodic hope that is sufficient to recreate it.

zark-zeugan commented 3 years ago

I have loaded the scene onto my system and using the dedicated graphics I see that the lights have rendered. Here is how it looks

peci1 commented 3 years ago

Is it Gazebo 9, right?

zark-zeugan commented 3 years ago

@peci1 Yes it is Gazebo 9. Any other way I could try?

peci1 commented 3 years ago

It would be beneficial to try to find and contact the original issue reporter. But it could be difficult because the bug was moved here from bitbucket...

As the world is a part of AWS robomaker, it might also be interesting to know it the original reporter ran the Gazebo locally or in the AWS cloud. Or if you had a chance of testing it in AWS (which might cost some money).

This issue might as well be GPU-specific. The reporter did not unfortunately mention which kind of GPU he used. I see you're testing on NVidia. I can give it a test on AMD Renoir GPU later today.

peci1 commented 3 years ago

default_gzclient_camera(1)-2021-04-05T18_33_40 379061

with Gazebo 9.16.0 binary build and

$ glxinfo | grep -i opengl
OpenGL vendor string: AMD
OpenGL renderer string: AMD RENOIR (DRM 3.40.0, 5.11.11-051111-generic, LLVM 11.0.1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.0.1 - kisak-mesa PPA
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.1 - kisak-mesa PPA
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.0.1 - kisak-mesa PPA
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions: