VR Discussions, Questions & Feedback

Yeah me too, hope they get it working soon!

 

Hey, which settings are you using for camera? And, the setting of old/new camera system is ****ing annoying with an option string saying "use old camera system" with a 0 value for "yes" and 1 for "no" ? It's ****ing weird, universally, on mathematics, programming, tech etc 0 always equals to "no" or "disable" and 1 value equals to "yes" or "enable".

Which is better, old or new? Old is for camera attached on car, new for camera attached on the horizon. Then, there is no sense to use all the other options for the new camera system, no?

 

Not sure if you fixed this but you need to enable Parallel Projections in PiTool

 

There is a version that works now but OpenXR toolkit needs to be disabled. So only for testing.
They know the issues so should be fully working versions out soon.

 

Which version did you use / is compatible?
The ACC one, which should be 0.63 (works fine for me in rf2 now), or the general openComposite? Really need to test that, because I think this might help pretty much with performance, like it does in pretty much every other sim.

 

Could not find the DL on Discord anymore so packed the ones I use for AMS2 OpenXR
You also need Opencomposite Runtime switcher.
And disable OpenXR toolkit.
Hardly worth it as I proper supported version will come inside a week with the changes so OpenXR toolkit also works.

I got a HP Reverb G2 not sure if this one above works with Oculus.

 

Which version are you using? I didn't think OpenXR worked with AMS2.

 

It is not a official version just a unsupported test version.
By next week there should be an official support version that will also support OpenXR Toolkit.
That should give us with WMR headset a much better experience.

 

Not sure if it's a useful tip or already known, but I'm sharing it anyway. If you're using Oculus with a link cable, switch 'link sharpening' from auto to enabled in the Oculus debug tool.
Image looks super crisp afterwards in AMS2 and the AA seems way better to boot.

 

Yep, Meta have worked some magic with the last couple of updates. The image quality on Link and Airlink is awesome

 

Take all my data Mark, I don't care

 

Although I don't use vr,I use trackir and wondered a couple of things firstly does it matter whether I load the game in steam vr or occulus vr also what is legacy mode and does it affect trackir. Thanks

 

I have 2 questions:

1) Is it normal that I have frame time of more than 40 (measured in Oculus Tray Tool with performance HUD)? It seems quite high! I read somewhere that frametime should be around 10 to be fluid. I have more than 40 but it still feels very fluid!? I have Quest 2 running on a RTX3090 with Link cable. In Oculus app I have set 72 hz and resolution to 100% (auto; default) which is still (by far) not the max resolution of the Quest 2.
With this I get fluid 72 FPS although frametime is high!?

2) Is it normal too that with these settings on my rig I still can’t hold the 72 FPS with full grid and rain and very high graphics settings without dropping to 36 FPS (seems AWS being active)? Although I don’t use max resolution of headset and only the lowest refresh rate of 72? Only in dry settings I get fluid 72 FPS…

 

I tried to run AMS2 today withe the fsr-mod by fholger. Got a bug screen…
Yesterday everything was fine.

 

try this one...works for me..
GitHub - fholger/vrperfkit: VR Performance Toolkit

 

Yeah, headlights completely tank VR performance. Hopefully Reiza can fix this one day.

Try running a wet race in a class with no headlights (formula etc). You'll find performance improves immensely.

 

1) Frametime is measured in ms, so 40ms = 1000/40 = 25fps. If you want 72fps you will need 1000/72 = 13.9ms frametime. Set up your graphics so you always stay below 14ms. Always.

2) Yes this is normal. But I have the same system (10900K+3090) and can run at 80fps 99% of the time (12.3ms or lower). 90fps gives issues due to driver/power issues which nVidia just can't seem to solve. Again, set up the graphics so you don't exceed 14ms. This means turning down a number of settings to a level that you feel are way too low for a 3090. Believe me I know how it feels.

 

Thank you, but how can it be that my frametime is so high and still I have 72 FPS? At least the green graph-line in tray tool performance HUB shows constant 72 hz?!

 

One or the other is reporting incorrectly. As Remco has already explained if your frame time average is 40ms then you have 25 frames per second. If your FPS is 72 then frame times must be 13.9ms average. It is impossible to have 40 ms frame time average and 72 FPS - because of arithmetic.

 

Yes, thank you. I understand your maths, but I don't understand the figures on my HUD .
Maybe my value of more than 40 is not frametime? I just had a quick look at the HUD and it reads "App Motion-to-Photon Latency" and the value is written in "ms" (miliseconds). That's why I thought it would mean "frameTIME"?! Is it not? The green graph-line is named "App Frame rate (Hz)" and it shows constant 72...