-
Notifications
You must be signed in to change notification settings - Fork 52
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
OGRE2: Gazebo (Fortress) rendering with OGRE2 crashes in a WSL2 environment with a dedicated GPU present, aka WSLg #662
Comments
related comment / issue: gazebosim/gz-sim#920 (comment) |
Any possible updates on this one? |
I think the workaround is to do software rendering by setting the |
This also occurs in WSL2 running Ubuntu 22.02 with Gazebo Garden. The error says:
This will make PX4 development using Garden on Windows impossible. |
@iche033 do you think we can either close this one or gazebosim/gz-sim#920 (comment), to keep just one issue to track Gazebo Sim support on WSL with GPU-accelerated graphics? @rosiakpiotr @hamishwillee I guess you can check gazebosim/gz-sim#920 for the latest updates on this issue. On WSL2 with GPU support, if anyone is interested in contributing the issue to solve a possible path forward is to use On a related note, if you are interested on Gazebo Sim support on Windows native (i.e. without WSL), you can also check gazebosim/gz-sim#168 . |
Thanks @traversaro ! FWIW Not all that interested in Gazebo Sim support on windows native right now, because the rest of the PX4 Windows toolchain is on WSL2. @bperseghetti suggested Vulkan might work, but there are no obvious setup instructions for WSL and the issues that show up on google search appear to be still open with lots of problem edge cases. |
sounds good. Closing this issue to keep all WSL + GPU support conversations in once place: gazebosim/gz-sim#920. |
Gazebo crashes when initialising the rendering while using OGRE2 as a rendering output in WSL2. Changing to OGRE1 works, since Gazebo Classic also uses this engine and works flawlessly. I checked against outdated binary builds by compiling the current code, but the behaviour is the same. It might be a problem in D3D12 kernel driver or in the way OGRE2 uses OpenGL, but since I'm no expert, I didn't dig too deep. The same behaviour might also apply to a WSL2 environment on Windows 10, but I have to test that.
Environment
Description
Steps to reproduce
ign gz --render-engine ogre2 shapes.sdf -v4
in a WSL2(g) environment with a dedicated GPU presentOutput
auto_default.log
The text was updated successfully, but these errors were encountered: