VR Discussions, Questions & Feedback

.

 

Hi,
very interesting topics here to read. Will try to edit the vertical FOV myself and see if it helps to boost the performance some more and if it looks for me, even if I have a decent performance in general.

I got a question to the Oculus debug tool. I always set asynchronous spacewarp to off. Sometimes it remembers it and sometimes not, so I have to check all the time I play. Is there a solution, so I can be sure it is off all the time?

Thank you
Florian

 

yes with the profile option

 

There isn't a magic bullet which will make your GPU process more graphic effects for free. It's either lower settings or buy a better GPU.

 

allocating time,brainstorming options,testing and validating is more the Option I personally prefer but each to his own I guess

 

Yes talking about things always makes up for lack of GPU grunt. Carry on

 

I meant the AMS2 config file where you can increase the sharpness for the game. I have the link sharpening at Quality on the ODT.

 

You have stocks at NVIDIA by any chance?
Just curious

 

It took me a while to "accept" having the vertically limited FOV in VR, but it didn't took that long before it I didn't even notice it when driving. With tintops, you view to outside is still less than what your vertical fov will be, so it doesn't really limit anything much, but I was also suprised that I didn't care about having it at 0.3 even with open wheelers, it's not like I have time to look up and marvel at the sky during driving..
.

 

Same with Quest 3, max resolution (I run with 80Hz personally and no ASW). I do run higher horizontal fov (0.95) with Quest 3, though I have a bit more powerful GPU (3080).

In any case, limiting that vertical fov is really easy to get a lot more performance out of your system with AMS2 without big drawbacks (IMO). If the vertical fov is limited a lot, I didn't find the need to limit the horizontal fov that much either (especially with quest where the image is pretty clear on the sides too).

 

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.