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
Linux: Rotated playspace breaks ALVR #2013
Comments
I also found a very similar behavior when using ALVR in conjunction with lighthouse devices, and starting a lighthouse device before connecting the HMD for the first time. Once the HMD has been connected at least once, only then the trackers are safe to be powered on. |
+1 on the matter, it causes stutters and small, but constant jumps of camera fov. For me it happens both on Linux and Windows when I'm entering 3D world in Falcon BMS. The difference between Linux and Windows is: under Linux/Proton once it starts it happens all the time, under Windows it's visible when game goes back to 2D mode. |
So let's say we workaround this by just checking if the Matrix isn't an identity matrix and resetting it to one. Would this break playspace movers? |
if @XenoPL says they also had this on windows, i would test it further there. if it's broken on windows too, then it's likely not a steamvr bug |
@Vixea i was actually thinking to implement this in wlxoverlay for the time being. i think it'll be fine, but will definitely impact titles that rely on this working |
Confirm. My test case is an app with 2D UI and 3D world with VR being initiated when 3D world is loading. App (for now) is using OpenVR, so SteamVR is mandatory here. From my limited testing, if game is run on Windows with VirtualDesktop+SteamVR, it seem to be fine. |
@XenoPL can you try this on windows?
this is known to work ok with VD and SteamLink |
@XenoPL does the |
With OVR AS I coulnd't trigger the bug with any setting present on offset tab, rotating, moving space on x/y/z axis nor seated recenter option is unable to make alvr stutter. I've tried latest stable: 5.7.4 and 5.8.6 beta. |
Could you link us to your test case app so we could try reproducing the bug on windows? |
if you have subnautica, i think that's also worth trying on windows with the vr mod. on linux, this breaks right on the main menu. |
Falcon BMS itself https://www.falcon-bms.com/downloads/ Short installation instruction:
Steps to reproduce If needed I'l drop 10$ extra to cover Falcon4 cost. |
@XenoPL we managed to track down the issue, but it is very Linux specific. Your BMS issue is caused by another bug and is not related to the original topic of this ticket. you might want to open a new ticket with the details. |
Thanks for headsup, if it'll fix stutter, pov jumps and latency spikes under Linux, then I'd more than happy. Actually issues with running BMS under Linux are only reason I've installed Windows on my bare metal system first time for last 15 years. |
I did some testing with alvr-streamer build from today master. I'm happy to report changes made fixed my issues with Falcon BMS on Linux. Nice steady latency in 80-100ms range and no jumps or shifts in playerspace. Very pleasant experience in general. |
When SteamVR playspace is rotated, the headset image stutters heavily. During a stutter, the eye images freeze in place, in a way that the frozen image follows head movement.
This happens when using
SetWorkingStandingZeroPoseToRawTrackingPose
or the Seated variant with a matrix where the basis is not identity.Can also be triggered using OVR Advanced Settings' space rotate functionality.
Does not happen with wired headsets.
Some older titles use this as a way to recenter during gameplay, in some cases even automatically, so it's really hard to work around. For example, Subnautica does this when entering player-built structures.
Resetting the matrix's basis to identity fixes the issue. For example, if the game breaks your view, you can use wlx-overlay-s's
Reset Offset
button on the Settings panel and the views will be fixed instantly.I have not tested on Windows, but I would expect this to be a well known issue by now if it broke the same way on Windows.
The text was updated successfully, but these errors were encountered: