VR Discussions, Questions & Feedback

It happens to me as well in Mosport in the corner right before the straight and in Sebring (the worst of all of them) in a couple of parts. I guess some 3d renders are not very well optimized. In Mosport it might be indeed the many trees, but I have no idea

 

With these settings, I race open wheelers with 90Hz and can go any track at any conditions with stable 90 FPS. If I want to race in Sebring with "boring" cars, night , thuderstorm, go 120Hz and let auto ASW do the magic.

I don't like ASW with open wheelers, because the artifacts when you look sideways with fast moving things are massive. Closed cockpit I can hardly feel when it kick in with 120Hz.

Maybe someday we have variable refresh rates in affordable VR headsets. Will be perfect.

One note: the most important setting for big FPS gains without losing MUCH in visuals ARE cars details and reflections to LOW. The LOD transitions are good. MEDIUM is terrible, just as HIGH. And ULTRA is heavy as hell.

 

BTW I tested 24 hour race (30min x50 time acceleration) yesterday for the first time in 1.6. It was Road Atlanta with full 48 cars (IMSA multi class). While in 1.5 I always had FPS decrease when getting dark, in 1.6 I had no performance hit whatsoever during the whole race

 

Stutters aren't always the easiest thing to get to the bottom of. One of the easiest things to try though is turning off HAGS Hardware Accelerated GPU Scheduling, reboot, check that HAGS is still off then try the game, HAGS off has helped in a few games for me including AMS2.

 

Do you mean that low is better than medium and high regarding overall image quality, or only for FPS?

 

Image quality too. The LOD transitions are really good in all cars at LOW. Other settings besides LOW and ULTRA are really visible, and with fast aproachig cars it's even dangerous to judge distance.

 

Particles are a FPS killer now.
I took a fun car on test day mode and started doing donuts. My FPS went down to 5 or 10, it was pretty bad.

New particles look fantastic though, i had settings on ultra dn high just to see them but i can't use them unfortunately

 

After testing and very rare FPS comeback to me. The final conclusion to me is, Reiza should do an ULTRALOW setting on track detail and car detail LODs, and a view distance slider.
In VR we can make sacrifices to maintain FPS.

 

The performance really has dipped hard.

Sunset in Hockenheim running qualifier without other cars in sight. Cant keep the frames at 90 fps. Not even close. Running OpenXR 2700x2XXX render res, basically all settings low, MSAA medium (also tried with SMAA ultra with no real help) Foveated rendering 50% outer ring with 1/16 render res, horizontal scale 185%. Frames run somewhere around 70fps. The qualifier was on LFM race though, so could that have an impact somehow? The ghost cars?

Daytime i can run 20 AI cars race without an issue, what the hell?

 

I follow some of your tips after reading 20 pages for VR settings.
Is it possible that you post your settings or youre videos with Microsoft windows set to english language? AMS2 also

 

LOW = BAIXO
MEDIUM = MÉDIO
HIGH = ALTO
ULTRA is the same.

But will change the language and make a video with the settings that can do this in MP:

 

Since so many people are struggling with the settings, I'll share here mine. I have a Quest3 and AMD 6950xt GPU, i7-13700F. With these settings I get stable 90Hz most of the time during day and night but only if it is not raining (max Quest3 resolution). Exceptions are the first lap in races with 48 cars, where the performance drops to around 70/75Hz, gets better in second lap and stable in 90 afterwards. Also some corners in Mosport and Sebring (mostly Sebring) where performance takes a hit. This is a generalization since I still didn't test every circuit of course. I am still trying to figure out what's the best compromise to do for raining, but I have some trust that some near future patches will improve the performance again.

Some stuff is in spanish but I guess it is sorted equally in other languages so people can hopefully find it useful (low=baja, medium=medio, high=alta)

In graphicsoculusdx11.xml:

<propname="SharpeningStrength"sharpeningstrength="1.200000"/>
<propname="SharpeningClamp"sharpeningclamp="0.090000"/>
<propname="OffsetBias"offsetbias="1.000000"/>

 

Too bad the fov tangent tweak is not possible with other than Meta headsets We need that Quad Views foveated rendering..

 

I use these settings.

I like to go ULTRA with shadows and Track Reflections, because these two have massive visual quality improvement for FPS hit, most visible in night (shadows), rain (Track reflections) and sunny days (shadows). I save FPS in cars reflections and details, and go for Track Details to MEDIUM, because in tracks like Daytona, Sebring and Azure, saves stutters and FPS drops in some points, with really minor objects pop up and LOD visible changes.

I give up of sharpening in config file editing, even if it is almost FPS free, and go to supersampling, because sharpening in config files induces more shimmering and supersampling is amazing for distant textures details, the biggest problem of Madness Engine in VR visual quality.

FOV I set horizintal the max visible for my IPD with Quest 2 (0.675), and set vertical to the size that I loose nothing of situational awareness when looking sideways (0.375). This have massive FPS gains, and I can go to 120HZ, and don't need any size buffer in image size with this refresh rate.

All settings are general guidelines, because VR is a funny mess with each Headset, hardware and even IPD.

 

For sim racing will be great someday a "cheap" headset with massive horizontal FOV and limited vertical FOV screens and optics.

But Reiza can solve this with a workaround: create a VR mask that only renders what we set vertical and horizontal, and all the rest total black, and the engine just do work rendering the visible area. Will work for any headset. A new "helmet view", because what we have now just put another layer and saves nothing in performance.

 

Thanks for the Quest 2 information.

 

Thanks, I'll give a try with supersampling instead of the config files thing, indeed my biggest visual issue are distant objects. So you set supersampling direct in game (not in Oculus debug tool). I read that the in-game supersampling does nothing, took it as the truth and never touched it myself. I also get a very big performance hit with shadows (and I don't like how they look like anyway), so yeah... interesting world this of VR configuration. Track details to me is god and I won't decrease it xD I just love to look at the road details near me.

 

Supersampling is working nice ingame, and you already have at Max what link can delivery in image quality (I can't set link resolution to 4096 with 120Hz, link can't keep up, even at 960 bitrate). Try set Supersampling to 1.3 just for testing and look at distant textures. Is a game change for sure! And works nice with flickering distant shadows in ULTRA and fences too.

Track details don't interfere with anything besides LODs. I only notice a difference in MEDIUM to ULTRA at trees in Montreal (pop up) and some little things in Green Hell. But from HIGH to ULTRA, only can see FPS gains.

 

<data class="GraphicConfigData" id="0x42676300">
<prop name="Name" data="" />
<prop name="Build" data="2752" />
<prop name="Version" version="2" />
<prop name="Mode" adapter="0" width="1920" height="1080" refresh_num="60" refresh_dem="1" />
<prop name="Vsync" vsync="0" />
<prop name="FrameLatency" framelatency="1" />
<prop name="AntiAlias" antialias="2" />
<prop name="SMAAFXAA" smaafxaa="0" />
<prop name="Windowed" windowed="2" />
<prop name="TextureFilter" texturefilter="5" />
<prop name="TextureResolution" textureresolution="2" />
<prop name="Brightness" brightness="10" />
<prop name="CarDetailLevel" cardetaillevel="3" />
<prop name="MaxVisibleVehicles" maxvisiblevehicles="12" />
<prop name="TrackDetailLevel" trackdetaillevel="3" />
<prop name="ShadowDetailLevel" shadowdetaillevel="3" />
<prop name="MotionblurLevel" motionblurLevel="0" />
<prop name="EffectsDetailLevel" effectsdetaillevel="2" />
<prop name="ParticlesDetailLevel" particlesdetaillevel="3" />
<prop name="EnvmapDetailLevel" envmapdetaillevel="1" />
<prop name="MirrorEnabled" mirrorenabled="1" />
<prop name="MirrorEnhanced" mirrorenhanced="1" />
<prop name="EnvmapReflectionDetailLevel" envmapreflectiondetaillevel="1" />
<prop name="GraphicsLevel" graphicslevel="4" />
<prop name="SuperSampling" supersampling="0" />
<prop name="LowSuperSampling" lowsupersampling="0" />
<prop name="VRSuperSampling" vrsupersampling="0" />
<prop name="SharpeningStrength" sharpeningstrength="3.000000" />
<prop name="SharpeningClamp" sharpeningclamp="0.090000" />
<prop name="OffsetBias" offsetbias="1.100000" />



After Hours of testing and reading over 400 Posts are these my "clearest" settings in AMS2 1.6
It was a pain . Everytime it was blurry with no Details in the Distance, and the 3D effect was not there and you had low sense of speed. Now it feels more natural to drive and you feel more that you inside the car . I Have more control over the car and can see the surface much better

Aus=Off
Niedrig=low
hoch=high

 

Max bitrate and supersampling does wonders in blurry asphalt in headsets with this crap compression. In 120Hz you really can feel the speed and judge MUCH better distance.