Gazebo Ignition fails to render scene in Ubuntu VM (using ogre2 = black screen) (using ogre = flickering of scene 1Hz) #1492
Comments
|
When I built the GARDEN version from source the flickering did disappear on the ogre version. However, the black screen remained when I used the ogre2 configuration.
|
|
Hi @marc-wittwer, I suspect this is similar to #1116. It has to do with the level of OpenGL support offered by the hypervisor running the VM (rather than what Ubuntu tells you it has when running glxinfo or similar). You can switch to software rendering (v. slow), and for ogre (1) there are some MESA settings you can adjust to remove the flickering, and it's a bit of trial and error depending upon your machine / OS etc. |
|
@srmainwaring Thanks for your reply. #1116 led me to this link: https://answers.gazebosim.org//question/27244/ignition-flashing-image-cant-quit/ |
|
I had a similar problem and I got it solved after disabling Anti-Aliasing, as suggested on #1116 (comment) |
|
Disabling accelereted 3D graphics in the VMWare settings, solved the flickering. I still have to run the
|
|
According to your output VMWare supports GL 4.1 Although Ogre2 only requires OGL >= 3.3 we do depend on a couple of extensions that were introduced later on and backported to those drivers. does ... # Required
glxinfo | grep GL_ARB_shading_language_420pack
glxinfo | grep GL_ARB_texture_storage
# Optional but really good to have
glxinfo | grep GL_ARB_buffer_storage
glxinfo | grep GL_ARB_texture_buffer_range
glxinfo | grep GL_ARB_base_instance
# misc, just in case. In fact it may be better if this one returns nothing
glxinfo | grep GL_ARB_multi_draw_indirectget hits in all of them for the required ones? And what does the rest get? If the required are not supported, the VMWare can't run ogre2 with acceleration (use If the optional have some missing functions, it is possible you hit a bug; since we don't often hit those paths. |
|
Appreciate this issue had been inactive for a while but as it's still open, and gz-harmonic has been released for Ubuntu 24.04, here is an update on rendering in VM. Host System: macOS Sonoma 14.4.1, arm64 Summary
The required extensions listed above are present: # Required
glxinfo | grep GL_ARB_shading_language_420pack
glxinfo | grep GL_ARB_texture_storageThe optional extensions are not: glxinfo | grep GL_ARB_buffer_storage
glxinfo | grep GL_ARB_texture_buffer_range
glxinfo | grep GL_ARB_base_instanceThere are some errors in the ```bash
$ simple_demo ogre2
terminate called after throwing an instance of 'Ogre::RenderingAPIException'
what(): OGRE EXCEPTION(3:RenderingAPIException): Fragment Program 100000003PixelShader_ps failed to compile. See compile log above for details. in GLSLShader::compile at ./RenderSystems/GL3Plus/src/GLSL/OgreGLSLShader.cpp (line 361)
Aborted (core dumped)Once this is fixed, running the Similarly running the QT_QPA_PLATFORM=xcb gz sim -v4 -g --render-engine ogre2 --render-engine-gui-api-backend opengl |
|
I can confirm that |
Environment
OS Version: Ubuntu 20.04 in VM (Host-Machine is running Windows)
Binary build: Ignition Gazebo, version 6.9.0
If this is a GUI or sensor rendering bug, describe your GPU and rendering system. Otherwise delete this section.
When using ign gazebo -v 3 lights.sdf --render-engine ogre : The scene renders but I get a 1Hz flickering in the scene window.
When using ign gazebo -v 4 lights.sdf --render-engine ogre2 : The scene does not render and I get a black scene window
dxdiagand report the GPU-related information.system_profiler SPDisplaysDataType. Copy the output here.~/.ignition/renderingDescription
Steps to reproduce
ign gazebo -v 4 lights.sdfOutput
Black scene window using ogre2:
ign gazebo -v 4 lights.sdf --render-engine ogre2Flickering scene window using ogre:
ign gazebo -v 3 lights.sdf --render-engine ogreThe text was updated successfully, but these errors were encountered: