No More modding for me :(

[Scottwasnt]

The whole problem with this game is the open modding. The games short on detail so as soon as temptation takes you you add some mods & down the track (after hours of work & half way to Duna or beyond CRASH. V1.04 no different to .23 or .9 in this regard, add a few mods (because docking & kerbal control is atrocious & hey modding is fun) then Crash! Crash! Crash! AS in something weird happens like fuel burns but acceleration has no effect when heading for Duna intercept- weird. Now "learn your lesson this time" speaking to self & DON'T MOD . Throw away weeks of game play re-install game & start Career again.

PS - yes I play career mode, most challenge = most fun ==== fun destroyed by stupid bugs

PPS- Yes I use alt5 & alt9 a mod I will have to keep using no matter what.

PPS- If you can explain why I seem to hit an invisible force feild the moment I work out an intercept with Duna please explain- fuel burns but the 236m/s (or whatever) to burn doesn't reduce & the orbit doesn't change- fuel still burns with throttle though- strange thing is I can reach Eve .

[Raven.]

The whole problem with this game is the open modding. The games short on detail so as soon as temptation takes you you add some mods & down the track (after hours of work & half way to Duna or beyond CRASH. V1.04 no different to .23 or .9 in this regard, add a few mods (because docking & kerbal control is atrocious & hey modding is fun) then Crash! Crash! Crash! AS in something weird happens like fuel burns but acceleration has no effect when heading for Duna intercept- weird. Now "learn your lesson this time" speaking to self & DON'T MOD . Throw away weeks of game play re-install game & start Career again.

PS - yes I play career mode, most challenge = most fun ==== fun destroyed by stupid bugs

PPS- Yes I use alt5 & alt9 a mod I will have to keep using no matter what.

PPS- If you can explain why I seem to hit an invisible force feild the moment I work out an intercept with Duna please explain- fuel burns but the 236m/s (or whatever) to burn doesn't reduce & the orbit doesn't change- fuel still burns with throttle though- strange thing is I can reach Eve .

More than likely, your game is crashing because you are using too much memory and not using some kind of memory management utility like Active Texture Management. Thirty mods later and I never had any bugs or crashes on my career in 0.90. On 1.0.4, I just need to change the conduction factor to 1 and it's solid with the same mod list. Was even able to migrate my save game from 0.90 to 1.0.4 without issue. Maybe if you can post a mod list along with a log file, maybe people can help you sort issues out.

[sumghai]

Scottwasnt, if you would like to seek help with a modded KSP installation, please provide the following additional pieces of information:

- Your computer's specifications

- The mods you tried to install

- The output log from when your modded game crashed:

[*] The Logs

These are text files that the game spits out for debugging purposes as it runs; if something broke horribly in-game, there will be something in here about it. You should upload the entire log as a file (i.e. not to pastebin); you can use dropbox or an equivalent host to upload the file. Make sure the entire file gets uploaded; you may have to zip it first, as logs can be very long. Here is where you can find the log:

• Windows: KSP_win\KSP_Data\output_log.txt (32bit) or KSP_win64\KSP_x64_Data\output_log.txt (64bit)
  
• Mac OS X: Open Console, on the left side of the window there is a menu that says 'files'. Scroll down the list and find the Unity drop down, under Unity there will be Player.log ( Files>~/Library/Logs>Unity>Player.log )
  
• Linux: ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log
  

NOTE: These logs are not the same as KSP.log, which lacks valuable data. Do not upload KSP.log; do upload output_log.txt / Player.log

[Scottwasnt]

An improvement over the old game or just this time I'm lucky OR it's a memory issue (Thanks Raven), I removed another half dozen mods & I can now proceed to Duna without starting the whole game from scratch i.e new install.

I'll try "Active Texture Management" & see if that solves it ( Raven )

Thanks Sumghai I'll look into that log & if I strike a bigger buggier bug then I'll bug you with it

PS: Culprit was "BoulderCo" or "CustomAsteroids" or "DDSLoader" or "FirstPersonEVA" or "HullCameraVDS" or "KittopiaSpace" or "Kopernicus" or "OPM" or "PlanetFactory" or "StarSystems" Or just an uncontrolled memory problem/leak (I have plenty of RAM).

The Kerbals are happy again

[Raven.]

An improvement over the old game or just this time I'm lucky OR it's a memory issue (Thanks Raven), I removed another half dozen mods & I can now proceed to Duna without starting the whole game from scratch i.e new install.

I'll try "Active Texture Management" & see if that solves it ( Raven )

Thanks Sumghai I'll look into that log & if I strike a bigger buggier bug then I'll bug you with it

PS: Culprit was "BoulderCo" or "CustomAsteroids" or "DDSLoader" or "FirstPersonEVA" or "HullCameraVDS" or "KittopiaSpace" or "Kopernicus" or "OPM" or "PlanetFactory" or "StarSystems" Or just an uncontrolled memory problem/leak (I have plenty of RAM).

The Kerbals are happy again

For 1.0.4, you really don't need DDSLoader, as KSP now provides that function as part of the stock game as of 1.0. PlanetFactory and Kopernicus, although I'm not entirely sure, may be incompatible with each other. The most recent version of OPM relies on Kopernicus, and is, and always has been, a memory hog. Now don't get me wrong, OPM is an awesome that should be part of the stock game in my opinion, but it eats memory faster than I can eat bacon. The same applies to StarSystems. BoulderCo is more than likely, environment visual enhancements with some kind of texture pack such as Astronomer's Pack, another known memory hog (but very excellent mod). The others I don't have first hand experience.

Now, about the memory issues. More than likely, your computer is a 64 bit system, right? And because it's a 64 bit system, it can address more than 4 GB of hardware memory. This includes both your RAM and the video memory on your graphics card(s). More than likely, your version of Windows is probably also a 64 bit operating system, meaning the OS can take advantage of the extra memory. However, Kerbal is not 64 bit software, it is 32 bit software running in a 64 bit environment. And now you see the pain in the rear. Kerbal itself can only use a max of 4 GB of memory. And guess what, approx. half a gig of that 4 GB is in video memory and is not reported by the OS. So according to Windows, Kerbal will crash at about 3.4 GB to 3.8 GB of memory usage.

Active Texture Management will attempt to compress textures from mods in an attempt to bring the memory usage down. It does an extremely good job at this, within reason of course. Another thing to try is setting the texture resolution to half or quarter resolution (I visuall can't tell the different between half and full resolution with the new DDS textures, but I can tell the different in task manager).

Hopes this helps set things straight for you.