- This topic has 27 replies, 11 voices, and was last updated Feb 22, 2021 10:20pm by
.
-
Posts
-
With WMR headsets please always leave FluidSync at ‘On’ or ‘Auto’ (which is the WMR default). Something like 90/45 should never happen, that’s what I meant above when I said that WMR makes it more difficult for vorpX to keep the headset frame rate stable. ‘Auto’ should work most of the time. If you still encounter odd situations like the one you mentioned, set it to ‘On’.
Warrie check if reprojection is active Enabling motion reprojection for SteamVR Apps
I don’t know what is the default option, but make sure it’s disabled (none option) if you don’t need it. The 90 game / 45 headset was occurring for me sometimes for a few seconds and it turned out to be auto reprojection.Good find! Clearly makes sense to leave that off (which seems to be the default BTW, just checked with a fresh install).
FluidSync should still be at ‘Auto’ or ‘On’ with WMR, the general issue with WMR making it harder for vorpX to maintain the full headset framerate in some situations does still occur.
Upgrading from a Rift-S to the G2 was well worth it for me, if you crank up the resolution high enough it looks nearly as sharp as a 1080p monitor. 60hz mode is very nice to have as well, it feels better than 90hz with Fluidsync on.
Thanks for the 60hz tip, will give that a try tomorrow. I noticed that some games, although showing 90fps, somehow still don’t feel really smooth, like F1 2020 for example, while for example Wreckfest runs/feels really smooth (both in Immersive mode). Never thought of experimenting with the 60hz mode.
Honestly my experience so far with 60hz isn’t good – F1 2020 still feels a bit stuttery in 60hz, the same as in 90hz. I expected other games to be able to run with higher gfx settings on 60hz but performace between 60hz and 90hz seem to be the same in my test – except now having 60fps instead of 90fps.
A little follow-up on the OpenXR plan mentioned above: I have a first implementation working since yesterday. Only tested about half a dozen games so far, but as much I can tell from that WMR via OpenXR seems to be a significant improvement over WMR via SteamVR. One layer less between vorpX and the headset driver is clearly a good thing.
Not only do uneven game/headset framerate ratios work much better, also game framerates below half the headset refreshrate are working in FullVR mode as they are supposed to. Pretty much exactly what I was hoping for, both major WMR annoyances largely gone, at least with the games that have been checked so far. Really promising.
Still lots of work to do, the headset part isn’t done yet and I haven’t even started with porting over the controller stuff. So don’t expect anything final in the immediate future.
Sounds promising Ralf! And I just read this on Reddit:
Yesterday in r/WindowsMR a WMR developer said that the only current way that the WMR for SteamVR plugin and SteamVR’s OpenVR API can interface is through copying the screen buffer. This can consume large amounts of memory because of the G2 100% size (actually 146% 2160×2160) , especially when (dynamically) oversampling. They have found a possible solution with sharing a screenbuffer both parties are working on.
This is a shortcoming of the OpenVR API, which despite its name is pretty much bound to Valve hardware and implementation, with support for other HMDs bolted on by plugins, instead of each manufacturer implementing the API as a driver.
The only structural solution is OpenXR, which all VR manufacturers including Valve are pushing. The huge difference in performance can already be seen when comparing games like MSFS and Revive with SteamVR vs OpenXR WMR native support.
After working out a few kinks and checking more games over the last days I’m confident to say now that with OpenXR WMR headsets will work just as good as native SteamVR headsets do with SteamVR. Couldn’t have hoped for a better outcome of the endeavour.
The controller part is still missing entirely, which is also a lot of work, so it’ll take a little longer until things are ready for release.
Since I never use motion controllers with vorpx anyway, you could perhaps release a version without controller support first? ;)
Anyway thanks in advance for the Reverb support.
Since I never use motion controllers with vorpx anyway, you could perhaps release a version without controller support first? ;)
Also never use motion controllers with Vorpx. Really looking forward to this either way! thx
- You must be logged in to reply to this topic.