Forcing DirectX11: 40% memory reduction!

[Curveball Anders]

Just now, Gaarst said:

The point of forcing DX was reducing memory usage, since 1.1 and 64-bit I don't think that's necessary anymore, is it ?

Well it works and does appear to use less gpu memory and lowers gpu load for me.

But that's on an almost antique GTX-570 where such things still matter.

[crash!!]

how do you put this code in using steam?

 

[Anquietas314]

11 hours ago, crash!! said:

how do you put this code in using steam?

 

Open the properties window for KSP, then do this:

Spoiler

Dunno if the disclaimer(s) still apply in 1.1+ though; I don't need to use this on my system.

[Nick233]

Oh, wow! Works very well! A few graphical gliches, but than not the point! On 32-bit win i has about 6 launches with dx11 on litle modded client, when typiclally it crashed after 2!

Edited October 7, 2016 by Nick233

[jpinard]

Is this commandline still necessary after the latest DLC (breaking ground) and patch?  They did a lot to optimize stuff and I'm not sure if DX11 was one of them.

[Stone Blue]

3 minutes ago, jpinard said:

Is this commandline still necessary after the latest DLC (breaking ground) and patch?  They did a lot to optimize stuff and I'm not sure if DX11 was one of them.

Yes, it is, unfortunately...
And it *will* be, until Squad finally decides to give up on Dx9, and re-codes the game, as may be needed... (infinitesimally smoll chance of this *ever* happening...)
Or, until Squad decides to upgrade Unity to or newer than 2017.3, which dropped Dx9 support... (smoll chance of *this* ever happening... but mebbe a tiny bit better than above...)

So I would get used to planning on needing to force Dx11 on KSP, at least until KSP 2.0 comes along :rofl:

[jpinard]

29 minutes ago, Stone Blue said:

Yes, it is, unfortunately...
And it *will* be, until Squad finally decides to give up on Dx9, and re-codes the game, as may be needed... (infinitesimally smoll chance of this *ever* happening...)
Or, until Squad decides to upgrade Unity to or newer than 2017.3, which dropped Dx9 support... (smoll chance of *this* ever happening... but mebbe a tiny bit better than above...)

So I would get used to planning on needing to force Dx11 on KSP, at least until KSP 2.0 comes along :rofl:

Do you have graphical artifacts from using it?

Also, dp you use the -no-singlethreaded command line as well?

[jpinard]

If I use the no single threaded command after the d3d11 option, should there be a space between them or not?  

-force-d3dll-no-singlethreaded

vs.

-force-d3dll  -no-singlethreaded

Edited July 2, 2019 by jpinard

[Stone Blue]

On 6/24/2019 at 1:19 PM, jpinard said:

Do you have graphical artifacts from using it?

Also, dp you use the -no-singlethreaded command line as well?

Unfortunately I do not actually *play* a lot... I pretend I am a mod dev, and dabble in modifying mods... So I spend most of my time in a limited dev install, 99% of the time never leaving Kerbin LKO...

Only real glitches I notice forcing Dx11, are the top and bottom rows of part icons being cutoff/overlapping the UI, and the darker, 3/4 cut-off icons of non-command parts when I havent selected a root part yet...
i can live with that, for the *HUGE* performance and lower RAM usage I see with Dx9...

But this is with Textures Unlimited plugin installed... you'll get blue'd out part icons, and mebbe other *stuff* with Dx11, w/o TU installed...

and, no, I dont use the no singlethreaded CLI... I dont remember hearing what it is or does... vOv

Edited July 2, 2019 by Stone Blue

[purpleivan]

On 7/2/2019 at 6:55 PM, Stone Blue said:

But this is with Textures Unlimited plugin installed... you'll get blue'd out part icons, and mebbe other *stuff* with Dx11, w/o TU installed...

On my machine I get blue parts icons even if I remove all my mods, when I force Dx11.

[HafCoJoe]

1 hour ago, purpleivan said:

On my machine I get blue parts icons even if I remove all my mods, when I force Dx11.

Dx11 was used a lot back when KSP was 32 bit, but now that its 64 bit you shouldn't need Dx11. See that the original post is from 2015.

[purpleivan]

2 hours ago, Avera9eJoe said:

Dx11 was used a lot back when KSP was 32 bit, but now that its 64 bit you shouldn't need Dx11. See that the original post is from 2015.

In my case I do, as I'm using a build of KS3P and Scatterer that require it.

[HafCoJoe]

9 hours ago, purpleivan said:

In my case I do, as I'm using a build of KS3P and Scatterer that require it.

Oh, strange

[Nightside]

On 7/4/2019 at 11:12 PM, purpleivan said:

On my machine I get blue parts icons even if I remove all my mods, when I force Dx11.

Textures Unlimited fixes this, even if you don't use its other features.

[purpleivan]

5 hours ago, Nightside said:

Textures Unlimited fixes this, even if you don't use its other features.

I'll take a look at it then.

[Stone Blue]

3 hours ago, purpleivan said:

9 hours ago, Nightside said:

Textures Unlimited fixes this, even if you don't use its other features.

I'll take a look at it then.

Thats what i was trying to tell you... install Textures Unlimited...

On 7/2/2019 at 12:55 PM, Stone Blue said:

But this is with Textures Unlimited plugin installed... you'll get blue'd out part icons, and mebbe other *stuff* with Dx11, w/o TU installed...

 

Edited July 7, 2019 by Stone Blue

[Nightside]

2 hours ago, Stone Blue said:

Thats what i was trying to tell you... install Textures Unlimited...

 

I was just peer reviewing your statement