Hello @Markosha2004, we've seen similar before if the Steam client and vrcompositor end up running on different GPUs. Can you check if that's the case for you?
So checking through nvtop, there is no vrcompositor process that I can see. However, steam client did launch on the GPU I use for VR, there are 2 vrmonitor processes, 2 steamwebhelper and 2 vrwebhelper processes (one for each GPU)
Going from vrcompositor.txt log file, I'd assume it's also using the same GPU as a steam process
Edit: also installed amdgpu_top. Same story, doesn't show which GPU does vrcompositor use
I'm going to try forcing it to render on my VR gpu with this SteamVR launch option: MESA_VK_DEVICE_SELECT=1002:73bf %command%
'Cause, according to AI, it could be the case of vrcompositor rendering on CPU
edit: nothing changed
got a crash dump with launch option MESA_VK_DEVICE_SELECT=1002:73bf! %command%
I'd test removing lsfg-vk and obs vkcapture from the mix to see if that has an effect.
good call. on it now.
removed lsfg-vk and completely obliterated OBS Studio. Launched steamvr. Got a crash dump, didn't even get past a grey screen. No changes to launch options.
update. Removing launch option mentioned above makes steamvr launch, but the dashboard is still broken
Apparently it's a framebuffer corruption (according to AI)
Describe the bug
SteamVR dashboard is broken and completely unuable
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A nice new dashboard as shown in 2.17 Update screenshot
System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!
runtime diag.txt
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]steam-logs.tar.gz
tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps]steam-minidumps.tar.gz
Screenshots
If applicable, add screenshots to help explain your problem.
Image taken from my another, open as I'm writing this, issue ( #1006 )
Additional context
Add any other context about the problem here.