-
Notifications
You must be signed in to change notification settings - Fork 300
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
rviz/Gazebo Not Rendering 3d Space on Intel Laptop #455
Comments
I have the same issue on Intel UHD graphics 630 on my core i7 9700k system. Blank output in glxgears. Works fine on my another system having discrete nvidia 1650 super card. Tried using latest Intel DCH drivers and old ones too. Latest os build 194 and wslg 1.0.26 |
I also have the same problem |
For me arch seems to work on same setup. https://github.com/yuk7/ArchWSL |
it is probably using software rendering in arch wsl, so it is not distro specific: #482 (comment) |
I have the same problem, but new tidbit of information: Software rendering, after installing the generic Intel driver but before I installed the updated Mesa, didn't display any GUI windows at all. Dell XPS 7590 (also has a dedicated Nvidia GPU, but apparently we want integrated for WSLg)
|
I think the title of this bug should be made more generic to clarify acceleration is not working on Intel UHD. Seems like a fairly important thing to fix. |
@westonNexben Well, as mentioned in #334, I also happen to be facing the same problem. Furthermore, I also happen to have it on the same platform as you, similarly a Dell XPS 15 7590, with the UHD 630 and GTX 1650 GPU as well. Hopefully a solution is found. |
Hello everyone, |
Regarding Gazebo, I have set "export LIBGL_ALWAYS_SOFTWARE=1" and then run gazebo, and I get now the GUI working well. |
yes but in this case you are not utilizing gpu, and since gazebo requires gpu to perform well, it is not that useful |
Yes indeed, I have checked, CPU is very high and GPU not used. I hope a fix will be delivered soon. |
Looks like the latest Intel Graphics Driver 30.0.101.1404, 2022-03-08 finally fixes the issue. |
Any fix for Nvidia? |
I tested it on Windows 11, Ubuntu 20.04, Intel 630. Indeed 30.0.101.1404 finally brings something new. Gazebo works great now (fast and smooth and GPU usage about 70%). However Rviz is not fully ok for me. The grid and axes are displayed now but my robot is not showing with GPU acceleration on. I tried with Mesa 21.0.3, 21.2.6 and kisak (turtle) 21.3.7 (same as suggested by svetoslavenchev) but same result: grid and axes displayed but not my robot (while it is correctly displayed with GPU off: GALLIUM_DRIVER=llvmpipe). |
I changed my laptop and upgraded to an Nvidia MX450 GPU. Result is identical in Rviz (and Gazebo). In fact, I realized that there is already an issue raised for Rviz addressing this specific problem (wslg issue 554). |
I have intel Iris Xe, and upgrade to: Tested on latest Windows 11, Ubuntu 20.04, Mesa 21.3.8 |
Same problem on my dell xps 13 9310 with intel iris xe and n. driver 30.0.101.1660 |
Since my new laptop has both an Nvidia MX450 and an Iris Xe, I had a try with the Iris Xe. I confirm that Gazebo remains black/empty with the Iris Xe (while it worked ok on my older laptop with same driver and Intel UHD 630). However, glxgears is working ok (gears are displayed and GPU acceleration provided by Iris Xe). Rviz is showing as well (but impacted by the global problem I mentionned earlier - STLs not being displayed). So now, It looks more like a Gazebo - Intel Iris problem only. |
Does anyone with Intel Iris happen to dual boot Linux is I see if it’s just a WSL issue or in both environments? |
Here! I don't have this problem on the linux partition |
Edit: Original message: |
Hello, I did a quick test on driver 30.0.101.1960. For me, the situation has not changed on Iris Xe: Gazebo is still black (and the meshes are not displayed in Rviz but this is a separate issue). rmorassi, I would tend to think that you had not GPU acceleration enabled when you did your test. At least, Rviz cannot be fully ok for now when GPU acceleration is on (wslg issue #554) - this is true for Intel Iris, Intel UHD and Nvidia MX at least (that I tested). |
The same for me, the problem still persist with the new driver (dell xps 9310) |
Anyone had any luck getting this working in hardware mode? |
Hey guys, I'm also with the same problem, glxgears works fine showing gears, but with driver Intel® Graphics Driver 31.0.101.3222/31.0.101.2111 on Windows 11 Intel Iris Xe, Gazebo just shows black screen, managed to get it working only on software mode |
Same here. No success with 31.0.101.3222 |
My friends, when I use coppeliaSim, the same problem occurs🤷: some of the openGL based screens are black. Hope to repair it as soon as possible!🙏 WSL2:Ubuntu20.04 |
Just to keep the issue alive, the problem is still here, not matter which kernel or driver I'm using! |
Is there anything happening towards solution? Feeling like this has been dead for too long now, being crucial feature for WSLg users that develop robotic systems using Gazebo. |
saved my life TWO times!!!! The other day windows updated the system, then I have to reinstall this driver...
This also works on my issue! I think the reinstallation just reset the GPU off, but every time I restart my laptop, the issue still happens. |
Laptop with 1235U Intel Xe, still no way to get accelerated graphics in WSL. llvmpipeis CPU rendering, not a solution at all. My 5 years old Galaxy phone with Dex can run llvmpipe and just like the laptop, it barely plays FullHD youtube in Firefox. With working graphics acceleration it should be an easy task. |
Ubuntu 20.04 & Windows 11 & Intel Ultra 9 185H with Arc graphics still not working. Gazebo even won't show up unless using |
After I type |
Environment
Steps to reproduce
rosrun rviz rviz
orrosrun gazebo_sim gazebo
WSL logs:
weston.log
pulseaudio.log
versions.txt:
WSLg ( x86_64 ): 1.0.19+Branch.main.Sha.2a47bf20c239b523d7413f315cbc9ee60dfde831
Mariner: VERSION="1.0.20210224"
FreeRDP: 5f083fa0b97d433d6204985f6047886e29c1c61e
weston: 16de531f00aa3dfd17e0de74c8f49e9fd7cec617
pulseaudio: 2f0f0b8c3872780f15e275fc12899f4564f01bd5
mesa:
Expected behavior
The applications should render the robot/simulation or at least the 3d grid.
Actual behavior
Gazebo:
![image](https://user-images.githubusercontent.com/733411/133133599-59daa246-f5df-4474-92d4-63140dc015ac.png)
rviz:
![image](https://user-images.githubusercontent.com/733411/133133747-d41b819a-9546-4f06-b42c-0ce1e64ebcf3.png)
This works fine on my intel/nvidia based machine but on my Intel laptop it consistently shows this behaviour where previously it worked fine.
CPU: Intel Core i7-8565U
GPU: Intel UHD Graphics 620
I've tried with the latest Intel drivers which claim to support WSLg and the newer beta drivers with the same behaviour.
The text was updated successfully, but these errors were encountered: