Many thanks (sorry I sound like a broken record) for the additional insights.

I am going to try Planets at 4096 and see what happens, still while doing (4x DSR, 0% smoothing and 0.65 SS in-game, these three parameters I won't change).

Once I get a feel of this (a couple cargo hauling missions should suffice) I'll try reverting to 8192 with the TexturePoolBudget set to 50. Last I'll see what the shadows SliceSize can do.

More reports coming soon, hopefully this can help people aiming at your settings but without the same horsepower.
 
Last edited:
Morbad said:
Also, you could try reducing the shadow 'SliceSize' back to 2048 on appropriate profiles. This will reduce the shadow map resolution and save memory, but most of the improvements will remain intact.

In the GraphicsConfiguration.xml file I pasted from yours a couple posts before I see that shadows Ultra are already at 2048 for SliceSize.. am I missing something?
 
In the GraphicsConfiguration.xml file I pasted from yours a couple posts before I see that shadows Ultra are already at 2048 for SliceSize.. am I missing something?

A few revisions back I started replacing the low preset rather than ultra, to make it easier to compare with ultra. So, if you are using the newest file, set shadows to "Low" for my custom cascade settings.
 
A few revisions back I started replacing the low preset rather than ultra, to make it easier to compare with ultra. So, if you are using the newest file, set shadows to "Low" for my custom cascade settings.

Ah! Sorry, I must have overlooked that.. so basically everything on HIGH/ULTRA and Shadows to LOW.

I'm gonna double check I also got the latest XMLs, just to make sure..
 
Last edited:
Ah! Sorry, I must have overlooked that.. so basically if I have everything on HIGH/ULTRA (as I used to before importing your two XML files) I am not using the parameters you set. I should set all parameters to low, instead.

Only for the shadows, which is the only thing I changed in the GraphicsConfiguration.xml.

The GraphicsConfigurationOverride.xml was put together separately (this thread originally only dealt with shadows) and modifies the ultra settings.

Set everything as you would normally, then set 'low' shadows.
 
Got it. Did that now.. and it's curious how the frame rate just jumped to the roof.. it could be the ViewDistance (which I know likes to reset itself at 1.000000 maximum, instead of the 1.999999 I had, which could be overkill at these settings) or something else just clicked in place (cache reset..)

So I'd say I can draw a line and consider the real testing (without clumsy mistakes :)) is starting now..
 
Hey guys, when you're talking about "smoothing" which setting is it exactly ? In game or in the GeForce setting ?
 
Hey guys, when you're talking about "smoothing" which setting is it exactly ? In game or in the GeForce setting ?

In this case it was part of NVIDIA's DSR. At 4.00x DSR (which is double both horizontal and vertical resolution) no smoothing is needed, but somewhere between 25 and 33% usually works best with the other DSR resolutions.

I generally use NVIDIA's DSR alone to capture for capturing 4k video, but occasionally use both together to achieve the best reduction of jaggies possible.
 
In this case it was part of NVIDIA's DSR. At 4.00x DSR (which is double both horizontal and vertical resolution) no smoothing is needed, but somewhere between 25 and 33% usually works best with the other DSR resolutions.

I generally use NVIDIA's DSR alone to capture for capturing 4k video, but occasionally use both together to achieve the best reduction of jaggies possible.

Ok thanks. I'm running it in 4.00x DSR but I still don't understand where I can find this "Smoothing" setting ni NVidia settings though =/

Edit Forget about it. My PC is in french and I didn't translate "Smoothing" with the right word so this is why I couldn't find it ;)
 
Last edited:
Just in case anyone else is wondering, these are two settings Morbad was talking about.

NVIDIA Control Panel
 
After a whole night visiting engineers and doing Haz Res duties, I can report on the above.

With my system (definitely not a new one: a Mac Pro 2009, Xeon 8-core W3540 @ 3GHz, 16Gb Ram, NVIDIA 1060 3Gb, SSD drive with Windows 10 x64 and ED on it) I only did bring Morbad's settings to one change, for the moment: 8192 for planets generated stutters in loading, especially on arrival to new systems etc. not totally unplayable but once toned down to 4096 things became much smoother.

Nothing else needed changing/adding. At present time the April Update is really messing up the frame rate and I found out (along with others) that the "Trails" parameter in the FX section of GraphicsConfiguration.xml (HAS to be edited there, because on the override it won't stick) is causing it. So I changed that to Trails=0 and the rest is the same as High.

Things are really smooth and already looking much better. I don't see any reason NOT to use Morbad's settings (and follow his constant developments) even on lower-profile systems like mine. I moved back to my native resolution (2K @ 75Hz VSync ON and in-game SuperSampling to x1.00) and turned of DSR because of some weird behavior (=sluggishness/low fps) that I thought was being caused by the massive upscaling to 4x DSR.. but it wasn't the case.

Yesterday I cleaned both GraphicsConfiguration.xml and GraphicsConfigurationOverride.xml, also cleaned the other xmls and started from scratch. Something must have been wrong either in my editing or in my messing up with EDProfiler. I don't know for sure but once things were put back into place, nice and clean, I started EDLaunch.exe directly and entered the game, I noticed the Shaders and Planetary Renders were being re-done and after that things were butter smooth. I double checked that things were as they were supposed to be and confirmed.

I am still on NVIDIA drivers 417.71 and need to update but never found the time to do a full clean install so far. Will do soon.

TLDR: Things look great with Morbad settings even on computers that are not top-notch in performance. I had some problems in the settings so I cleaned everything and started from scratch and the result was butter smooth.
 
the "Trails" parameter in the FX section of GraphicsConfiguration.xml (HAS to be edited there, because on the override it won't stick) is causing it.

I've got engine and weapon trails disabled in the override and it's definitely working for me. Perhaps there was a formatting error in yours?

This is what my current GraphicsConfigurationOverride.xml looks like:

XML:
<?xml version="1.0" encoding="UTF-8" ?>
<GraphicsConfig>
    <Planets>
        <Ultra>
            <TextureSize>8192</TextureSize>
            <WorkPerFrame>512</WorkPerFrame>
        </Ultra>
    </Planets>
    <GalaxyBackground>
        <High>
            <TextureSize>3328</TextureSize>
        </High>
    </GalaxyBackground>
    <Envmap>
        <High>
            <TextureSize>1024</TextureSize>
            <NumMips>10</NumMips>
        </High>
    </Envmap>
    <GalaxyMap>
        <High>
            <LowResNebulasCount>24</LowResNebulasCount>
            <HighResNebulasCount>3</HighResNebulasCount>
            <LowResNebulaDimensions>128</LowResNebulaDimensions>
            <HighResNebulaDimensions>512</HighResNebulaDimensions>
            <LowResSamplesCount>24</LowResSamplesCount>
            <HighResSamplesCount>96</HighResSamplesCount>
            <MilkyWayInstancesCount>24000</MilkyWayInstancesCount>
            <MilkywayInstancesBrightness>0.9</MilkywayInstancesBrightness>
            <MilkywayInstancesSize>0.8</MilkywayInstancesSize>
            <StarInstanceCount>12000</StarInstanceCount>
        </High>
    </GalaxyMap>
    <Trails>
        <High>
            <EnableEngineTrails>0</EnableEngineTrails>
            <EnableWeaponTrails>0</EnableWeaponTrails>
        </High>
    </Trails>
</GraphicsConfig>

Also, I just noticed this forum code thing is converting my tab stops into spaces. Should still work fine, but it's annoying.
 
Morbad said:
I've got engine and weapon trails disabled in the override and it's definitely working for me. Perhaps there was a formatting error in yours?

Ah! Thanks, yes there was, as I was not calling the "0" with "EnableEngineTrails.. I was using a duplicate of what the <FX> tree looks like in the main GraphicsConfiguration.xml - definitely not what you have here.

Annoyed at the tabs=spaces too, but it's ok I usually use a grep search and replace and it's all good.
but when I paste in Notepad++ the correct tab indentation is back..

Trying this immediately and reverting FX to default ultra in-game. Thanks! :hatoff:
 
Everything working great, smooth as butter on my system.
  • Planets at 4096 (instead of Morbad's 8192 default)
  • Engine and Weapon Trails disabled (0) as a temporary fix before the April's patch is .. patched.
  • No additional XML lines added or modified
  • Shadow set to Low in-game (since Morbad's shadows tweaks are applied to "Low")
  • 2k res @ 75Hz VSync ON, in-game supersampling to x1.00
I am going to step things back to 4x DSR and 0% smoothing and see how it goes. The fact that I currently barely have as much credits as a 1-time rebuy and I am sailing in hostile Powerplays territories makes the testing more... enticing.
 
Ok so far so good. I did try 4x DSR with 0% smoothing, in-game SS at x0.65 and yes, the system is more stressed, but it's still very much playable and enjoyable. I did notice some texture swapping (low..high..low..high) while undocking at a station, it's clear that this resolution is putting more stress on the card (and probably making the same textures more demanding to be displayed?).
 
Last edited:
After updating the NVIDIA drivers to the latest (v430.39) I have to say things are 2x smoother and faster. Impressive, whether it is the driver or just the fact that a clean install removed something that was messed up from all the tweaking.

Anyway, I am now playing at 60Hz VSync on instead of 75Hz (could that custom resolution I had added be the cause for decreased performance? Go figure..) and only tuned down the planets to 4096, playing at 2K native or 2K -> 4x DSR 0% Smoothing -> 0.50 in-game SS. Which gives me the same 2k but with a less "defined" effect that I must admit is not too bad and hides the "hi, I am a videogame polygon" effect :)

When docked at planetary outposts and settlements I can see some textures not being at their best qualities (on structures) and the FPS dropping a bit, but I guess that's the nature of being in a more complicated environment to calculate for my graphics card.

I might try adding this under <planets>:
XML:
<TexturePoolBudget>50</TexturePoolBudget>


Or bringing the shadows slice at 2048 (from 4096), both things as suggested by Morbad.
 
After a day or two of testing, here's what I found out.

1. XML configuration for GraphicsConfiguration.xml and GraphicsConfigurationOverride.xml
After some testing I found out I only had to scale down the Planets to 4096 textures instead of 8192, as I don't have a GPU as powerful as Morbad's and yours. However, I did not find the need to tone down the shadows from 4096 to 2048 or add a <TexturePoolBudget>50</TexturePoolBudget> parameter, which actually seemed to make things worse. I won't like the XMLs here as Morbad has already done it and he can keep us posted on further developments in case he modifies his again.



2. NVIDIA DSR settings + in-game Super Sampling combinations
Original ResolutionNVIDIA DSR SettingResulting ResolutionIn-Game Super-SamplingFinal Resulting Resolution
2560 x 1440 (2k native)x1.002560 x 1440 (2k native)x1.002560 x 1440 (2k native) A
2560 x 1440 (2k native)x4.005120 x 2880 (5k native)x0.653328 x 1872 B
2560 x 1440 (2k native)x4.005120 x 2880 (5k native)x0.502560 x 1440 (2k native) C
2560 x 1440 (2k native)x4.005120 x 2880 (5k native)x0.753840 x 2160 (4k native) D

and obviously let's just state that [A] is just the default of my native display resolution and it's what I was used to. No major problem here but there is room for improvement, especially since the so-called "jagged lines" are still visible and not effectively hidden by any of the in-game anti-aliasing.

As suggested by Morbad, I did try - which is a resolution he used and found to be working nice and crisp. Indeed, this would be for me the de-facto standard "step up" from anyone having a native 2k. It comes at a higher stress for your GPU and my 1060 3Gb cannot really take all that hit during station/planetary landings. It's not THAT bad, but I wanted to try something less demanding.

So I moved to [C], which uses the same DSR factor but then scales the in-game super-sampling to x0.50 instead of x0.65 - this (if my calculations are correct) brings the game back to 2k native. However, the difference is huge. It might be a tad blurrier, but the "video-game sharp polygon edges and jaggies" are gone and it looks much more appealing and immersive, to me. On my system this is still playable and smooth even during station landing etc.

[D] would be even better as it takes the final resolution to 4k native. Try it out, it's definitely more demanding though. I did revert back to [C].

3. Further desktop tweaks
When you use DSR, the Alt-Tab can get a bit sluggish in full screen mode. Well, sometimes even without using DSR, you might have noticed that Alt-Tab is sluggish. ED is a game where a lot of 3rd party resources can be used, and in my case, the alt-tabbing is kinda frequent between jumps or during automated cruise/landing (I happen to do so from time to time ;)). I don't like Borderless very much although I can't say it does hold worse FPS than full screen. Actually they seem pretty much the same. The sluggish Alt-Tab - however - bothered me.

I found out ways you can use to lessen the problem, especially if you use two displays (on two different cards or on the same). These tweaks might be good anyway for general improving of your performances, so try them out.

a) Focus Assist can be a problem. I would recommend disabling it

Go to: Settings > System > Focus Assist and change When I’m playing games to OFF. I actually did turn it to OFF for all the parameters.​

b) Change the way the scaling is done

Go to: Nvidia Control Panel > Adjust Desktop Size and Position > Scaling Tab > select Full-Screen for Scaling Mode and in the Perform scaling on: dropdown, select GPU.​

c) with DSR set at x4.00 you can even turn your desktop to 5120x2880. You should experiment with the above (if things are too small go to scaling: 200% and they will be looking the same as you had in x1.00 with scaling 100%) - because it could speed up your alt-tabbing. I did it and found no visible difference, but before doing the A and B tweaks I did notice that alt-tabbing was faster already, probably because your NVIDIA card does not have to switch between different internal resolution? I am not sure, however it's worth investigating and it's kinda cool that with DSR on you can use your resolution also for the desktop. As usual, YMMV. I do use an old ATI card for my secondary display so I have 2 cards on 2 displays and in fullscreen mode, with DSR going on and all that jazz I noticed my 2nd display just had a desktop without windows on it. Now I can keep g19s, the Fuel Rats IRC and Discord, all there. Kinda cool and alt-tab is snapping fast.

Credits for this go to /u/FuneralChris, /u/Joskhi77 and u/Dare
 
Last edited:
Thank you for yout testing Morbad and Tazpoken!

I tweaked my graphic with this thread for the last 2 days and it looks amazing!
Did i understand right: a higher DSR Factor in NVIDIA driver is better than a high supersampling setting in game- options?
For example 0.75x supersampling in game and DSR 4.0 is better than 1.00x supersampling in game and DSR 2.25 at res 2560x1440 ?

2nd thing: I have in NVIDIA in program setting supersampling 8x. How effect it to the in game super sampling?
 
Back
Top Bottom