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]

Origineel geplaatst door Corrie:

I'm playing on a 4090 a 7800x3d so it's running fairly well but some stages, I think ones with big crowds, still drop the FPS below 90 pretty often. Is there a setting or two you recommend to lower that gives the best bang for the buck performance wise even on a high end rig?

Hard to know, First you need to find where is the drop. Because you have a 7800x3D and it will capable to run at 90 fps (I had tested) I supposed that is on GPU side.

The 4090 don't have enough headroom to run this game on (Ultra: 2688x2784) with the presets on the guide, without cut the FOV.

The guide target for 80 fps, runs on limit in hard performance stages (ex. Japan in rain at night). In light stages stays about 85% of GPU usage.

For 90 fps or don't cut the FOV, I suggest to lower the preset on this sequence:
Shadow - Medium
Track - Low
Trees - Medium
Ground Cover - Low
Dynamic Objects - HIgh (Medium create too many POP-IN in open stages)
Shader - High \ Medium

And for last (free about 15 a 20% of performance)
PostProcessing - Ultra Low (because the LOW, or MEDIUM runs worse than HIGH)

But personally I prefer to cut the FOV, or run in 80 (mainly the vertical FOV - 65 \ 70, that don't really affect the experience) than reduce the quality presets because the game looks ugly without Shader in Ultra and PostProcessing in High...

[Corrie]

Origineel geplaatst door Wilck:

Origineel geplaatst door Corrie:

I'm playing on a 4090 a 7800x3d so it's running fairly well but some stages, I think ones with big crowds, still drop the FPS below 90 pretty often. Is there a setting or two you recommend to lower that gives the best bang for the buck performance wise even on a high end rig?

Hard to know, First you need to find where is the drop. Because you have a 7800x3D and it will capable to run at 90 fps (I had tested) I supposed that is on GPU side.

The 4090 don't have enough headroom to run this game on (Ultra: 2688x2784) with the presets on the guide, without cut the FOV.

The guide target for 80 fps, runs on limit in hard performance stages (ex. Japan in rain at night). In light stages stays about 85% of GPU usage.

For 90 fps or don't cut the FOV, I suggest to lower the preset on this sequence:
Shadow - Medium
Track - Low
Trees - Medium
Ground Cover - Low
Dynamic Objects - HIgh (Medium create too many POP-IN in open stages)
Shader - High \ Medium

And for last (free about 15 a 20% of performance)
PostProcessing - Ultra Low (because the LOW, or MEDIUM runs worse than HIGH)

But personally I prefer to cut the FOV, or run in 80 (mainly the vertical FOV - 65 \ 70, that don't really affect the experience) than reduce the quality presets because the game looks ugly without Shader in Ultra and PostProcessing in High...

Thanks, I'm using an Index so I don't think I can target 80fps and I was really trying to get away without adjusting the FOV but maybe it's worth a try if the benefit outweights the downside. Thanks again for the info.

[DmAnd]

If you have a Index, you might be better off using a much higher refresh rate and then targeting the reprojection ratio.
So if you set your index to 144hz, you could then target 72fps

That is what i do with my Q3 because the game feels very bad even with a consistent 90 fps.
Solution for me was to stick my q3 to 120hz mode and now i have a much smoother feeling and looking 60 fps.

It is strange because both DR2 VR and EA WRC VR feel loke a choppy mess at lower hz rates. For DR2 it was the low framerate of the steering wheel and windshield wipers that make the game feel choppy at a cinsistent VR framerate.
EA WRC has vastly improved in this department but 60 fps ratio is needed for some reason.

Now it is smooth like butter at 60 reprojected into 120. Much smoother then a 72,80, or 90 framerate with asw on or off

[Lucash eLSamuell]

Origineel geplaatst door DmAnd:

If you have a Index, you might be better off using a much higher refresh rate and then targeting the reprojection ratio.
So if you set your index to 144hz, you could then target 72fps

That is what i do with my Q3 because the game feels very bad even with a consistent 90 fps.
Solution for me was to stick my q3 to 120hz mode and now i have a much smoother feeling and looking 60 fps.

It is strange because both DR2 VR and EA WRC VR feel loke a choppy mess at lower hz rates. For DR2 it was the low framerate of the steering wheel and windshield wipers that make the game feel choppy at a cinsistent VR framerate.
EA WRC has vastly improved in this department but 60 fps ratio is needed for some reason.

Now it is smooth like butter at 60 reprojected into 120. Much smoother then a 72,80, or 90 framerate with asw on or off

Thats interesting, i will look in to this, not for this game but overal. Did you try that in non-sim games?. Like shooters etc thanks

[Wilck]

Origineel geplaatst door DmAnd:

If you have a Index, you might be better off using a much higher refresh rate and then targeting the reprojection ratio.
So if you set your index to 144hz, you could then target 72fps

That is what i do with my Q3 because the game feels very bad even with a consistent 90 fps.
Solution for me was to stick my q3 to 120hz mode and now i have a much smoother feeling and looking 60 fps.

It is strange because both DR2 VR and EA WRC VR feel loke a choppy mess at lower hz rates. For DR2 it was the low framerate of the steering wheel and windshield wipers that make the game feel choppy at a cinsistent VR framerate.
EA WRC has vastly improved in this department but 60 fps ratio is needed for some reason.

Now it is smooth like butter at 60 reprojected into 120. Much smoother then a 72,80, or 90 framerate with asw on or off

I had tried.. But ASW in this game create a lot of input lag... I can't enjoy.

[DmAnd]

Origineel geplaatst door Lucash eLSamuell:

Origineel geplaatst door DmAnd:

If you have a Index, you might be better off using a much higher refresh rate and then targeting the reprojection ratio.
So if you set your index to 144hz, you could then target 72fps

That is what i do with my Q3 because the game feels very bad even with a consistent 90 fps.
Solution for me was to stick my q3 to 120hz mode and now i have a much smoother feeling and looking 60 fps.

It is strange because both DR2 VR and EA WRC VR feel loke a choppy mess at lower hz rates. For DR2 it was the low framerate of the steering wheel and windshield wipers that make the game feel choppy at a cinsistent VR framerate.
EA WRC has vastly improved in this department but 60 fps ratio is needed for some reason.

Now it is smooth like butter at 60 reprojected into 120. Much smoother then a 72,80, or 90 framerate with asw on or off

Thats interesting, i will look in to this, not for this game but overal. Did you try that in non-sim games?. Like shooters etc thanks

Normally i run things at 90 or 120 but more demanding games i tend to leverage the higher refresh rate and reprojection tech rather than turn down graphics settings.

Games like No Mans Sky VR and this game here really benefit from it in my opinion. It is the only way i can get the steering wheel animation to look smooth.

I tried running EA WRC at the native 72,80, 90hz rates, i turn down a lot of settings to make sure i can hold the desired framerate and it just feels horrible, the steering wheel animation and things flying by while driving just look so choppy.

Other sims are fine at lower refresh rates. AMS2, AC, ACC. I don't need to use ASW with those and it all looks nice and smooth.
It is something in the design of both Dirt Rally and EA WRC. I don't see it mentioned very often so maybe it is something on my end.

[BrokeBassTurd]

looks great but i can only see out of one lense. both works fine up until stage preview where it seems like i get my right lense shut off and then once im in the stage the same thing, anytime i am able to move my head around with the engine.ini settings. anyone able to help?

[Corrie]

Origineel geplaatst door BrokeBassTurd:

looks great but i can only see out of one lense. both works fine up until stage preview where it seems like i get my right lense shut off and then once im in the stage the same thing, anytime i am able to move my head around with the engine.ini settings. anyone able to help?

I think you're running into this

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

[Corrie]

I decided to upgrade my 7800x3d to the new 9800x3d. I'm curious how it will improve this game. I will report back once I receive it.

[pixelcowboy79]

Origineel geplaatst door Corrie:

I decided to upgrade my 7800x3d to the new 9800x3d. I'm curious how it will improve this game. I will report back once I receive it.

Very likely minimal, perhaps less stutter.

[Arborea]

Origineel geplaatst door Corrie:

I decided to upgrade my 7800x3d to the new 9800x3d. I'm curious how it will improve this game. I will report back once I receive it.

10-20 fps increase.

[pixelcowboy79]

Origineel geplaatst door Arborea:

Origineel geplaatst door Corrie:

I decided to upgrade my 7800x3d to the new 9800x3d. I'm curious how it will improve this game. I will report back once I receive it.

10-20 fps increase.

In flat, maybe. In VR, no way. 5-10 is probably even overly optimistic. But stability might be greatly improved.

[Wilck]

Origineel geplaatst door Corrie:

I decided to upgrade my 7800x3d to the new 9800x3d. I'm curious how it will improve this game. I will report back once I receive it.

I don't think you will get any improvement.. =\ . The 7800x3D is strong enough to run this game at 120 fps without get 100% on the render cores.

Maybe something with the microsutters? Hard to say... More easily get more problems, with newest BIOS, bugs, lack of adjustments on launch...

But let's get optmistic, will be better!

[oJJoJoe]

just try it with this graphics guide instead, runs butter smooth...

[Wilck]

Origineel geplaatst door oJJoJoe:

just try it with this graphics guide instead, runs butter smooth...

This guide is very old and not updated anymore. I had see and tested it in the past.

Some commands are useful, but some of them, now create more problems than solutions.