OGRE doesn't display meshes anymore with Intel GPU enabled

[rhaschke]

I'm maintaining an OpenGL application, called rviz, that doesn't correctly display meshes since a few weeks: ros-visualization/rviz#1748

Simple geometries are correctly rendered. As the program runs fine on Linux natively and we didn't changed the rendering pipeline recently, I'm afraid this issue is related to some recent change in WSLg or Mesa.

Looks like WSLg forwards OpenGL via the Mesa driver to the NVIDIA card. I tried building against both, Ogre 1.9 (default) and Ogre 1.12 (which is the underlying rendering library). Both fail to display meshes. Using another application, meshlab, the meshes render correctly.

Was there any change released recently that could explain this regression?

Environment

Windows build number: Microsoft Windows [Version 10.0.22000.675]
Your Distribution version: Ubuntu 20.04
Your WSLg version: 1.0.26

WSL logs following these instructions: WslLogs-2022-05-24_14-22-30.zip

I'm using a laptop with an integrated Intel UHD and an NVIDIA GeForce graphics card. I'm using default graphics settings (power saving using Intel UHD). However, OpenGL (glxinfo) lists the NVIDIA card being used by WSLg:

OpenGL vendor string: Microsoft Corporation
OpenGL renderer string: D3D12 (NVIDIA GeForce GTX 1050)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 21.2.6

[rhaschke]

On another laptop, having an Intel GPU only, the meshes are displayed correctly. Here OpenGL (glxinfo) reports:

OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 21.2.6

I conclude that the issue is related to Microsoft's D3D12 renderer.

[rhaschke]

As a workaround, you can set the environment variable LIBGL_ALWAYS_SOFTWARE=true, thus disabling accelerated rendering and instead enabling software rendering via llvmpipe.

[rhaschke]

Can I provide any more information to resolve this issue?

[IoTDan]

I have this happening with an Intel Iris XE graphics card, with the MESA drivers installed. setting LIBGL_ALWAYS_SOFTWARE=true does correctly render. So looking for a hardware accelerated fix.

[hideyukn88]

This looks like dup of #554.

[IoTDan]

I did the other day. Runs doesn’t crash. Thanks, Dan

…

________________________________ From: Hideyuki Nagase ***@***.***> Sent: Friday, August 5, 2022 4:24:04 PM To: microsoft/wslg ***@***.***> Cc: Dan Rosenstein ***@***.***>; Mention ***@***.***> Subject: Re: [microsoft/wslg] OGRE doesn't display meshes anymore with Intel GPU enabled (Issue #744) @IoTDan<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIoTDan&data=05%7C01%7Cdanrose%40microsoft.com%7Caaf0129e9f9d40c8156f08da77399678%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637953386475155294%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3V2XjQJl1GchLINVI6f%2FGaDjoO4lwCa%2Fpj1SOL08q4g%3D&reserved=0>, would you please run glxgears on your system? Does it crash? We are aware of GL app crash issue with Intel XE graphics, and wondering if your case is same, please let us know, thanks! — Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fwslg%2Fissues%2F744%23issuecomment-1207085322&data=05%7C01%7Cdanrose%40microsoft.com%7Caaf0129e9f9d40c8156f08da77399678%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637953386475155294%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=x%2BEF04bOWxrnASBCP9vDuJCFr1hfl7MaLaU1zGCTJZ8%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB5YFXX7LRS53F62RBNDXRDVXWPBJANCNFSM5WW7Q6IA&data=05%7C01%7Cdanrose%40microsoft.com%7Caaf0129e9f9d40c8156f08da77399678%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637953386475155294%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SYe65juIwb0rUXnc1De5FTB%2FAfVYlvG%2B40FCK8ZsUmY%3D&reserved=0>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[rhaschke]

@hideyukn88, I don't think this is only related to Intel GPUs, but to D3D12 in general. Above, I stated that WSLg picks my NVIDIA card and the D3D12 driver showing these problems (as well).

[hideyukn88]

@rhaschke, we did verification internally at our side, and it is working fine on NVIDIA GPU, while Intel Iris Xe renders black contents (but interestingly it works fine with Intel UHD 620 GPU). Would you please let us know your NVIDIA GPU model and driver version? And if you can take screenshot of app, it's helpful too, thanks!

[rhaschke]

I have a Laptop with an integrated Intel UHD GPU and an NVIDIA GeForce MX250.

software rendering via llvmpipe	accelerated rendering via D3D12
OpenGL device: llvmpipe (LLVM 12.0.0, 256 bits)	OpenGL device: D3D12 (NVIDIA GeForce MX250)
OpenGl version: 3.1 (GLSL 1.4)	OpenGl version: 3.1 (GLSL 1.4)

I don't know how to switch to the Intel GPU to report results for it as well. Is there an environment variable to set?

[hideyukn88]

@rhaschke, please refer below for switching GPUs, and if it reproduces with NVIDIA, would you please share the driver version, thanks!

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10710

[rhaschke]

Switching the GPU via the env variable MESA_D3D12_ADAPTER_NAME=intel doesn't work for me. glxinfo always reports the NVIDIA GPU being selected.

NVIDIA driver: 30.0.15.1236
Intel driver: 30.0.101.1338

Looks like my WSL wasn't updated for a while. However, Windows Update doesn't report any pending updates.

> ver
Microsoft Windows [Version 10.0.22000.856]

> wsl --status
Default Distribution: Ubuntu
Default Version: 2

Windows Subsystem for Linux was last updated on 26.05.2022
WSL automatic updates are on.

Kernel version: 5.10.102.1

[jorolf]

Switching the GPU via the env variable MESA_D3D12_ADAPTER_NAME=intel doesn't work for me

They changed the variable name from MESA_D3D12_ADAPTER_NAME to MESA_D3D12_DEFAULT_ADAPTER_NAME before merging the merge request. (See also: https://docs.mesa3d.org/drivers/d3d12.html#envvar-MESA_D3D12_DEFAULT_ADAPTER_NAME)

[xiayip]

@jorolf
Use MESA_D3D12_DEFAULT_ADAPTER_NAME, the GPU switched, but the problem still exist. I think its the problem with D3D12, not GPU hardware.