VR Discussions, Questions & Feedback

I did clean reinstall and … it didn’t help! :-(

But then I found out that ASW seemed to be stuck/forced although it’s turned off in Oculus Tray Tool and when I switch it on and off it snaps back to my 72 fps!! Yessss!

I have to do this at every game start now. Don’t know what happened and as I mentioned I don’t have this problem in beta or all my other VR games but at least I found a workaround to get fluid 72 FPS again.

 

Any reason you are aiming for 72hz, your PC spec should give you 90hz without any issues?

 

I personally target 72 because when i tried more and was hitting higher framerates, my eyes felt zero difference. On a monitor i immediately see difference between 60, 75 or anything in betwee, but in VR nothing, so i just save on performance by having the lowest refresh rate.

 

Same. Don’t see difference in VR between 72 hz and 90 hz whereas in 2D I’m quite sensitive when it comes to framerates….
And NO, my system can not hold 90 fps. Even the 72 fps are not “secure” in rainy conditions with full grid and especially in replays (Trackside cam) they go down and cause stuttering and ghosting in rainy conditions at specific trackparts when many cars are there.

I must admit though that I have cranked up the Quest3 resolution to maximum (x1.3) in Meta Horizon App and ingame I have maxed graphics settings and VR supersampling set to 1.3 (2 is max) because I like super crispy high resolution…

But yeah, sounds strange that my rig still has huge fps probs at rain and replays with “only” 72 hz in Quest3 and a shrinked FOV (via Oculus Tray Tool)…

 

I've not used 72hz for a while, the issue I had with it at the time (and this issue may have been resolved in updates) was that cars turning in front of you on tighter slower corners didn't appear to move smoothly at 72hz.

If you were just following cars or on wider curves and turns it was fine but on tight corners cars turning across you just didn't look right to me but it was fine at 90hz.

 

I crop a lot my vertical FOV and like to race in 120Hz, after a long time (almost a year) that crap Oculus software keep me out of 120Hz. Daytime clear with 20 cars, I don't have any drop, and ASW with tons of waterspray or at night, with 60FPS reprojection, don't brother so much for the pleasure that is race in 120 FPS in VR in formula cars. 90hz is rock solid with 20 cars in any condition

 

MSAA is still better than TAA with the config file sharpening tweak (i didnt have time to test it) ?

 

I thought I read somewhere that the sharpening tool on the graphicsconfigdx11 .xml file in the documents folder was disabled ... and that we were just using the Super Sampling tool in Steam VR settings?

That comes at a performance loss... is the sharpening tool not enabled anymore? I'm on Vive Cosmos .. it would be this file that does it right, if it's working.. .graphicsconfigopenvrdx11.xml..?

 

it didn't , but I think mine started working again after the last update

 

For me it works again.

 

Here too, hope stays this way and be a future option in settings for use with MSAA and other AA options besides TAA.

 

Does anyone have HP Reverb G2?

Have you upgraded to Windows 11 and it still works?

I'm worried that its not supported in Win 11.

 

it isn't supported in W11 and WMR doesn't run. It does have a 3rd party driver which works on W11 though.

Oasis Driver for Windows Mixed Reality on Steam

 

Im using a Pimax crystal light all was working fine until i changed the car and track combo and now i cannot get the correct view, when i try to recenter i end up in the passenger seat, i have tried centering with the Pimax controller but this puts me out of the car?
I restarted my pc and headset but no luck, anyone had this?

 

Have you got a button bound to recenter the VR view in game? The hardware recenter and the in game recenter are different things.

Also worth binding a button to skip through camera views as you may have accidentally changed your default view and thats the easiest way to loop through them.

In options you also have settings for the cockpit where you can move your seating position about.

 

as previously described, assign a button.
I've added a button to the steering wheel to center the vr-view, to found under control options.

 

Thanks for the replys, i have a button assigned to centre view, turns out i had accidently pressed the change camera view button, ha, had no idea i had done it, will change the button so that i dont do it again

 

Just to add onto the other response, I use the Oasis driver on Windows 11 for my Reverb G2, and in my opinion, it works better than the old mixed really portal way we had to use before.

 

Today I got an update in Meta Link. Can run now in 120Hz with my old 90Hz settings, with a Quest 2.

Someone else noticed any changes in performance? Tested with ASW auto, maybe this thing is working better. Strange as hell, as usual with VR performance.

EDIT: tested now more, and it's better because ASW in 120Hz now is waaaayyyy better. Much less artifacts and better response and transition between on and off.

 

Ive been having real issues around this time - VirtualDesktop with VDXR+OC went to - well 'not good.' in the end I was so desperate for a half decent drive in AMS2 I went back and re-installed SteamVR to try with Meta Link! and yes, it worked, but like a charm as the OPENXR! in VirtualDesktop back to what I had with VDXR+OC, on ethernet link, with H.264+. I have no idea whats going on since early May but something is! Please stop, I want to get off, and just enjoy the AMS2 drive! ;-)