-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RgbdCameraSensorTest.ImagesWithBuiltinSDF/ogre2 failure on macOS #67
Comments
I added the following code to the test to save a received image to a png file to help debug the macOS failure:
Image from successful Linux testImage from unsuccessful macOS test |
here's the ogre2.log file from macOS: rgbd_macos_ogre2.log |
I'm comparing the ogre2 log from macOS with a log from a successful run on my Linux machine the following line appears in both logs:
but the following lines appear only on macOS:
|
That looks suspicious. The shaders with name that starts with numbers are dynamically generated by ogre. Setting this line of code in ign-rendering to (true, true), will tell ogre to write the shaders out to file on disk (I think it'll be written to where the executable is run). If you have time, can you give that a try that and share the generated shader files and ogre2.log? |
|
This suspiciously sounds like gazebosim/gz-rendering#332 which has been fixed now. Can you check if it has been fixed now with latest ign-rendering5?
Although that sounds suspicious, unfortunately that warning is very common. I never looked deep into this problem, what I think happens is that Ogre assigns 0 to all samplers because our param buffers haven't been initialized yet, calls some GL functions (and some GL drivers warn about this problem at this point), then the params get initialized with correct values and now the shader is actually used. If the GL driver validates too early, the warning appears. But 99% of the time it's a meaningless warning. |
Several tests on macOS were failing to load the
ignition-rendering*-ogre2
plugin (#62), which has been fixed, but now the RgbdCameraSensorTest.ImagesWithBuiltinSDF/ogre2 test is failing:The text was updated successfully, but these errors were encountered: