Serious issue with Deferred Shading Colours and Detail

[imacken]

I have got major issues when Deferred Shading is switched on. Colours are horribly over saturated, and the lack of detail on some terrains and all cockpits is very striking.

At the moment, I am sticking to DS off. Everything is much more natural and real!

However, there are issues with that as well, with MFD and a few cockpit dials. (See attached for black square on map and missing dials on gauges.)

See attached for a couple of examples, but there many others! You could say increase gamma to resolve things like the A-10C attachment. Yes, that improves things in that case, but then makes a whole load of other scenarios overly bright and washed out!

[kreisch]

Did you try and deleted the shaders inside the saved games folder?

Or also deleted the whole folder (save your controls) and tried if it is the same?

 

Gesendet von meinem F5121 mit Tapatalk

[outlawal2]

Everyone keeps talking about a "Saved Games" folder to delete and for the life of me I cannot find this folder anywhere.. What is the complete FULL path to this folder? (And for the record I think 2.5 looks awesome and the immersion in VR flying a helicopter is amazing, but I am having a few issues with colors and such.. Example is looking over the sea at distance the water looks brown rather than blue)

[mhe]

Everyone keeps talking about a "Saved Games" folder to delete and for the life of me I cannot find this folder anywhere.. What is the complete FULL path to this folder? (And for the record I think 2.5 looks awesome and the immersion in VR flying a helicopter is amazing, but I am having a few issues with colors and such.. Example is looking over the sea at distance the water looks brown rather than blue)

 

Open Windows Explorer (Win+E), the left bar should show you a tree of things. One folder should be a folder named just like your windows user. Double click on it. A subfolder of your User folder should be called "Saved Games". It contains a DCS.openbeta folder (or just DCS if you updated your 1.5.8 final to 2.5 Openbeta). In there is a folder called metashaders. Delete or rename it. Reload DCS, suffer the longer loading time only once and pretty much all the shading stuff should be fixed apart from weird discoloration in fog.

[imacken]

I have a similar impression concerning saturation with DS enabled. Contrast is also very harsh. Switched back to non-DS but don't have any problems with cockpit gauges.

The cockpit gauge issue is only on the Spit that I’ve noticed so far, and even then it only appears when the the sun is at a particular angle.

[Art-J]

Everyone keeps talking about a "Saved Games" folder to delete and for the life of me I cannot find this folder anywhere.. What is the complete FULL path to this folder? (And for the record I think 2.5 looks awesome and the immersion in VR flying a helicopter is amazing, but I am having a few issues with colors and such.. Example is looking over the sea at distance the water looks brown rather than blue)

 

As Mhe said, or just note down the full path: C:\Users\[your user name]\Saved Games\DCS (or DCS OpenBeta).

 

Mind you, this is the location where all your personal data about DCS is stored: controls, replays, screenshots, settings, logbook, campaign progress and whatnot, so you'll be visiting this place often. Obviously, don't just remove the whole folder - you might incidentally delete something useful. Look around in it, sub-folder names are pretty much self-explainatory.

 

Removing options.lua file in config subfolder (as per ED's clear instruction by the way) and removing contents of metashader and fxo subfolders are usually enough to fix most of DCS 2.x.x graphics issues (as doing so resets the game to default gfx state).

[Brigg]

Open Windows Explorer (Win+E), the left bar should show you a tree of things. One folder should be a folder named just like your windows user. Double click on it. A subfolder of your User folder should be called "Saved Games". It contains a DCS.openbeta folder (or just DCS if you updated your 1.5.8 final to 2.5 Openbeta). In there is a folder called metashaders. Delete or rename it. Reload DCS, suffer the longer loading time only once and pretty much all the shading stuff should be fixed apart from weird discoloration in fog.

 

Do you have to delete it every time before you launch the game?

[bolek]

No, only when you change graphics settings in the game or in the graphics driver panel.

[Brigg]

As Mhe said, or just note down the full path: C:\Users\[your user name]\Saved Games\DCS (or DCS OpenBeta).

 

Mind you, this is the location where all your personal data about DCS is stored: controls, replays, screenshots, settings, logbook, campaign progress and whatnot, so you'll be visiting this place often. Obviously, don't just remove the whole folder - you might incidentally delete something useful. Look around in it, sub-folder names are pretty much self-explainatory.

 

Removing options.lua file in config subfolder (as per ED's clear instruction by the way) and removing contents of metashader and fxo subfolders are usually enough to fix most of DCS 2.x.x graphics issues (as doing so resets the game to default gfx state).

 

is this advised to do every time you launch the game

[Art-J]

No, not at all. But it's good habit to clean up fxo and metashaders folders plus remove options.lua file after every major DCS update, which contains any gfx changes, just to "referesh" the game.

[Brigg]

ok thx

[Emmy]

Thank You to those who patiently explained what needs to happen here...

 

Did the deletions and restarted and I'm very happy with the frame rates Vs quality I'm seeing on my very average computer.

[imacken]

Really glad you got that sorted, but could we get back to the topic of the thread please?

[mkiii]

What is your gamma setting when on DS? The default seems to be set up for some freaky Apple MAc Monitor setup, not my steam powered PC, but at least that is easy to test.

 

I'm also seeing the map problem in the A-10C.

 

Have you noticed strange artifacts when viewing the exterior, like a very high frequency noise texture, that seems to consist of tiny swirl patterns when you zoom right in? It also seems to appear on the HUD lenses (& projector part of gunsights) as a strange dark speckly shadow.

 

I'm still experimenting, but it does seem that you really need to restart after tweaking any of this stuff, which can make testing a bit time consuming.

[imacken]

What is your gamma setting when on DS? The default seems to be set up for some freaky Apple MAc Monitor setup, not my steam powered PC, but at least that is easy to test.

 

I'm also seeing the map problem in the A-10C.

 

Have you noticed strange artifacts when viewing the exterior, like a very high frequency noise texture, that seems to consist of tiny swirl patterns when you zoom right in? It also seems to appear on the HUD lenses (& projector part of gunsights) as a strange dark speckly shadow.

 

I'm still experimenting, but it does seem that you really need to restart after tweaking any of this stuff, which can make testing a bit time consuming.

If the gamma is set to 2.2, then the sea is improved in Normandy, but the cockpits are washed out. If I reduce the gamma to 1.6, cockpits are OK-ish but the sea goes almost black at times in Normandy.

I effectively cannot use Deferred Shading because of the terrible colour palette in Normandy, and the poor cockpits being over saturated sometimes, under at other times.

I have also noticed a huge difference in the rendition of radar on the F-5 and more importantly, in the visibility of aircraft and tracer bullets.

Both visibility and tracer bullets as well as the radar detail in F-5 are hugely better with DS on.

This is becoming very frustrating now.

[mkiii]

I agree that the various maps do not appear to be consistant, but I have only really been experimenting with instant action missions so far, and the time of day & season on those does vary a lot, leading to some noticable differences. However, some small setting changes seem to have a large impact.

 

I have also noticed that my gamma settings seem to be a bit variable. It defaults to 2.2, which at first was completely washed out, so I set it to 1.6, which was good. Then I had to delete options.lua and gamma was back to default 2.2, but was now OK. Odd.

 

I'm getting the feeling that perhaps the shader cache might have something to do with it. We were advised that it might be necessary to delete the cache folders after all, but doing that after each tweak is going to take quite some time.

 

All that being said, I'm very pleased that this version seems to run at a decent framerate, even with settings pretty much maxed out on my trusty old GTX 970, and various shader/gfx problems tend to work themselves out as people become more familiar with the settings and report what they are using to fix things. It is still in beta after all.