Shadow Quality
- Thread starter Morbad
- Start date
It's performance impact is very low when there are no VRAM constrains, but these changes are intended for higher-end hardware and I haven't tested it on any cards with less than 10GiB of memory.
Ok ... I have 4Gb on laptop's 3050. Default high works ok though.
You're right: the game replaced the xml file with the stock one.
Thanks and sorry for not have thought to that myself.
aquilla has done some work on stripping down shadows for lower-end parts if you want to look up his posts.
You can also mix and match the settings you find in my profiles. The spot and directional shadows do not need to be set to the same quality and pretty much any power of two slice size of 16k or lower will work (and free up some VRAM).
Sorry to ask this here but is there a similar thread about graphic settings other than shadows, specific for/to Odyssey? For example settings that used to be modifiable in the override file (C:\Users\*****\AppData\Local\Frontier Developments\Elite Dangerous\Options\Graphics) outside the main GraphicsConfiguration.xml (that resides inside the C:\Program Files (x86)\Frontier\EDLaunch\Products\elite-dangerous-odyssey-64)? Any attempt to use overrides made for/from Horizons results in unreadable game menus inside the game. I find default game menus (and in some but not all cases) graphics in Odyssey not clear and sharp (or colorful/bright) like Horizons (Before it was "upgraded" to version 4.0).
For example in Space Engine I can modify its graphics by tweaking some (tone/color mapping?) values from within the app itself as shown here: (otherwise found in external post effect-injector apps like re-shade which I really DON'T want to use on top of a running instance of Elite
angerous Odyssey) :
I already know about the NVidias Graphics Drivers Sharpening settings:
But I want more control just like Space Engine's internal graphics settings BUT without the need to use ReShade or Nvidia GForce Experiments.
Thanks and sorry for long post.
For example in Space Engine I can modify its graphics by tweaking some (tone/color mapping?) values from within the app itself as shown here: (otherwise found in external post effect-injector apps like re-shade which I really DON'T want to use on top of a running instance of Elite
angerous Odyssey) :Thanks and sorry for long post.
That's my 3.8 Horizons GraphicsConfigurationOverride.xml
And this is how the game looks with this override, both on menu and in-game (completely black):
On main menu:
In Game:
And these are with the default Odyssey (i.e. empty) Override: (both main menu and in-game:
Code:
<?xml version="1.0" encoding="UTF-8" ?>
<GraphicsConfig>
<HDRNode_Reference>
<PrototypeLightingBalancesEnabled>0</PrototypeLightingBalancesEnabled>
<UseCompute>0</UseCompute>
<ExposureType>0</ExposureType>
<GlareCompensation>0.75</GlareCompensation>
</HDRNode_Reference>
<GUIColour>
<Default>
<LocalisationName>Standard</LocalisationName>
<MatrixRed> 1, 0.15, 0 </MatrixRed>
<MatrixGreen> 0, 1, 0.85 </MatrixGreen>
<MatrixBlue> 0, 0, 1 </MatrixBlue>
</Default>
</GUIColour>
<HBAO>
<High>
<RadiusInMeters>8.4</RadiusInMeters>
<NearRadiusInMeters>4.2</NearRadiusInMeters>
<NearDistance>200.0</NearDistance>
<PowExponent>2.0</PowExponent>
<Bias>0.4</Bias>
<BlurSharpness>3.0</BlurSharpness>
</High>
</HBAO>
<SSAO>
<High>
<Enabled>false</Enabled>
</High>
</SSAO>
<Planets>
<Ultra>
<TextureSize>8192</TextureSize>
<WorkPerFrame>512</WorkPerFrame>
</Ultra>
</Planets>
<GalaxyBackground>
<High>
<TextureSize>5632</TextureSize>
</High>
</GalaxyBackground>
<Bloom>
<Ultra>
<GlareScale>0.045</GlareScale>
<FilterRadius>0.8</FilterRadius>
<FilterRadiusWide>4.5</FilterRadiusWide>
</Ultra>
</Bloom>
<Envmap>
<High>
<TextureSize>1024</TextureSize>
<NumMips>10</NumMips>
</High>
</Envmap>
<GalaxyMap>
<High>
<HighResNebulasCount>4</HighResNebulasCount>
<LowResNebulaDimensions>128</LowResNebulaDimensions>
<HighResNebulaDimensions>512</HighResNebulaDimensions>
<LowResSamplesCount>64</LowResSamplesCount>
<HighResSamplesCount>96</HighResSamplesCount>
<MilkyWayInstancesCount>24000</MilkyWayInstancesCount>
<MilkywayInstancesBrightness>0.75</MilkywayInstancesBrightness>
<MilkywayInstancesSize>0.75</MilkywayInstancesSize>
<StarInstanceCount>12000</StarInstanceCount>
</High>
</GalaxyMap>
<Volumetrics>
<Ultra>
<BlurSamples>3</BlurSamples>
</Ultra>
</Volumetrics>
</GraphicsConfig>On main menu:
Of your HDRNode_Reference settings, only GlareCompensation is likely to work, and that may have a different optimal value. Setting UseCompute=0 is likely the cause for the black screen.
HBAO and Bloom have changed to the point that setting the same values is likely to produce a different effect, so those settings should be reevaluated.
SSAO hasn't been parsed in either Horizons or Odyssey in years and any settings related to it can be omitted.
The rest of your settings should be fine.
From HDRNode_Reference settings, I left only <GlareCompensation>1.00</GlareCompensation>. All other modifications were causing severe lighting issues.
I removed HBAO and Bloom completely as I observed completely different values on the default GraphicsConfiguration.xml
SSAO also removed. All remaining modifications were left. From 1st glance everything looks fine. But further testing is required. That will be for another day. Thanks a lot.
StefanOS
Volunteer Moderator
Hello I am new to this thread but very interested in what can be done with this file.
Why is it recomanded to set SHADOWS to LOW for this settings?
Morbad's custom settings are applied to the 'low' setting on the basis that anyone wanting extra pretty may want to compare to the standard ultra but probably doesn't have much use for the standard low settings so they are replaced.
Also, spot shadow quality controls a rather intensive smoke shader. Using the low preset here lets me get better quality shadows than ultra, often with better performance than ultra.
I personally have extreme difficulty seeing the difference between the different smoke shaders, so there is almost no reason for me to want to use it.
StefanOS
Volunteer Moderator
So if I use LOW - after using your files - the engine reads your settings for the specific effect (spot shadow) at LOW instead of what FD had set as LOW?
Must all GFX settigs in EDO be set specific then to get the better effects?? Or are the changes effecting all settings and all values?
Did you do the changes on all settings to LOW maybe? So anyone can switch between the suggested setting and FD settings?
Last edited:
The only thing these alterations change are spot and directional shadows, yes.
I suppose it's possible. I'm using 16k slice sizes which might not play nice with two viewports on some cards.
What GPU is this?
I suggest trying 2D to rule out some other issue, then try reducing all "16384" slice and atlas sizes to "8192".
3090 ti
%s/16384/8192/ = 6 substitutions on 6 lines.
Unfortunately it crashed again. But that's okay I guess I can live with the normal way they do it.
2D or VR?