Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Launch KSP" causes performance issues #630

Closed
Ippo343 opened this issue Dec 18, 2014 · 4 comments
Closed

"Launch KSP" causes performance issues #630

Ippo343 opened this issue Dec 18, 2014 · 4 comments
Assignees
Labels

Comments

@Ippo343
Copy link
Contributor

Ippo343 commented Dec 18, 2014

Link to original forum post

Summary
Launching KSP v0.90 via CKAN's "Launch KSP" function results in ridiculous amounts of RAM usage even though no mods are actually installed. Launching via the usual KSP.exe does not do this.

Versions
KSP version 0.90.705 x86 ~ CKAN version 1.3.6 ~ System info

Details
Launching KSP via CKAN (no mods installed) results in memory limit being reached before it even finishes loading (image). Launching KSP via the stock launcher .exe (no mods installed) is successful and uses just over 2gb of RAM (image)

How to reproduce

  1. Install KSP v0.90.705
  2. Install CKAN v1.3.6
  3. Do not install any mods
  4. Run KSP via stock launcher app or .exe
  5. Note RAM usage
  6. Close KSP
  7. Launch CKAN
  8. Click "Launch KSP"
  9. Observe RAM usage throughout loading process. It should jump up to almost 3gb before any parts are loaded.
@Ippo343 Ippo343 added the Bug label Dec 18, 2014
@AlexanderDzhoganov
Copy link
Member

This may be my fault, I've put the -force-opengl flag by default, could you remove it from Settings -> KSP Command Line and check if you have the same issue?

@Ippo343
Copy link
Contributor Author

Ippo343 commented Dec 18, 2014

I cannot reproduce the issue on my system: however, I normally use opengl, so this might be the reason.
I will report your solution to the OP, it makes a lot of sense :)

@space-is-hard
Copy link

I'm the original submitter. Removing the -force-opengl flag worked perfectly. Thanks!

@Ippo343
Copy link
Contributor Author

Ippo343 commented Dec 18, 2014

Great to know! I propose we leave this issue open until the option is removed from the default in the next update.

RichardLake added a commit to RichardLake/CKAN that referenced this issue Dec 19, 2014
@RichardLake RichardLake self-assigned this Dec 19, 2014
@RichardLake RichardLake added the In progress We're still working on this label Dec 19, 2014
@Ippo343 Ippo343 closed this as completed Dec 27, 2014
@Ippo343 Ippo343 removed the In progress We're still working on this label Dec 27, 2014
RichardLake added a commit to RichardLake/CKAN that referenced this issue May 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants