VR Discussions, Questions & Feedback

Thank you so much for mentioning this. I did not realise that adjusting the FOV required a restart. I had been playing around with it before but the squashed perspective and the wonky center of rotation made me quickly write it off. what a fool I've been.

The pico 4 has a really big vertical FOV and I would be more than happy to trade some of that in for extra performance. Can't wait to give this another go. Thank you again!

 

My issue with using Reprojection with OpenXR Toolkit is that it stayed on 45fps even though it should've reverted to 90fps, I had to "force" it back to 90 by looking at the car floor!
Eventually I have up and now have two separate graphics config files, one that bumps up the graphics for daytime and one that lowers them for nighttime/rain, bit of a faff but works well enough for me.

 

doing the same thing with my PICO Neo3 Link right now so thanks for sharing your experience.

These headlights are a fps killer and when you drive in the rain, that's even worse.

But hey that's the big part of the fun with VR tweaking I guess

 

Thanks for the link, this makes the HUD much better in VR although it's not a mod as such as it only changes the values in the graphics file. So I copied/paste the one line into the current file as this "mod" hasn't been updated in two years so doesn't include a lot of new stuff added since.

 

Anyone here with a Quest 3, a 4070, and an i5 10400 or a reasonably comparable setup (needs to be a Quest headset though) that has AMS2 running smooth and fast willing to share their settings from A to Z and 1 to 10?

With all the different interfaces, control panels and tools, I'm wondering if these different settings aren't aligned properly they have an negative effect on performance. Like a geriatric on a dozen different drugs can have bad interactions.

NVIDIA Control Panel, Oculus Debug Tool, Oculus desktop app, Oculus Tray Tool, Open Composite, OpenXR (which doesn't seem to work with AMS2), AMS2 in-game settings, VRPerfkit,....

 

I have a problem with the focus of windows in AMS2 in combination with the Pico4 headset. When I take off the headset and the pico4 goes into low power mode, I could always wake the headset from sleep and AMS2 had the focus (I have over 1200 hours of experience with VR in AMS2). In recent weeks, AMS2 no longer has focus when it comes out of sleep mode and therefore the steering wheel and pedals no longer respond. That is very annoying just before the race (when I want to check the amount of fuel). This has caused me to miss the start several times (and get hit by other racers because I can't accelerate after the start). The Performance tab setting is Windowed. Changing the setting to borderless or full screen does not provide a solution (I filled in a separate bug report for a double image). So what can I do to maintain the focus in AMS2 after waking up the headset?

 

I don't think this is unique to your Pico4, I have the same problem with my Pimax Crystal. I play AMS2 pretty much every day, and for me the problem started to appear after the big breaking SteamVR (2.0?) update.

My workaround has been to do a quick double alt-tab which gives focus to SteamVR and then back to AMS2, for some reason.

I haven't had time to test the recent addition of the startup parameter -doNotPauseOnFocusLoss to see if it makes any difference to this behavior, but I suspect that it won't.

 

Seems it’s just something to accept unless Reiza can do something about it. It’s a shame because it makes 24hr cycles difficult in the sunrise/ sunset moments. And reading through the threads it seems OpenXR just ain’t gunna work on an oculus headset, ah well.

 

I just tried this with all kinds of weather and times. And 20 max rendered with the max ai. Its perfect until you add headlights and start moving forward in the pack. You can watch your frames drop with every car you pass. I dont know if its even possible but maybe limit how many cars behind you have headlights or many have headlights that reflect off stuff?

 

Same terrible experience i am afraid with my pico neo3 and quest2

Even using tweaking tools Iike openxrtoolkit or vrperkit
Only way is to reduce dramatically MSAA but then you end up with AMS2 bad aliasing

 

Im using a G2. Result is the same though.

 

Are you using VD or SA? If VD as a sanity check you could try using opencomposite + vdxr at least then you would no if it's steam specific. That's the setup I'm using with my P4 at the moment and I do not suffer from this issue. Also counterintuitively opencomposite + vdxr actually gives objectively better framerate than SteamVR. ymmv.

 

Yes its definitely game driven not headest type issue

edit please ignore following, thanks
Now someone on discord mentioned reiza pushed an update to mitigate the headlights bad impact
Sorry but i didn't see anything coming to us in japan
People comments here?

 

Hi. I just fired up ams2 in my new headset and somehow I can't get a very sharp image. What's everyone's values in the graphics config file?
What about openxrtoolkit?
Thanks

 

Hi Mate, I'm running a Quest 3 / RTX4070 / 5600X so pretty close in specs to yourself.

I'm still tinkering but this is where I'm at currently. I'm running 80hz and it's stable in daytime, with the occasional need for reprojection with night races. I've set ASW to be off by default but I have a switch on my rig to toggle ASW back on if needed.

I've tried 90hz at same resolution and it seemed fine but I can't really notice the difference between 80hz and 90hz so I figured the extra headroom could be useful.

I've reduced vertical FOV a little via the debug tool as it's an easy way to find extra performance and I honestly don't even notice it after a while. I haven't touched the horizontal as I found this would be noticable even at 0.95 and I definitely don't want to lose horizontal FOV.

I haven't had the chance to tinker with the new visible cars setting. I don't see it being that impactful to be honest as the real killer is headlights of the cars behind you. If Reiza could introduce a setting to change the number of visible headlights ahead and behind that would be ideal. Maybe one day right?

I'm running Quest Link via cable. I've fiddled with Opencomposite/VRPerfKit previously (on the Quest 2) but found any possible gains not to be worth the trouble. I found myself spending more time fiddling with stuff than actually playing so I didn't want yet another thing to tinker with.

These are all my settings. Hopefully it'll help you find a baseline to work from. Let me know how you go and please share any discoveries you make.

Nvidia Control Panel:
All default. I've fiddled a little with MFAA & FXAA but honestly didn't notice any improvement.

Oculus Desktop App:
Refresh Rate: 80hz
Resolution: 5152x2752

Oculus Debug Tool:
Pixels Per Display Override: 1.0
FOV-Tangent Multipler: 1.00 (H) / 0.65 (V)
(PC) Asynchronous Spacewarp: Disabled
Distortion Curvature: Low
Encode Bitrate (Mbps): 400
Link Sharpening: Normal

Documents\Automobilista 2\graphicsconfigoculusdx11.xml
SharpeningStrength: 0.45
SharpeningClamp: 0.09
OffsetBias: 1.00

AMS2 Performance Settings:
Texture Resolution: High
Texture Filtering: Anisotropic 16X
V-Sync: Off
MSAA: Medium
Reflections: Medium
Environment Map: Medium
Car Detail: High
Track Detail: High
Pit Crew Detail: All
Shadow Detail: Medium
Enhanced Mirror: Yes
Motion Blur: Off
Render Frames Ahead: 1
Detailed Grass: Low
Particle Level: Medium
Partical Density: Medium

AMS2 Visual FX:
Post-Processing Filters: On
Exterior Sun Flare: Chroma
Interior Sun Flare: Chroma
Bloom: Off
Heat Haze: Off
Exposure Compensation: 1.00
Rain Drops: No
Vignette: No
Crepuscular Rays: Yes
Screen Dirt: Yes
Cockpit Mirrors: Yes

 

Not sure if this is possible in the AMS2 Engine but in RF2 the following setting in the player.json file worked wonders (or at least used too until they broke it!) - "Max Headlights":256,
With that I lowered it to double digits and immediately got a performance boost, if that is something that could be done for AMS2 then that could be the answer by limiting the number of headlights. Again though there will be "popping" in of headlights on/off cars just the same as now with cars magically appearing/disappearing, different tracks with more cars visible, safety car scenarios etc etc.
Like the visible vehicles setting it would'nt ever be perfect for everyone one, it's about compromise and accepting what you can achieve with your individual system specs.

 

That's much better thanks. Two of the bottom ones cover the wing mirrors though, how on earth do you move them?

 

I use VD, but i'll try SA to see if the same thing will happen under SA. Under VD I use VDXR, but I will try also the OpenComposite.

 

Like most things theres a trade off but until we have 6090s its a necessary one. AMS2 looks absolutely stunning if you can turn the settings up but if you want to play in a scenario that needs headlights you cant do that at this point.. I start at a steady 90fps at the back and by the time im mid pack im at 50fps. So i can live with that.

 

So with vdxr if the game is launching in steam it is ignoring this option, that's why you need to use opencomposite to bypass steam. Hope you can get it sorted either way.