You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
SteamVR fails with the error code 307, if enableLinuxVulkanAsync is set to false in steamvr.vrsettings. I would need to disable reprojection, as it severely hinders ALVR.
To Reproduce
Steps to reproduce the behavior:
Set enableLinuxVulkanAsync to false in steamvr.vrsettings
Start SteamVR
Expected behavior
I would expect it to not fail on it.
System Information:
Distribution: Arch Linux
SteamVR version: 1.21.11
Steam client version: Latest as of today, 10.3.2022 (dd/mm/yyyy)
Additional context
As stated before, I am using ALVR for connecting to my Oculus Quest 2 headset. For ALVR reprojection causes major issues such as flickering, jittering, instability, etc. As far as I know this problem seems to be only happening on AMD cards such as mine (RX 570).
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:
Please note that this has already been reported here also please update ALVR as it should be doing it automatically.
It would also be nice to tell me what version your using, also this is not a ALVR support repo so please join the discord or matrix to continue from there.
Describe the bug
SteamVR fails with the error code 307, if
enableLinuxVulkanAsync
is set to false insteamvr.vrsettings
. I would need to disable reprojection, as it severely hinders ALVR.To Reproduce
Steps to reproduce the behavior:
enableLinuxVulkanAsync
tofalse
insteamvr.vrsettings
Expected behavior
I would expect it to not fail on it.
System Information:
Screenshots
Additional context
As stated before, I am using ALVR for connecting to my Oculus Quest 2 headset. For ALVR reprojection causes major issues such as flickering, jittering, instability, etc. As far as I know this problem seems to be only happening on AMD cards such as mine (RX 570).
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: