VR Discussions, Questions & Feedback

you're welcome, not really sure which to elements you're talking about, I tend to only ever use a hud to briefly check position or the ffb meter. In the hudUI options you can turn on/off whichever elements you want and to an extent position them as you like.

 

You don't need that VR hud mod, the ingame VR hud menu contains extra settings for resizing, rotating, tilting and adjusting the H & V planes fore - aft, up - down etcetera. It's under the help menu in the hud and displays what keypad keys you need to use.

 

Hey everybody , i dont know if this is a known issue or not but i gained a good 25 fps by disabling driver names .During daytime its not a big problem but during nighttime it helps allot .

 

I tested that nighttime performance loss. Started with 29 gen2 GT3s at Spa, 6pm and x15 acceleration, I started last or at least close to (it was random, but I remember everybody being in front of me on first lap).

I have set my configuration so that normally I have about 35-40% headroom (in the oculus debug tool performance overlay).

When the darkness came and I overtook cars, I went down to -5% to +20% head headroom and my fps usually stayed the same, only dropping max 5-10fps. So basically I needed the headroom to avoid having impact to how smoothly the game runs (and this is kinda my whole point, try to make sure you have that headroom available if you want to avoid how the conditions affect your fps).

As for my settings (Quest 3, rest you can find from my signature).

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

Oculus Debug Tool:
Pixels Per Display Override: 0
FOV-Tangent Multipler: 0.9 (H) / 0.3 (V)
Adaptive GUP Performance Scale: Off (first time trying this OFF, not sure did it do anything)
(PC) Asynchronous Spacewarp: Disabled
Distortion Curvature: Low
Video Codec: Default
Sliced Encoding: Default
Encode dynamic bitrate: Disabled
Encode Bitrate (Mbps): 500
Link Sharpening: Quality
Local Dimming: Enabled

Oculus Tray Tool:
I just installed it and set the values, but not sure did it actually do anything as I had debug tool already running at the time (and the values were set pretty much similar to what I had in Oculus Debug Tool).

AMS2 Performance Settings:
Texture Resolution: High
Texture Filtering: Anisotropic 8X
V-Sync: Off
MSAA: High
Reflections: Low
Environment Map: High
Car Detail: High
Max Vehicles: 18 (there is still issues with some cars vanishing from front, but it was only issue in the first 2 laps when the whole group was together).
Track Detail: High
Pit Crew Detail: None
Shadow Detail: Low
Enhanced Mirror: Yes
Motion Blur: Off
Render Frames Ahead: 1
Detailed Grass: Off
Particle Level: High
Partical Density: High

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

Nvidia Control Panel:
All default.

Documents\Automobilista 2\graphicsconfigoculusdx11.xml
All default

 

Where do you do that?

 

I never had them enabled because of immersion, but a whole 25 just from turning off that ? Seems odd.

 

I took them out recently too, not because of fps in mind, but because it sometimes made it look I can see thru another car. I wouldn't surprised that it might impact performance too.

 

Gameplay - Display OPPONENT NAMES -> OFF

 

It's been a while since running AMS2 in VR but, is anyone else having raindrops (open cockpit) on the visor in VR?
Tested with / without helmet view, nothing.

 

Hope it works for your headset. Another note on the FoV, I still don't know what it actually does in the openxr toolkit. It felt more like a supersampling in the narrowed region with the pixels provided for vertical resolution. So to get more fps one would need to lower the resolution again? (I didn't test it myself)
This VR stuff .. In ten years the children will just switch it easily on without any problems, and we tell them: "you know, back then we injected third party tools, exchanged hardware parts in the headset, overwrote the config files, restarted the game 268 times, to just get some 3k pixels at moderate fps (<-- they will call that a blurry mess then), and during the night, and rain it was even more difficult!"

 

I had a play around with it yesterday and yes when you first apply it while in game it just squashes the existing resolution into a smaller box. After a restart though as you said it fixes the scale and in the headset it just appears as though the original image has been cropped. However, it actually had a negative impact on performance in my case, I believe this is down to Virtual Desktop in my case, one of the devs/mods on their discord said that due to VD's design gains would likely be very small if any.

 

The optimized max visible vehicles setting in 1.5.5.1 works much better, on my system a 30 car race with setting to 18 visible vehicles FPS jumps from 50 to 60. Finally Reiza did something to save the poor performance at night. But when I get a leading position in a big crowd FPS drops again as the number of visible vehicles increases.

In this case it is clear that light casted by vehicles behind costs much more performance, therefore adding a separate option to limit the number of visible vehicles behind may achieve bigger performance boost than current solution. For me with VR, 4-5 visible vehicles behind is enough as they can be seen in side mirror only, side effect is negligible.

I'm so happy the night performance issue finally comes into devs' view, please keep on! Thank you Reiza!

 

Found a workaround guys

change driving view from cockpit to bumper and bang no lights reflections inside the cabin anymore killing the fps


Oh yeah but killing the VR immersion

 

I never thought about trying this but, I have wondered if the problem is interior reflections/shadow casting etc. Would be interesting if they could test having only the car closest behind you casting to the interior. Although that starts to get very specific, probably a bit of a head scratcher to implement. Still wanting other cars in front and behind to affect the exterior environment but not the interior...

 

The interior light casted by cars behind is so annoying, I would rather turn it off totally. In terms of the performance cost of such light, it may be a potentional direction of opitmization.

 

I give up to demand changes in core graphics engine. The game engine is third part, and I really think is hard to Reiza to change some things - even simple - in this aspect.

 

Ah, good catch with restarting AMS2 to apply FOV correctly! Thanks.

 

Thank you for this! Major improvement in clarity. I need to fiddle with the MSAA level. I have it on high and think medium might give a smoother experience. Need to balance that with the quality drop though. I do think I had some settings that were conflicting, and missed some obvious wins (majorly raising the resolution level) due to there being about 5000 variables amongst all the platforms, config files etc.

Thanks again, much appreciated.

 

I know my post sounded like a joke, was the purpose of last comment but actually I was being serious in the return on this camera view change.

I do drive in bumper view when I play on my 4k TV, its an habit I took in my early video games days 40yrs ago so not changing now that I have happily passed middle aged man age

but of course in VR, nothing gives more immersion than the cockpit view.

I play other Sims in the rain&night with a better VR experience so I feel its only with AMS2 that I had to use this workaround

 

Is it possible though to change to bumper view and then move the camera back so it is in the cockpit?