Possible small fix to FPS , DIsable shadows 5 to 10 fps increase

Hi all been tinkering with the elite dangerous odyssey graphicsConfig.xml file managed to disable shadows on my game completely, this resulted in an increase of roughly 5 - 10 fps , went from around 9 - 10fps in the concourse to 15 and at times 20 , on foot in settlements the fps increase was even better at around 10 to 15 fps increase , I no longer have to use the AMD downsampling to play the game, I can share the config .

it only disables shadows when shadows are set to low , spot shadows only setting the directional light shadows (The main Star light) to off resulted in wierd glitches and only increased fps by 1 or 2 FPS , Added lower terrain quality as well as lower reflection quality, again set all terrain quality settings to low to use these settings

Note currently using AMD Athlon 3000g with integrated GPU , 12 GB ram , so your results may vary .


Some things I noticed :
the main culprit for the low fps in the concourse is all the spot lights , I count upwards of 10 to 20 in one area , when staring at a wall or with you back to the most of the lit areas your fps will sky rocket , so if there is light culling it just isn't working properly , if someone with more expertise in code injection could find a way to limit the max number of active lights this would help a lot , also to disable the reflections on the ground and all shiny surfaces as these are real fps killers .

Let me know if you encounter any errors , Make a backup of the original file incase of problems , copy the file to this location \EliteDangerous\Products\elite-dangerous-odyssey-64 , and overwrite the old file
Added new override file which you place in C:\Users\ ' your user name here' \AppData\Local\Frontier Developments\Elite Dangerous\Options\Graphics

this is just a config file so it shouldn't break anything , but if it does I take no responsibility for it so please note this entirely untested on other machines , use at your own risk .

Note this override will crash in horizons , so if you use horizons as well just delete this file or rename it before running horizons

if you encounter any weird behavior do let me know I might be able to fix it .

File link to GitHub graphicsOverride
 
Last edited:
File link to GitHub graphics config

I tried something similar a while back, though figured using the override would be more convenient as no frustums need to be added.

Your changes in the override would look something like this, for example:
XML:
<?xml version="1.0" encoding="UTF-8" ?>
<GraphicsConfig>
    <SpotShadows_Low>
        <NumCacheShadows>0</NumCacheShadows>
        <NumSpotShadows>0</NumSpotShadows>
        <CacheShadowAtlasSize>0</CacheShadowAtlasSize>
        <CacheShadowSize>0</CacheShadowSize>
    </SpotShadows_Low>
    <Shadows_Low>
        <Profile_General>
            <SliceSize>128</SliceSize>
            <NumFrustums>1</NumFrustums>
            <Frustum0>
                <EndDistance>0</EndDistance>
            </Frustum0>
        </Profile_General>
        <Profile_PlanetApproach>
            <SliceSize>128</SliceSize>
            <NumFrustums>1</NumFrustums>
            <Frustum0>
                <EndDistance>0</EndDistance>
            </Frustum0>
        </Profile_PlanetApproach>
        <Profile_PlanetSurface>
            <SliceSize>128</SliceSize>
            <NumFrustums>1</NumFrustums>
            <FrustumZeroCanBeOverridden>1</FrustumZeroCanBeOverridden>
            <Frustum0>
                <EndDistance>0</EndDistance>
            </Frustum0>
        </Profile_PlanetSurface>
        <Profile_StationInterior>
            <SliceSize>128</SliceSize>
            <NumFrustums>1</NumFrustums>
            <Frustum0>
                <EndDistance>0</EndDistance>
            </Frustum0>
        </Profile_StationInterior>
        <Profile_AsteroidField>
            <SliceSize>128</SliceSize>
            <NumFrustums>1</NumFrustums>
            <Frustum0>
                <EndDistance>0</EndDistance>
            </Frustum0>
        </Profile_AsteroidField>
    </Shadows_Low>
</GraphicsConfig>

Not 100% certain the "FrustumZeroCanBeOverridden" line is being parsed from the override. Would need to test it again.

I never did figure out how to disable the cockpit shadows and they were already looking distractingly bad with a 512 slice size. Maybe if I insert an EndDistance of zero for the cockpit as well...
 
very cool , was looking for an override , its better cause you just delete it if you encounter issues, but didnt really want to do something if I didnt understand it , anyway thanks , if you happen to know a way to override reflections that'd be great , otherwise Im gonna start messing with 3d mitgo see if I can locate the shader using hunting mode , didnt actually check for cockpit in my config , but ill take a look , in my game ive been making for fun there's an option of max active spot lights , if we could turn this number down in odyssey it'd be great , as each spot light adds extra work for gpu , usually doubling the vertices count of the object illuminated .
 
Last edited:
It is, but Frontier isn't going to almost completely disable shadows on consoles, or do any other radical graphical downgrades vs. Horizons, in order to get their new expansion to work.
Sure, my tongue was firmly in my cheek :)
That being said, maybe there is scope still for some well directed optimisations that could help significantly ..
 
AMD Athlon 3000g with integrated GPU? Purely curious - not trying to be clever - does that meet the minimum specs for Odyssey or have you managed to get it running on sub-min-spec hardware? Which would be pretty darned impressive!!

* EDIT *

Please ignore - this has already been covered … should’ve read the whole thread!
 
It is, but Frontier isn't going to almost completely disable shadows on consoles, or do any other radical graphical downgrades vs. Horizons, in order to get their new expansion to work.
I mean … they might have to … or perhaps implement custom-optimised shadow rendering for each console platform … which is one of the reasons I think continuing to optimise the PC version with the assumption that’ll somehow magically make it run fine on consoles is folly.
 
What's your opinion? Will they get acceptable performance on prev gen consoles??

I don't know that they will. I think it's within the technical capabilities of the previous gen consoles and FDev, but I suspect it's ultimately a matter of the resources they're willing to devote to keeping that market.

AMD Athlon 3000g with integrated GPU? Purely curious - not trying to be clever - does that meet the minimum specs for Odyssey or have you managed to get it running on sub-min-spec hardware? Which would be pretty darned impressive!!

It's well below minimum spec.

I mean … they might have to … or perhaps implement custom-optimised shadow rendering for each console platform.

I'm sure they have custom configuration settings tailored to each platform. However, I am highly doubtful that a clear graphical downgrade would fly. Odyssey is supposed to look better than Horizons and if it doesn't, it's going to get destroyed in critical and consumer reviews, which will seriously harm it's profitability.

If they can't, or aren't willing to, improve performance to the extent that such sacrifices aren't required, I'd bet on no release at all, rather than one that would make the PC release look pleasant.
 
AMD Athlon 3000g with integrated GPU? Purely curious - not trying to be clever - does that meet the minimum specs for Odyssey or have you managed to get it running on sub-min-spec hardware? Which would be pretty darned impressive!!
yeah its well below minimum spec , but yes I get 40 -50 in space , on planets I get 25 fps , on settlements outside 20fps , inside 25 , in station I get 15 to 20 fps , note this is with shadows off textures to medium and fx to medium , terrain to medium , rest of it low , I knew I wouldnt get great fps going in but I figured horizons ran fine(35fps to 60fps) so odyssey is an expansion so the fps will be the same , big mistake.
 
I mean … they might have to … or perhaps implement custom-optimised shadow rendering for each console platform … which is one of the reasons I think continuing to optimise the PC version with the assumption that’ll somehow magically make it run fine on consoles is folly.
I have a suspicion that they will wait a bit longer and then release Ody for new consoles only.
There is no way they can get this game running on PS4 in an acceptable state.
 
yeah its well below minimum spec , but yes I get 40 -50 in space , on planets I get 25 fps , on settlements outside 20fps , inside 25 , in station I get 15 to 20 fps , note this is with shadows off textures to medium and fx to medium , terrain to medium , rest of it low , I knew I wouldnt get great fps going in but I figured horizons ran fine(35fps to 60fps) so odyssey is an expansion so the fps will be the same , big mistake.
It’s probably unreasonable to expect the fps in settlements to be the same as a station in horizons tbh, there is so much more happening. What fps do you get in space in ODY?
 
40 to 50 fps no matter the settings used , up to high settings ill always get 40 to 50 the same as horizons ,my station fps is much lower than in horizons though even just docking I can get as low as 15fps , horizons I get a solid 35
Edit , The reason for this slow down I believe is even though you can never really see inside the concourse from far away they still render everything inside , including the eyes and hair , I dont think player models have a LOD system , otherwise everything about the station is the same besides the lighting so fps drop shouldnt be that drastic
 
Last edited:
Back
Top Bottom