VR Users - START GUIDE

[Wilck]

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

- 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 +280 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
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 AUTO MODE ON (310.1) PROFILE J (10)

[/script/engine.renderersettings]
r.EyeAdaptation.LensAttenuation=0.70
r.Tonemapper.Sharpen=1.68
r.Color.Mid=0.49
r.Color.Max=0.94
r.Tonemapper.GrainQuantization=0
r.TemporalAA.HistoryScreenpercentage=115
r.DefaultFeature.AntiAliasing=2
r.TemporalAAPauseCorrect=1
r.TemporalAA.Upsampling=0
r.TemporalAACatmullRom=1
r.TemporalAA.Algorithm=0
r.PostProcessAAQuality=3
r.AntialiasingMethod=2
r.TemporalAA.Quality=2
r.TemporalAACurrentFrameWeight=0.15
r.TemporalAAFilterSize=0.10
r.TemporalAASamples=2
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=2
r.FastBlurThreshold=0
r.FilmGrain=0
r.TranslucencyVolumeBlur=0
r.SSR.Quality=1
r.SSR.MaxRoughness=0.01

----

FOR DLAA (DLSS 310.1 version)

[/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=125
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

----

IN GAME ADJUSTS:

And finally, the in game adjusts. I made changes in 2 fronts here. VR Settings and Graphics config.


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 – Double check the DLSS ON and Enable the AUTO Quality right below. (If use DLAA the 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 AUTO - GODLIKE or DLAA - ULTRA)
FPS	72	80
FOV	78(H) - 58(V)	78(H) - 58(V)
Shadow	Medium	Medium
Fog	On	On
Particles (CPU)	High	Ultra
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]

Nguyên văn bởi 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...

Probably there is any piece of software breaking your game... Disable all unnecessary apps and windows services and give a try.

[HUNTY]

Nguyên văn bởi Wilck:

Nguyên văn bởi 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...

Probably there is any piece of software breaking your game... Disable all unnecessary apps and windows services and give a try.

Yep, you're completely right.
This time it was the Moza software running on my other screen (I had to recalibrate my wheel in game because of unknown reasons)
I closed it and back to normal GPU usage and 72fps... It's so weird how sensitive this game is to random stuff...

[DannyDan]

Nguyên văn bởi Wilck:

Nguyên văn bởi 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 .

I have swapped the dll file in the game folder.

[Wilck]

Nguyên văn bởi HUNTY:

Nguyên văn bởi Wilck:

Probably there is any piece of software breaking your game... Disable all unnecessary apps and windows services and give a try.

Yep, you're completely right.
This time it was the Moza software running on my other screen (I had to recalibrate my wheel in game because of unknown reasons)
I closed it and back to normal GPU usage and 72fps... It's so weird how sensitive this game is to random stuff...

Here, I disable the second monitor, and close ALL the active windows, only keep open GPU-Z for monitoring. Not even Steam window, I start the game by the steam notification icon.

[mamamakanyuk]

I wonder if rtx 3070 and ryzen 5600 can have stable frame rate on VR? I have psvr2 headset.

I don't expect high quality, low is ok. Anyone have experience? does DLSS4 help?

[Wilck]

Nguyên văn bởi mamamakanyuk:

I wonder if rtx 3070 and ryzen 5600 can have stable frame rate on VR? I have psvr2 headset.
I don't expect high quality, low is ok. Anyone have experience? does DLSS4 help?

Maybe at 60 fps? But even that it'll be tought... This game is very heavy on CPU and GPU.

[EAX]

Nguyên văn bởi Wilck:

Nguyên văn bởi 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.

I use a i5 13600k and 6000MHz DDR5 Ram CL30.
I guess they have silently patched alot over the time, back then ive even noticed performance gain by disabling the E-Cores, not just in this title.

The performance my CPU pushes out is fine for me, i could just need a new GPU.

[Wilck]

Nguyên văn bởi EAX:

Nguyên văn bởi Wilck:

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

I use a i5 13600k and 6000MHz DDR5 Ram CL30.
I guess they have silently patched alot over the time, back then ive even noticed performance gain by disabling the E-Cores, not just in this title.

The performance my CPU pushes out is fine for me, i could just need a new GPU.

People over the internet says that the E-cores are problematics with this engine...

I5 13600k is a good CPU, absoluted.

But in past I had a 7600x and they don't have the performance to run this game in VR.. it's insane, I know.. with any settings and resolution, I was not able to run at 72 fps stable, when the scene got more complex, dropped a LOT.

The latest patches improved a lot the game problems (stutterings), but the game become even more heavy on CPU and GPU. So, chose and heavy stage and give a look in your core usage (not the CPU usage), look only the two main cores (renderer engine).

Maybe give you any tip.

[igb557]

This guide helped a lot, the game is finally playable on 4070 ti.

I was wondering if there is any advantage in using VD over the link cable? I've been using the cable due to charging. I have a usb c port in my desktop, I think it's 15W

[Wilck]

Nguyên văn bởi igb557:

This guide helped a lot, the game is finally playable on 4070 ti.

I was wondering if there is any advantage in using VD over the link cable? I've been using the cable due to charging. I have a usb c port in my desktop, I think it's 15W

Performance is very similar. I tried recently. The image enchancements in VD is better (smoother and colors more vibrants). Questlink have a "raw" image.

Besides that will work pretty decent in both.

[blackbern66]

Guys i spent almost half my playtime tinkering with settings and i wanna share best i could find. VD is no go for me. I never had decent picture with VD, i almost gave up with WRC. Then i started tinkering with OculusLink and my god, i found perfect settings, almost DR2.0. (4070ti super, Quest3)

MetaQuest settings: Graphic preferences:
refresh rate 72Hz,
render resolution 1.3x

Oculus debug tool:
PPD override:1.2
FOV tangent Multiplier V+H: 0.82
Encode resolution widt:4128
Dynamic bitrate:820 (i think this is not important, even if is 500)

steam launch option: -notexturestreaming

Engine.ini setting are same as in Wilck guide except r.EyeAdaptation.LensAttenuation=0.90 (link is quite dark)
Folow Wilck guide for most important setting in game:Custom Hidden Area Mask

I cannot be more happy with this setting, i have constant 72FPS in game, ocasional stutter

[Wilck]

Nguyên văn bởi blackbern66:

Guys i spent almost half my playtime tinkering with settings and i wanna share best i could find. VD is no go for me. I never had decent picture with VD, i almost gave up with WRC. Then i started tinkering with OculusLink and my god, i found perfect settings, almost DR2.0. (4070ti super, Quest3)

MetaQuest settings: Graphic preferences:
refresh rate 72Hz,
render resolution 1.3x

Oculus debug tool:
PPD override:1.2
FOV tangent Multiplier V+H: 0.82
Encode resolution widt:4128
Dynamic bitrate:820 (i think this is not important, even if is 500)

steam launch option: -notexturestreaming

Engine.ini setting are same as in Wilck guide except r.EyeAdaptation.LensAttenuation=0.90 (link is quite dark)
Folow Wilck guide for most important setting in game:Custom Hidden Area Mask

I cannot be more happy with this setting, i have constant 72FPS in game, ocasional stutter

Nicee!!
"r.EyeAdaptation.LensAttenuation=0.90 (link is quite dark)" - Good Tip.
"Custom Hidden Area Mask" - Exactly, its impossible to run this game well without setting this.
Dynamic bitrate:820 - Try 700, maybe help you with the stutterings. The Q3 decode isn't plenty capable to use bitrates above 500, so any extra value, cost in latency and sometimes in stutterings.

[keczup]

Hello. I got 4080 Super and 9800x3d and after trying fixes from this topic I stil have problems with performance. My game is stuttering as hell no matter which settings in game I'm using including DLSS on auto or quality.

[blackbern66]

Nguyên văn bởi Wilck:

Nguyên văn bởi blackbern66:

Guys i spent almost half my playtime tinkering with settings and i wanna share best i could find. VD is no go for me. I never had decent picture with VD, i almost gave up with WRC. Then i started tinkering with OculusLink and my god, i found perfect settings, almost DR2.0. (4070ti super, Quest3)

MetaQuest settings: Graphic preferences:
refresh rate 72Hz,
render resolution 1.3x

Oculus debug tool:
PPD override:1.2
FOV tangent Multiplier V+H: 0.82
Encode resolution widt:4128
Dynamic bitrate:820 (i think this is not important, even if is 500)

steam launch option: -notexturestreaming

Engine.ini setting are same as in Wilck guide except r.EyeAdaptation.LensAttenuation=0.90 (link is quite dark)
Folow Wilck guide for most important setting in game:Custom Hidden Area Mask

I cannot be more happy with this setting, i have constant 72FPS in game, ocasional stutter

Nicee!!
"r.EyeAdaptation.LensAttenuation=0.90 (link is quite dark)" - Good Tip.
"Custom Hidden Area Mask" - Exactly, its impossible to run this game well without setting this.
Dynamic bitrate:820 - Try 700, maybe help you with the stutterings. The Q3 decode isn't plenty capable to use bitrates above 500, so any extra value, cost in latency and sometimes in stutterings.

i changed FOV multiplier in ODT even lower to 0.7 so Hidden Area Mask can be now changed to barely visible on the edges of FOV multiplier of ODT, now i am able to switch to 80Hz 1.5 render resolution and still have constant FPS, even better, so i think OTD fov is more important setting than in game:Custom Hidden Area Mask, and with 0.7 you still can see more area than yours Hidden Area Mask settings, and i need to play around about aspect ratio of X and Y tangent

[Hank from breaking bad]

These settings are a game changer. I've had this game since release and could never get good frame rates or clarity with a 13700k, 3080 on a Quest 3. With these settings I can get a steady 90fps at 100% resolution using Virtual desktop and steam VR runtime(VDXR gets much lower frames, usually in the 80s with constant stutters). Everything is now sharp and the game is finally playable. I went from being disappointed in this game to loving it and buying the DLC. Thanks for your effort OP!