VR Discussions, Questions & Feedback

When Q3 have 120Hz PCVR option, give it a try. Amazing to drive fast cars and 60 fps is the only ASW that works nice in racing.

 

Thank you, but i think i am blind. I can not find it in oculus debug tool.

 

These are my settings which are fine for me and I can also run on Daytona or Nordschleife with rain at night (framedrops to 40fps at the start and than constant 70-90fps). Good weather conditions: nearly constant 90 fps!

My Hardware:
CPU: Ryzen 7 5700X
GPU: 3070ti
Ram: 64gb
VR Headset: Meta Quest 2

Oculus Desktop App:
Refresh Rate: 90hz
Resolution: 5408x2736

Oculus Debug Tool (I´ve setted it with Ocolus tray tool, because I don´t want to start ODT every time new):
FOV-Tangent Multipler: 0.82 (H) / 0.75 (V) -> Absolutely the biggest FPS-Improvement!
Asynchronous Spacewarp: Auto
Encode bitrate: 400
-no other settings there-



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

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

Nvidia Control Panel:
Power Mangement Mode: Maximum
All other settings = Default

Documents\Automobilista 2\graphicsconfigoculusdx11.xml
<prop name="SharpeningStrength" sharpeningstrength="1.00000" />
<prop name="SharpeningClamp" sharpeningclamp="0.090000" />
<prop name="OffsetBias" offsetbias="1.100000" />

->If you have some improvements, so let me know but it works for me!

 

That is from oculus tray tool, that you have to get separately (it uses debug tool though internally).

 

For sure, didn't work that well with 90Hz/AWS at 45 ... like you said earlier, it probably requires that 120Hz with AWS at 60 to be smooth enough.

It's kinda weird they have limited the Quest 3 in that app to 90Hz unlike Quest 2, but haven't increased the max encoding resolution from what is the max for Quest 2, even though Quest 3 can do better.

 

That’s because this screenshot is from the oculus tray tool

that’s another tool than oculus debug tool

 

I've noticed this behaviour with ASW setting not sticking in AC too. Best way to make sure it works is start Debug Tool, set your FOV Tangent Multiplier and anything else you like except ASW, start Oculus Home then go back to ODT and toggle your ASW on / off. A bit of a pita, but the setting does always stick this way

 

aahh I was thinking incorrectly, changing the vertical FOV in the toolkit just "squishes" the image and doesn't actually "cut off" anything. I noticed there's no Disable HAM option with AMS2 like there is with MSFS, that would be handy for an extra FPS or two.

 

At least limiting the FOV with the oculus debug tool cuts clearly. No idea how the OpenXR toolkit works (you had some other than Quest I guess?), would be shame if those don't have similar option.

 

Oh, that could explain some occasional stutters I got yesterday when joining a MP race on Nords

ps. not the greatest idea, haven't really driven on Nords much on VR yet and it was 5 lap race... had to drop out on 3rd lap when it felt that continuing might make my brain go over the limit and make me sick... should have done that probably a bit earlier already as it was a bit too late, fortunately nausea didn't last more than half an hour. I really though I could take it after doing a bit longer races on tracks like Spa, but Nords is on another level what comes to elevation changes and constant left right turns on a super long track.

 

Reverb G2 so yeah it's different, doesn't matter as I've tweaked enough for now was purely interested in the possibility of limiting vertical view.

 

Right Ctrl + numpad 1, 2, 3 and 4 cycle ASW modes:

1 = Full Refresh Rate FPS, ASW OFF;
2 = Half Refresh Rate FPS locked, ASW OFF;
3 = Half Refresh Rate FPS locked, ASW ON;
4 = ASW AUTO (kick in with less FPS than Refresh Rate).

 

You need to restart AMS 2 for it to take the adjustment, otherwise you just end up with as you discovered a squashed image.

 

yeah but the issue is it won't "blank" out the top & bottom of the image which is what is required to help improve FPS further, that's why the FOV adjustment won't work for me with this scenario. FYI adjusting FOV with the Toolkit does not require a restart

 

It does require a restart because it has to request a new render resolution which is what crops the image.

 

I apologise you are correct, I'm so used to the Toolkit saying it needs a VR restart I was relying on that but it didn't state it (like it does for some other options). Unfortunately lowering both UP/DOWN Vertical FOV to their lowest amounts changed nothing with the FPS, like with the Disable Mask HAM setting available in MSFS which disables the hidden area mesh (and helps performance) that is what I need for AMS2 but as above it's not available.

I guess with the FOV change even though you see less it's still rendering underneath the blank areas regardless, a shame but not a major loss.

 

Hi Marc,

Are you referring to the opencomposite.ini file in the x64 folder?
hiddenMeshVerticalScale=0.3

I don't know if it really works though. Don't see much difference

 

no need to apologise, I got caught out by exactly the same thing intially. And also in my case with the pico 4 I actually take a performance hit so it does nothing for me either but, hopefully it's helpful for someones use case.

Anyway overall, I'm pretty happy with performance, realistically only a new gpu is going to get me over the nightime + rain barrier at acceptable settings and even still the aliasing isn't worth it for me. So I just have to live with boring old daylight hours for the time being.

 

Yes, but the small wireless keyboard I use on my lap from the rig doesn't have Numpad and the full keyboard on the desk is a bit of a stretch to reach from the rig so just use the keyboard track pad to toggle ASW in the Debug Tool before starting up the game.

 

hello


can you confirm few things? because your Graphics settings are pretty high so I wonder how you can maintain 90fps in night&rain conditions.sorry maybe many questions but I am curious as I ahve a Q2 and RTX3080 and thats not easy to run at 90fps honestly in such weather conditions

1. you mentioned Daytona and Nord but do you do Race or Hot lapping?
2. if Race, how many cars on track and how many visible?
3. If Race, is 90fps sustainable when you are in the middle of the pack?
4. do you drive in cockpit view?
5. any assistance of tools like Openxrtoolkit to adjust the rendered resolution (not only FOV as you did but foveated rendering resolution and upscaling like FSR or CAS)

thanks a lot!