[BUG] VR Compositor displays SteamVR on Laptop Screen #496
Comments
shaunblyde
changed the title
|
Hello @shaunblyde, it might be interesting to test setting |
|
@kisak-valve thanks for the suggestion, unfortunately I am still getting the same results and vrcompositor.txt still references the iGPU.
|
|
I have found I can get SteamVR using video memory (monitoring via EDIT: Audio output is also not detected, not sure if this indicates a driver issue or similar? The microphone is detected, but doesn't seem to pick up any sound.
|
|
Here's how I got mine to work with your exact laptop: I do believe the linux kernel itself doesnt support leasing a display that is connected to another GPU so you must run your wayland session on your dGPU to be able to lease your headset to openvr. |
|
You are a hero, thank you! Now to see if Gnome has any equivalent environment variable. |
|
Hi, I think I'm running into this issue, too. I also have two GPUs here. Already wrote a comment on the closed #202 (a duplicate of this one?), which I found first, before this ticket. This is what it looks like for me and this is the hardware and the software versions I'm using: https://gitlab.freedesktop.org/monado/monado/-/issues/267 How would I properly disable the iGPU on X11+Xmonad? |
|
Hi, can you confirm which desktop environment you're using? I could only get it going on KDE (and it was a bit janky), but I'm usually using GNOME. So I ended up just using Windows and haven't tried it again for a while, but I can do some testing.
…On 13 June 2023 5:47:07 am GMT+02:00, T-X ***@***.***> wrote:
Hi, I think I'm running into this issue, too. I also have two GPUs here. Already wrote a comment on the closed #202 (a duplicate of this one?), which I found first, before this ticket. This is what it looks like for me and this is the hardware and the software versions I'm using: https://gitlab.freedesktop.org/monado/monado/-/issues/267
How would I properly disable the iGPU on X11+Xmonad?
--
Reply to this email directly or view it on GitHub:
#496 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
|
Hi @shaunblyde, thanks for your reply! Like I wrote above, I tested it with the tiling window manager Xmonad. From reading these tickets here so far I got the impression that something might have gotten confused with the two available GPUs. But the window manager is a good point, too, I'll retry with KDE, Gnome and Mate the next time I get a chance to do so and will provide an update about my findings here. |
|
The root issue is entirely to do with running apps across different GPUs. If on any sort of PRIME system ensure everything in use in your VR session is running on the same GPU as cross use of optimized vulkan memory segments read out wrong when reaching into other GPUs. Just append the env var |
|
@SpookySkeletons thanks for the suggestion! Unfortunately, for one thing DRI_PRIME=1 does not seem to fix the scrambled overlays for me. For another, this makes the VR environment appear as a window on my laptop screen instead of on the VR headset. I'm using this https://github.com/hertg/egpu-switcher to set the eGPU as the default GPU. This tool creates the following file for me:
|
|
I recommend running wayland for your multiGPU setup, Xorg is terrible for this kind of config. You must identify what kind of a PRIME configuration is running on your system and then from there you must ensure every element of your SteamVR session is running on the eGPU if you want to see maximum performance without artifacting. A particular window is artifacting because it is being run on a different GPU than the actual VR session, the vulkan textures located on that GPU are optimized for that GPU, and when read out back to the steamVR session on your other GPU they appear scrambled. |
|
Ok, after many tries/hangs/reboots I got it working with Plasma+Wayland+LightDM, too. Using "DRI_PRIME=1 %command%" as the SteamVR launch option (and having the xorg.conf set by the egpu-switcher - not sure if it was needed, might have only had an effect on LightDM and on which display its greeter was shown). But I can also confirm that it seems janky / very jittery, like @shaunblyde wrote. On Xmonad+X11 it was fluent (when setting the CPU governor to performance and other than the SteamVR overlay not working). I would love to switch to Wayland but unfortunately Xmonad only works on X11... So the next steps for me would be to report a bug at X11? Or could/should SteamVR do something differently? (is the SteamVR dashboard using a different compositor or something like that?) |
|
Steamvr is perpetually broken. Do not expect fixes soon. The steamvr compositor will function but it will consistently miss time frames to the display. We are trying to fix up the open XR stack to wholly replace steamvr on desktop linux. |
Describe the bug
I am running an all-AMD laptop (Asus G513QY) and have tried many troubleshooting suggestions, but cannot get SteamVR to display on my Valve Index, VRCompositor always shows on my laptop display instead. There is no issue with movement of the headset and controllers as this can be demonstrated as functional within the display of VRCompositor.
I am currently using
DRI_PRIME=1 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%as Launch Options within Steam, and running X11.It works fine on Windows, so there is no hardware issue, they USB-C port I am using (to DisplayPort adapter) is directly connected to the dGPU.
I suspect SteamVR is not loading using the dGPU (despite my best efforts with Launch Options) as there is a line in the logs (see below) referencing the AMD RADV RENOIR, which I believe is the iGPU. My understanding is that this would also explain the
Failed to acquire xlib displayerror.SteamVR also wants to select 90Hz as the operating frequency, and I would like it to run at 144Hz. I cannot currently change this, but perhaps it will become possible once the display issue is resolved.
Thank you for the assistance.
To Reproduce
Steps to reproduce the behavior:
Section "Monitor" Identifier "DisplayPort-1-0" Option "PreferredMode" "2880x1600" Modeline "2880x1600_120.00" 827.00 2880 3128 3448 4016 1600 1603 1613 1717 -hsync +vsync Modeline "2880x1600_100.00" 678.50 2880 3128 3440 4000 1600 1603 1613 1697 -hsync +vsync Modeline "2880x1600_90.00" 607.00 2880 3128 3440 4000 1600 1603 1613 1687 -hsync +vsync EndSectionDRI_PRIME=1 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%Expected behavior
I expect SteamVR to use my Valve Index as the display, rather than open VRCompositor on my laptop display.
System Information (please complete the following information):
Additional context
vrcompositor.txt logs below.
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.
The text was updated successfully, but these errors were encountered: