VR Users - START GUIDE

[Wilck]

MAJOR UPDATE in 01/05/2025
*Engine.ini to FSR MODE.
*New Engine.ini to DLSS QUALITY.

UPDATE in 07/04/2025
*New graphics settings (The game is more heavy in the last update)
*new recommended FOV... heavy... =\
*Use DLSS 310.1 file
*new refinaments for the DLAA;

UPDATE in 31/03/2025
*Complete overhaul of the GUIDE;
*DLAA is the default option now;

UPDATE in 26/03/2025
*Adjustments for the 2.3.1 version of the game:
*Changes in: eye adaptation, color mid, sharpening and AA Quality;
*Recommend using DLSS 310.1 and PROFILE J (10); DLSS 310.2 and Profile K doesn't resolve very well the Anti Aliasing and ghosting.

UPDATE in 19/02/2025
*Removed various command lines

UPDATE in 30/01/2025
*Adjustments for the 2.2.1 version of the game
*A few upgrades in quality graphics and FOV for GODLIKE setting.

UPDATE in 26/01/2025
*Notes about DLSS 4 (310.2)
*Night mode (sound) for Q3
*AF 16x is now possible with new DLSS.

UPDATE in 05/12/2024
*Add some lines to force better material upscaling

UPDATE in 13/11/2024
*Include external link to definitive fix for the microstutters.

UPDATE in 03/11/2024
*Presets for others GPUs ready to play on Quest 3.

UPDATE in 22/10/2024
*Lock the DLSS profile in engine.ini (Help with image stability)
*Lock the bloom quality to resolve the snowflackes

----

REQUIREMENT

- High tier CPU (i5 - serie 13 or above), AMD (serie 7000 or above), x3D chips recommended
- High tier NVIDIA GPU - 4070Ti or above
- Disable OpenXR Toolkit
- OpenXR headset preferable
- At least 12 GB of VRAM
- GPU with DLSS capable (preferable)

- A LOT OF PATIENCE...

----

IMPORTANT

*Use DLSS 310.1 and Force DLAA (Great Clarity):
Works even better than DLSS Auto MODE ON. But have a BIG glitch in some sky and trees. It's more heavy than DLSS Auto, BUT the results even in lowest resolutions (2500x2500) are very, very decent.

* HistoryScreenPercentange create several bugs in AMD cards. Drop off if you use AMD cards. The image will lose a LOT of resolution...

*Any adjust include in [SystemSettings] create the right eye black frame. So if you have this glitch remove all the codes and this headline there.

*Don't use the Post Processing in Ultra, create the wrong camera position in left\right eye.[

*OpenXR Toolkit DON'T WORK in this game. There is nothing to do about it.

*Disable SMT (AMD or INTEL) DO IT! This engine hate SMT!

*For MICROSTUTTERS - Disable "Control Flow Guard for the WRC.exe. Instructions on the link below.

https://www.reddit.com/r/Back4Blood/comments/qgjp2z/psa_disable_control_flow_guard_for_better/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

*Use DLSS 4 (310.1) - NOT the 310.2 - DLSS file has to be installed manually on the game folder. It's a game change, brings better LATENCY (a lot), sharpening, fluidity and have only a few artifacts now. RECOMMEND! [/b] This engine.ini already choose the profile.

Game folder
C:\xxxxxx\Steam\steamapps\common\EA SPORTS WRC\Engine\Plugins\Runtime\Nvidia\DLSS\Binaries\ThirdParty\Win64

Download the version 310.2 at:
https://www.techpowerup.com/download/nvidia-dlss-dll/

-------------------------------------------------------------------------------------------
After +285 hours of testing, gaming and searching for tweaks, trying to achieve the best quality on VR and FLAT gameplay on this game, here is my tips and know-how acquired.

Here the hardware and software used.
Quest 3 – V74
PCVR - 9800x3D + 2x16 GB (6000 Mhz) + SSD Nvme 4.0 + RTX 4090
Virtual Desktop 1.34.2
EA WRC - Version 2.3.1 beta VR
Windows 11 24H2

------------

NVIDIA DRIVER ADJUSTS

Let’s talk about the nvidia drivers. Some adjusts is necessary here:

Used version: 561.09

Go on Manage 3D Settings - Program Setting
Add a profile for the EA WRC, if not exist, and change:

- Texture Filtering Negative LOD bias – “Clamp” (Helps with the textures)
- Texture Filtering Quality – "High"
(High Quality is [b/RECOMMEND[/b] cost about 8% more, BUT resolve very well the textures in game)
- Vsync – “Fast” (Games running on window mode, I like to fix this config)
- Low Latency Mode – “On”
-----------

VIRTUAL DESKTOP ADJUSTS

Run the game on VDXR mode.

On the VD Quest App – Tab Streaming

• VR Graphis Quality – “ULTRA” (2688x2784 per eye) - For steamVR users try to match this resolution)
  
• VR Frame Rate – “80 fps"
  
• Decode - H264+
  
• VR Bitrate – “450 Mbps”
  
• No sharpening
  
• Gamma - "0.99"

Advanced Options (THIS ITEMS ARE IMPORTANT)

• Snapdragon Game Super Resolution – “ON” – In another games I choose OFF, but in this game it’s necessary. (Every extra performance is useful)
  
• Track controllers – “OFF” – This option disables Quest 3 Controllers and Hand Tracking inputs. – Why off? The inputs on Quest, sometimes bugs\overlap the controllers in game, and request the restart of everything.
  
• Increase color vibrance – “ON” – Helps with the color pallet in game. (GAME CHANGER)

----

ENGINE.INI - ADJUSTS

This is an extensive topic, because a lot of tweaks are necessary on this file to run this game decently. Put the codes on the file locate in:
C:\Users\XXXXXXXXXX\AppData\Local\WRC\Saved\Config\WindowsNoEditor

FOR DLSS QUALITY (310.1) - PROFILE J (10) - VD at GODLIKE - 80 FPS - FOV 88H / 78V

[/script/engine.renderersettings]
r.EyeAdaptation.LensAttenuation=0.70
r.Tonemapper.Sharpen=1.68
r.Tonemapper.GrainQuantization=0
r.Color.Mid=0.49
r.Color.Max=0.94
foliage.DitheredLOD=0
r.DefaultFeature.AntiAliasing=2
r.TemporalAAPauseCorrect=1
r.TemporalAA.Upsampling=1
r.TemporalAACatmullRom=1
r.TemporalAA.Algorithm=1
r.TemporalAA.Upscaler=1
r.PostProcessAAQuality=4
r.AntialiasingMethod=2
r.TemporalAA.Quality=3
r.TemporalAACurrentFrameWeight=0.15
r.TemporalAAFilterSize=0.15
r.TemporalAASamples=4
r.NGX.Enable=1
r.NGX.DLSS.Enable=1
r.NGX.DLSS.DilateMotionVectors=1
r.NGX.DLSS.EnableAutoExposure=1
r.NGX.DLSS.Preset=10
r.NGX.DLSS.Reflections.TemporalAA=0
r.NGX.DLSS.WaterReflections.TemporalAA=0
r.NGX.LogLevel=0
r.NGX.EnableOtherLoggingSinks=0
r.Velocity.ForceOutput=1
r.BasePassOutputsVelocity=1
r.Velocity.EnableVertexDeformation=1
r.VertexDeformationOutputsVelocity=1
niagara.CreateShadersOnLoad=1
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.FullyLoadUsedTextures=1
r.SceneColorFringeQuality=0
r.SceneColorFormat=3
r.Upscale.Quality=5
r.Upscale.Softness=0
r.BloomQuality=3
r.FastBlurThreshold=0
r.FilmGrain=0
r.SSR.Quality=1
r.SSR.MaxRoughness=0.01
r.LightShafts=0
r.TranslucentLightingVolume=0
r.TranslucencyVolumeBlur=0

----

FOR DLAA (DLSS 310.1) - VD at ULTRA - 80 FPS - FOV 78H \ 58V

(OUTDATED)

[/script/engine.renderersettings]
r.EyeAdaptation.LensAttenuation=0.70
r.Tonemapper.Sharpen=1.65
r.Color.Mid=0.49
r.Color.Max=0.94
r.Tonemapper.GrainQuantization=0
r.TemporalAA.HistoryScreenpercentage=120
r.DefaultFeature.AntiAliasing=2
r.TemporalAAPauseCorrect=1
r.TemporalAA.Upsampling=0
r.TemporalAACatmullRom=1
r.TemporalAA.Algorithm=0
r.PostProcessAAQuality=6
r.AntialiasingMethod=2
r.TemporalAA.Quality=2
r.TemporalAACurrentFrameWeight=0.15
r.TemporalAAFilterSize=0.10
r.TemporalAASamples=2
r.NGX.Enable=1
r.NGX.DLAA.Enable=true
r.NGX.LogLevel=0
r.NGX.EnableOtherLoggingSinks=0
r.TemporalAA.Upscaler=1
niagara.CreateShadersOnLoad=1
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.FullyLoadUsedTextures=1
r.SceneColorFringeQuality=0
r.SceneColorFormat=3
r.Upscale.Quality=5
r.Upscale.Softness=0
r.BloomQuality=2
r.FastBlurThreshold=0
r.FilmGrain=0
r.TranslucencyVolumeBlur=0
r.SSR.Quality=1
r.SSR.MaxRoughness=0.01

----

FOR FSR 2 - VD at GODLIKE - 80 FPS - NO FOV ADJUST

(NEWER!)

[/script/engine.renderersettings]
r.EyeAdaptation.LensAttenuation=0.70
r.Tonemapper.Sharpen=2.20
r.Tonemapper.GrainQuantization=0
r.Color.Mid=0.49
r.Color.Max=0.94
foliage.DitheredLOD=0
r.DefaultFeature.AntiAliasing=2
r.TemporalAAPauseCorrect=1
r.TemporalAA.Upsampling=1
r.TemporalAACatmullRom=1
r.TemporalAA.Algorithm=1
r.PostProcessAAQuality=4
r.AntialiasingMethod=2
r.TemporalAA.Quality=3
r.TemporalAACurrentFrameWeight=0.20
r.TemporalAAFilterSize=0.15
r.FidelityFX.FSR2.Enabled=1
r.Velocity.ForceOutput=1
r.BasePassOutputsVelocity=1
r.BasePassForceOutputsVelocity=1
r.VelocityOutputPass=1
r.Velocity.EnableVertexDeformation=1
r.VertexDeformationOutputsVelocity=1
r.Velocity.EnableLandscapeGrass=1
r.FidelityFX.FSR2.ForceVertexDeformationOutputsVelocity=1
r.FidelityFX.FSR2.HistoryFormat=0
r.FidelityFX.FSR2.AutoExposure=0
r.FidelityFX.FSR2.AdjustMipBias=0
r.FidelityFX.FSR2.CreateReactiveMask=1
r.FidelityFX.FSR2.DeDither=1
r.FidelityFX.FSR2.UseSSRExperimentalDenoiser=1
r.FidelityFX.FSR2.ReactiveMaskReflectionScale=1
r.FidelityFX.FSR2.ReactiveMaskReflectionLumaBias=1
r.FidelityFX.FSR2.ReactiveMaskRoughnessScale=0.60
r.FidelityFX.FSR2.ReactiveMaskTranslucencyBias=1
r.FidelityFX.FSR2.ReactiveMaskTranslucencyLumaBias=1
r.FidelityFX.FSR2.ReactiveHistoryTranslucencyBias=0.0
r.FidelityFX.FSR2.ReactiveHistoryTranslucencyLumaBias=0.0
r.FidelityFX.FSR2.ReactiveMaskPreDOFTranslucencyScale=0
r.FidelityFX.FSR2.ForceLandscapeHISMMobility=1
r.TemporalAASamples=8
niagara.CreateShadersOnLoad=1
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.FullyLoadUsedTextures=1
r.SceneColorFringeQuality=0
r.SceneColorFormat=3
r.Upscale.Quality=5
r.Upscale.Softness=0
r.BloomQuality=2
r.FastBlurThreshold=0
r.FilmGrain=0
r.SSR.Quality=1
r.SSR.MaxRoughness=0.01
r.LightShafts=0
r.TranslucentLightingVolume=0
r.TranslucencyVolumeBlur=0

----

IN GAME ADJUSTS:

VR Settings
3D Location Reveal – “OFF” breaks a lot the loading in the gameplay
Fixed Horizon – “OFF” – Definitely.

Custom Hidden Area Mask (HIGHLY NECESSARY – FOR ALL GPUs)

• Area Mask X Offset “minus 12” and Y Offset “positive 6” – Because we are cutting the render area is necessary to Adjust the position of the “visible area” on the lens
  
• Area Mask Width – “78” – Cut the Image render on horizontal
  
• Area Mask Height – “58” – Cut the Image render on vertical

These items reduce a lot the FOV; the values are aggressive, but is necessary for performance. And reducing the vertical FOV don’t take too much immersion in rally games.


Sound Settings
For who uses the default speakers in Quest 3, go in sound profile in game and enable
the night mode for better audio immersion, works very well. You can listen the tires, the surface and weaks sounds way better. Give a try.


Brightness Setting
0.50 for Quest 3, (HEAVY RECOMMENDED for the eye-adaption value in engine.ini and Gamma value in VD Quest App)


Basic Setting

• Resolution – 1280 x 720
  
• Display Mode – Windowed
  
• AA Quality – Low
  
• Anisotropic Filtering – 4x (night and rain) and 8x (for dry)
  
  
• Foveated Rendering Strength – “2” – 3 for MORE performance available, BUT remove too much details from the textures.
  
  
• (IMPORTANT) Upscaler – Set according to the engine.ini profile. Recommend restart the game after do a change. The DLAA engine.ini will overlap this option.

Advanced Settings
GENERAL SPECIFICATIONS

Shadows – “High" (works better in the most scenes, create less drawcalls. Ultra is too expensive in ALL scenarios)

Fog – “On”

Particles (CPU DEMAND) – “Ultra” - Because the heavy rain is very annoying on High.

Weather – “High” - Ultra give some extra effects on Rain \ Snow weather.

Crowd (CPU DEMAND) – “Ultra” -

Ground Cover – “Medium” (High \ Ultra is very demmanding on GPU)

Trees – “High" - Ultra is heavy and will bring stutterings

Dynamic Objects – “High” - (Ultra works better if you have a lot of headroom, because create less drawcalls, but drops the fps a lot in some heavy moments.

Post Processing - "Ultra-low" for anthying below 4080 or High for 4080 / 4090. (Obs: Low or medium performes worse in every scene on NVIDIA GPU)

Car Reflections – “Ultra-low" - DON'T CHANGE THAT!

Mirrors – “Off”

Track – “Medium" – adjust the complexity of the objects on scene (cars, build, barracs, rocks, road, etc..)

Textures – “Ultra" for 16 GB of VRAM \ "High" for 12 GB of VRAM.

Shaders – “Medium"

GPU	3080Ti \ 3090 \ 4070Ti \ 4080	4090 DLSS QUALITY GODLIKE OR 7900XTX FSR GODLIKE
FPS	72	80
FOV	78(H) - 58(V)	88(H) - 78(V) NVIDIA NO FOV ADJUST TO AMD
Shadow	Medium	Medium
Fog	On	On
Particles (CPU)	High	High
Weather	Medium/High	High/Ultra
Crowd	Medium/High	Ultra
GroundCover	Low/Medium	Medium/High
Trees	Medium	High
Dynamic Objects	Medium/High	High
Car Reflection	Ultralow	Ultralow
PostProcessing	Ultralow	High
Mirrors (CPU)	Off	Off
Track	Low\Medium	Medium
Textures	High	Ultra
Shader	Medium	Medium/High

[Wilck]

Αναρτήθηκε αρχικά από Cruisix:

Αναρτήθηκε αρχικά από Wilck:

Guide updated.
Apparently preset=11 for profile K. But both are really identical. At 11 I can see a little less ghosting, but is minimal in DLSS Auto Mode.

But DLSS Quality at the profile K, yeah is a BIG improvement! Despite the AA in the small objects like (fences or road signs) is very playable!

DLSS 310.2 in Quality mode will demands more stronger AA.
Other thing: The AA profile in game, now, don't ♥♥♥♥ up the image anymore, EPIC is recommend.

Ok. Did some runs. I am staying at the settings you described for 310.2 in DLSS Auto and upping some of the sharpness like before as I found the distance becomming more blurry again. I'll take that little bit of shimmering as the rest is just so much better now.

This new version of DLSS have this little problem, a little shimmering on medium\high distance and even at the road.

I suppose that they ignore the TAA in profile, but I need to do a more deep search about that.

Guys about the reccomendation for DLSS at Quality, its runs OK, a little too shimmering, but its playable. So maybe in others headsets less demands for resolution will be fine.

But for the Quest 3, DLSS Auto MODE ON still the best option for clarity.

[Wilck]

Αναρτήθηκε αρχικά από HUNTY:

Αναρτήθηκε αρχικά από Westindiman:

I have Pico4 and though I mainly use my Reverb G2 and play with WRC v1.8 (I dont use my Reverb with the later updates due to issues so I have 2 folders), I have tried the update with my Pico4 without issues other the stutters when the I get into the car to start a time trial and its crashes out every 2-3 runs. I am using PCVR with USB and gnirehtet. I will check my settings later.

Yeah that checks out, it doesn't crash for me, however it's unplayable. I play wired with link cable as well.
72hz (in streaming assistant and also in the headset settings)
Super definition
AVC
Frame buffering and ASW on
Bitrate 200 (I lowered it from 300 and thought I solved it, but FPS drops anyway)
video super resolution off

I get 60 fps at best on these settings.

This HW will be plenty of enough to run the game, maybe not with Post Processing at HIGH, but if you drop the FOV, probably will run very well.

Your CPU either, is plenty enough.

But this game have various "mini tweaks" to achieve a good performance.

Give a look with more careful at the guide, maybe you find something.

[Amuse]

For the longest time, struggling with performance and just barely sustaining reprojected 60fps, I was hesitant about disabling hyperthreading because I wasn't sure what performance impact it would have in other tasks..

But I finally gave it a shot today, along with DLSS4 preset 11 and set to Quality ingame and literally night and day difference.

12700k/4080Super/Index, previously at 120% render res, medium-ish settings, was getting occasional dips under 60fps but still somewhat playable.

Now with hyperthreading disabled and all of that, 200% render res and almost maxed out settings and it was a rock solid 60fps the entire time.

Very similar improvement (with a bit lower ingame settings) before and after disabling hyperthreading on my laptop as well, which has a 14900hx/4070.

If anyones still struggling with performance, give that a shot, its worth it! And thank you so much for the guide!

[EAX]

Havent tried disabled HT for quite some time, last time i did it the game was still shaderstuttering anyways.
But i can just imagine how it ramps up 1% framerate performance.

Guess i may recheck that one later aswell.
As of now im quite happy with the performance i got.
I should be somewhere in the 50-65fps range its not entirely smooth but very well playable on almost maxed out settings (shadows and post processing high, mirrors and reflections off) with the 310.2 profile 11 and DLSS Quality.

ASW literally is a no go, it ruins the fresh gained imageclarity from dlss tweaks, totaly not worth a smoother picture for me atleast.

[Wilck]

Αναρτήθηκε αρχικά από EAX:

Havent tried disabled HT for quite some time, last time i did it the game was still shaderstuttering anyways.
But i can just imagine how it ramps up 1% framerate performance.

Guess i may recheck that one later aswell.
As of now im quite happy with the performance i got.
I should be somewhere in the 50-65fps range its not entirely smooth but very well playable on almost maxed out settings (shadows and post processing high, mirrors and reflections off) with the 310.2 profile 11 and DLSS Quality.

ASW literally is a no go, it ruins the fresh gained imageclarity from dlss tweaks, totaly not worth a smoother picture for me atleast.

ASW is awful in this game. I cannot use to. But I think that you'll be able to extract more frames... It's too low for your GPU.

HT OFF is almost a requeriment. The framepace changes a LOT.

Tell me, do you reduce the FOV in the VR section in game? It's necessary even for the 4090... :/

Another tips:
Fovoated Rendering - Off or 1 is very aggressive for this card. Leave at 2.

Ground Cover - High is heavy and have big impact in performance. Leave at Medium.

[HUNTY]

Αναρτήθηκε αρχικά από Westindiman:

Have you tried Virtual Desktop? A few months back I thought Connect gave me a better performance but now I have tried VD again that is giving me better performance in the Pico while streamer crashes before I can get any drive. I just did 2 runs, the first I was a fraction of a second off the time trial I was trying to beat, second attempt I was 6 seconds up then it crashed and I couldn't be bothered to load it again to check my settings.

I only use wired and afaik VD can't be used wired. But I've been wondering if VD was better than Connect.

Αναρτήθηκε αρχικά από Wilck:

What the real resolution that you are trying to play?

I think around 2700x2700.

I realized though that I had an overlay running (similar to OVR toolkit), and for some reason that doubled the GPU load ONLY in WRC. I closed that overlay and suddenly GPU load is way less... now it seems to work on DLSS auto with your settings. That was fun to troubleshoot... I'll stick to 72hz, it still can't seem to handle 90.

[Mars]

I implemented these changes in Engine.ini, in addition to the render changes from OP here. Did not seem to have any negative effect. It primarily focuses on CPU optimizations. If anyone else wants to try it out to help confirm if there is any positive effect. I did not test the additional vars from the comments though, will most likely test them as well.
https://www.reddit.com/r/HarryPotterGame/comments/11bbi72/cpu_usage_env_vars_tweaks_to_eliminate_some/

[Westindiman]

Αναρτήθηκε αρχικά από HUNTY:

Αναρτήθηκε αρχικά από Westindiman:

I only use wired and afaik VD can't be used wired. But I've been wondering if VD was better than Connect.

You can use VD wired, as Ive mentioned I use gnirehtet, look it up

[EAX]

Αναρτήθηκε αρχικά από Wilck:

Αναρτήθηκε αρχικά από EAX:

Havent tried disabled HT for quite some time, last time i did it the game was still shaderstuttering anyways.
But i can just imagine how it ramps up 1% framerate performance.

Guess i may recheck that one later aswell.
As of now im quite happy with the performance i got.
I should be somewhere in the 50-65fps range its not entirely smooth but very well playable on almost maxed out settings (shadows and post processing high, mirrors and reflections off) with the 310.2 profile 11 and DLSS Quality.

ASW literally is a no go, it ruins the fresh gained imageclarity from dlss tweaks, totaly not worth a smoother picture for me atleast.

ASW is awful in this game. I cannot use to. But I think that you'll be able to extract more frames... It's too low for your GPU.

HT OFF is almost a requeriment. The framepace changes a LOT.

Tell me, do you reduce the FOV in the VR section in game? It's necessary even for the 4090... :/

Another tips:
Fovoated Rendering - Off or 1 is very aggressive for this card. Leave at 2.

Ground Cover - High is heavy and have big impact in performance. Leave at Medium.

Yes i have cut the FOV, i did cut a little bit in between both lenses where my nose is at because that part is least noticeable and i cut the horizontal bottom side a bit, could get more and act like simulating a helmet in order to keep immersion but im fine with it right now.

Foveated is at 3.
I also thought about reducing ground cover or trees but it takes away alot of detail and may cause more flickering due to lower detailed foliage

Edit:

So i use Area Mask X Offset 7, Mask Y Offset -18, Mask Width 86 and Mask Height 90

And i also gave Hyperthreading Off a shot but honestly i do not notice a improvement anymore.
According to my OSD of the Oculus Debug Tool im constantly running at 45Hz inside the car and outside it easily can catch up to 90 Hz Refreshrates.
That said its smooth enough for me to be enjoyed, the only thing that is annoying are any kind of reflection or dirt effects on the windshield, they are ghosting and from a graphical perspective they suck without any use inside the game files.

[Jevvy]

First ever post on Steam forums to say thanks for this guide - took some getting my head around but once everything was dropped into the right place the results are very impressive compared to how it was out of the box.

Thanks @wilk ;)

[Wilck]

Αναρτήθηκε αρχικά από Jevvy:

First ever post on Steam forums to say thanks for this guide - took some getting my head around but once everything was dropped into the right place the results are very impressive compared to how it was out of the box.

Thanks @wilk ;)

I'm glad, thank you.

[Wilck]

Αναρτήθηκε αρχικά από EAX:

Yes i have cut the FOV, i did cut a little bit in between both lenses where my nose is at because that part is least noticeable and i cut the horizontal bottom side a bit, could get more and act like simulating a helmet in order to keep immersion but im fine with it right now.

Foveated is at 3.
I also thought about reducing ground cover or trees but it takes away alot of detail and may cause more flickering due to lower detailed foliage

Edit:

So i use Area Mask X Offset 7, Mask Y Offset -18, Mask Width 86 and Mask Height 90

And i also gave Hyperthreading Off a shot but honestly i do not notice a improvement anymore.
According to my OSD of the Oculus Debug Tool im constantly running at 45Hz inside the car and outside it easily can catch up to 90 Hz Refreshrates.
That said its smooth enough for me to be enjoyed, the only thing that is annoying are any kind of reflection or dirt effects on the windshield, they are ghosting and from a graphical perspective they suck without any use inside the game files.

What CPU do you have? Seems problems in other fronts.

[DannyDan]

Strange, I am not getting it to work in VR with the new DLSS dll. I still have better performance when using Fidelity FX instead of DLSS. When running in flat, I can see via DLSS indicator, that the new DLSS Version is used, but I don't see the indicator when running in VR so I am not sure that its working.
When trying ACC with the new DLSS Version, I instantly recognized, that its in use, because the performance is so much better now.

[HUNTY]

completely insane... i manage to get this ♥♥♥♥ fixed in vr, then the next day I try to play on THE SAME SETTINGS I can't get 72 fps anymore and my GPU usage is capped at 100%...
so ♥♥♥♥♥♥♥ tired...

[Wilck]

Αναρτήθηκε αρχικά από DannyDan:

Strange, I am not getting it to work in VR with the new DLSS dll. I still have better performance when using Fidelity FX instead of DLSS. When running in flat, I can see via DLSS indicator, that the new DLSS Version is used, but I don't see the indicator when running in VR so I am not sure that its working.
When trying ACC with the new DLSS Version, I instantly recognized, that its in use, because the performance is so much better now.

Yeeh, is for that situations, that I reccomend swap the file in the game folder. Resolves the uncertainty about the DLSS use, and about which profile is used either because it's selected by engine.ini .