[HOWTO] avoid moded memory crashes with openGL: 12 steps for victory

[scavenger]

hi kerb all

I ran into several issues since the 1.0.2 went out, and after having passed a lot of time everywhere, and somewhat having found fair enough working solutions, I guess it's time to post

This post follows the thread from Samlow - Memory leak & Memory cap Crash to desktop workarounds - and compile its ideas and the latest tricks I found.

PURPOSE: avoid 1.0.2 moded crashes (especially during ascention phase) and frustration

PRE-REQUISITES:

- having more than 4GB system RAM. These advices are useless otherwise, as the main problem is KSP is a 32 bits application that cannot address more than 3.8GB RAM somewhat

- wanting loads of mods

- and visual enhancements.

- and unlimited debris

- and visual light and shadow quality maxed out to 64

- and maybe astronomers pack for those who dare (currently almost not even working in LOW resolution with 1.0.2).

SYMPTOMS: sudden crashes anytime and illegible log output generation (and impossible to revert flight (and more frustration))

METHOD: just plug off your brain and follow the 12 steps method bellow. For loads of mods and NO crashes. AT ALL. Anymore. Ever.

system:

step 0: Windows 32 bits users: enable PAE with elevated command prompt: "BCDEdit /set PAE forceenable"

step 0b: Windows 64 bits users may patch KSP.exe with NTCore's 4GB patch

step 0c: create your 10mn savegames rotation tool

step 1: uninstall ALL your mods (delete all under \GameData\ except "Squad" dir)

step 2: install CKAN in some other dir

CKAN:

step 3: run CKAN and set it up, select KSP dir, then refresh, then "Filter Compatible" button

step 4a: If you really go for Astronomer's Visual Pack, tick it at first, before any other mod, as there is an obscure way to install it that only CKAN knows about. And choose LOW settings.

step 4b: tick the mods you want.

step 5: add these 3 mods: Graphic Memory Monitor , Temperature Gauge Killer , Active Texture Management - aggressive

step 6: switch KSP to opengl with Settings --> KSP command-line --> "KSP.exe -force-opengl -popupwindow"

step 7: if you choosed Scatterer mod, edit the files under \GameData\scatterer\config\*.txt to disable Anisotropic filtering (forceOFFaniso = True)

launch:

step 8: launch the savegame rotate batch

step 9: launch KSP via CKAN to be in opengl (or create an msdos batch than can include the savegame rotate)

in game:

step 10: turn off PPFX in settings / nope, useless as it doesn't save any memory

step 11: ENJOY

Have a look from time to time at the memory value on the left edge of the screen. At load with my 35 mods, I run at 1,8GB. Then it goes up, and up, each time I switch from the VAB to the launchpad to the map to the game back, and so fort.

step 12: When you start reading 3,400+MB it is time to stop what you were doing, SAVE, and exit the game.

I am deadly serious. Passed the 3,400 MB limit, it will increase to 3,600MB quite rapidly, then crash at 3,800MB.

NOTES:

If you really do as above, AND strictly stick to the critical step 12, you will never have a crash anymore

If you still have a crash, which I doubt if you follow the instructions, the 10mn savegames rotate will save your launch

Do not forget to set up anti aliasing with your GC 3D control panel, and Threaded optimization or anything that can improve performance, there are numerouse threads about that.

APPENDIX:

- I am not sure whether step 0b is still necessary as of version 1.0.2 but better use it than be sad / nope, doesn't change anything, game is still crashing passed the 3,600MB memory usage

- PAE explained by Billou: Physical Address Extention

- CKAN is better than KSPModAdmin because KSPModAdmin gets sloooooow with just 10 mods added

- step 5 can be completed with Critical Temperature Gauge mod

- step 7 covers a known bug between Scatterer and OpenGL where strange lines will appear in the sky

- step 8 and 9 can done with a batch containing these 2 lines, placed in the KSP_win directory:

start <your path here>\loop_saves.bat
start KSP.exe -force-opengl -popupwindow

- step 0c is critical. If you played for 2 hours then crash a launch that costs you 9/10 of your funds, the savegame you would have done before launching the game would also means loosing all of your 2 hours progression...

Bugs and ideas covered:

Memory leak & Memory cap Crash to desktop workarounds by Samlow

KSP memory management by Warenschultz

Less memory usage by using OpenGL

New heat system causes memory leaks

Critical Temperature gauges memory leak

OpenGL mode doesn't work

Astronomer's Visual Pack crashes on load

Unexpected crashes

rotate savegames every 10 mn

Edited May 30, 2015 by scavenger
update