Open letter to Ksp

[322997am]

Dear KSP

You are a great game and I want you grant the following permission

TO USE MY GRAPHICS CARD

and for no price whatsoever

ThanK You

322997am

ps: the point is load the textures onto the graphics card and not anything else.

[legoclone09]

8 minutes ago, 322997am said:

Dear KSP

You are a great game and I want you grant the following permission

TO USE MY GRAPHICS CARD

and for no price whatsoever

ThanK You

322997am

ps: the point is load the textures onto the graphics card and not anything else.

Well the textures and assorted stuff use a few GB of normal RAM, but using vRAM before normal RAM sounds like a good idea.

[sal_vager]

KSP is using your graphics card, if it wasn't you wouldn't be able to see anything ...

 

Edit:

Also, stock textures aren't that big a deal, lowering your texture quality is.

[Gaarst]

Don't the -forced3d11 (or -d3d11, not sure) and -forceopengl tricks transfer some RAM usage to VRAM ?

Edited January 24, 2016 by Gaarst

[BloodDusk]

Maybe some physics calculations could be offset to the GPU? No, I'm not talking about CUDA or PhysX.

[Alshain]

Game Engine guys.  The game engine handles that. Squad couldn't do it if they wanted to, at least not on U4, I don't think they can on U5.

[BloodDusk]

4 minutes ago, Alshain said:

Game Engine guys.  The game engine handles that. Squad couldn't do it if they wanted to, at least not on U4, I don't think they can on U5.

Considering console port...Maybe it's time to consider making a dedicated engine for KSP?

[Alshain]

8 minutes ago, BloodDusk said:

Maybe some physics calculations could be offset to the GPU? No, I'm not talking about CUDA or PhysX.

If you aren't talking about CUDA and PhysX then what are you talking about?  That is the only way to move processing to the GPU.

[Alshain]

5 minutes ago, BloodDusk said:

Considering console port...Maybe it's time to consider making a dedicated engine for KSP?

Squad isn't big enough for that, and even if they hired a bunch of people started today you wouldn't see it for 5 to 10 years.  You don't just throw a game engine together overnight.

[BloodDusk]

5 minutes ago, Alshain said:

If you aren't talking about CUDA and PhysX then what are you talking about?  That is the only way to move processing to the GPU.

Something else. If you don't have a nVidia GPU, CUDA and PhysX are offloaded to the CPU, which is exactly the same as what we have now.

[Alshain]

1 minute ago, BloodDusk said:

Something else. If you don't have a nVidia GPU, CUDA and PhysX are offloaded to the CPU, which is exactly the same as what we have now.

There is nothing else.  I don't think you know what CUDA and PhysX are.  There is no offloading them to the CPU, if you don't have Nvidia, it just don't happen at all.

[Captain Sierra]

1 hour ago, Gaarst said:

Don't the -forced3d11 (or -d3d11, not sure) and -forceopengl tricks transfer some RAM usage to VRAM ?

Its -force-d3d11 and it does get the game to offload some of the textures to VRAM (things related to planets and PQS can't be because of how the game is coded but part textures can be). Because its fickle about what offloads and what doesnt, your milage may vary, but I've personally observed RAM savings as high as 40% and in 1.0.5, there are virtually no graphical artifacts. There are some framerate issues relating to certain shaders, but its a small price to pay for taking yourself out of the danger zone for memory leak crashes.

[322997am]

2 hours ago, legoclone09 said:

Well the textures and assorted stuff use a few GB of normal RAM, but using vRAM before normal RAM sounds like a good idea.

I was saying to have the textures and anything that can be loaded onto the gpu without much trouble should as that is what allows a lot of video games to function properly.

Also who rated this 1 star. Y u do that?

[BloodDusk]

37 minutes ago, Alshain said:

There is nothing else.  I don't think you know what CUDA and PhysX are.  There is no offloading them to the CPU, if you don't have Nvidia, it just don't happen at all.

That is correct for CUDA, but not for PhysX.

[Alshain]

1 hour ago, BloodDusk said:

That is correct for CUDA, but not for PhysX.

Depends on what you are referring to as "PhysX".  It can have a couple of meanings.  1. It's a software based physics engine. 2. It's shorthand for PhysX GPU Hardware Acceleration.  The former cannot be done differently without a game engine change.  The latter can not be done without a game engine change.

Hmm, I guess it didn't depend on anything really.

2 hours ago, 322997am said:

I was saying to have the textures and anything that can be loaded onto the gpu without much trouble should as that is what allows a lot of video games to function properly.

Also who rated this 1 star. Y u do that?

Nothing can be loaded onto the GPU.  That seriously makes no sense, which is probably why someone rated it one star.

[cantab]

6 hours ago, Gaarst said:

Don't the -forced3d11 (or -d3d11, not sure) and -forceopengl tricks transfer some RAM usage to VRAM ?

They do. What's actually going on I've been told is that the default DirectX 9 mode duplicates the textures - once in the graphics memory where they're needed, and again in the system RAM where it doesn't need them.

Anyway, the issue is already fixed in DX11 and OGL modes. KSP 1.1 is expected to move to DirectX 11 as the default, so it shouldn't be a problem any more.