Freezes at Menu

[cptbetty]

Ever since the .25 update, i cant play KSP. At first it was crashing in the middle of loading and i removed the mods it kept getting stuck on but that only made a partial fix. now after it loads, it freezes right as the menu is about to show up. I read on another thread that it may be related to ram and i should keep my mods below 2.9gb. When i was removing mods, the loading bar would get further so i thought that this was right but my mods are way below 2.9gb. Can anyone help?

I checked all of the mods for newer versions and found one for B9-aerospace and KW-rocketry. other than that, the rest of my mods are up to date and i removed all of the ones lower than 0.24.

Edited October 21, 2014 by cptbetty

[Whovian]

I'm having the exact same issue; I get freezing every time I start up in the middle of the loading screen, and yes, I do have active texture management installed and it's frozen sometimes when it was only using 1.4 GB, so it's definitely not a ram issue. Here's the weird thing.

If I add KW Rocketry to this gamedata folder, it works. If I add Novapunch, it works. If I add the Near Future Technologies pack, it works. If I add all three, it doesn't. I haven't checked if pairs of them work.

EDIT: Ignore the output freezing midline; that's just Finder's crappy .txt viewer. Also I checked with that folder, Near Future Technologies, Squad, and Novapunch and it didn't work. Here's the output log. The log says it froze on KAS, but interestingly, the loading screen got stuck on the stock escape tower.

Edited October 21, 2014 by Whovian

[NathanKell]

Please follow the guidelines in the How To Get Support (READ FIRST) sticky. You're partway there, but we also need mod *versions* (not just a screenshot of Gamedata) and we need the correct log.

I will, however, hazard a guess that you're running out of memory (tracking can be inaccurate); the limit for KSP on OS X is about 2.8-3GB, IIRC. Either increase the scale factor in ATM, or selectively delete the parts you don't want from the various mods you want to add.

Note: this applies to both of you, although cptbetty (welcome to the forums!) there's more extra info needed because less was supplied.

[cptbetty]

Same for me Whovian, but thats happening to me with different mods as well. Some times if i remove a mod, launch ksp, and re-add the mod after it crashes, the crash says its caused by something else other than the mod that was initially causing it.

[Whovian]

Turned the scale factor to 8 and TEXTURE_QUALITY in settings.cfg to 3; it changed nothing. Here are the mod versions.

Toolbar: 1.7.7

ATM: Whatever the latest version is.

ASET and ASET_Props: From ALCOR v0.9

CrossFeeedEnabler: Whichever version came with Near Future Spacecraft 0.3.0

CustomBiomes: Whichever version was packaged with RSS 8.1.2

Firespitter: Whichever version was packaged with B9 5.2.5

Hyomoto: I believe that's MFD 1.2

JSI: That's RasterPropMonitor 0.18.3

KAS: 0.4.9

Kerbal Flight Indicators: R5

KJR: 2.4.4

HyperEdit: 1.2.4.2

KineTechAnimation: Whichever version came bundled with B9 5.2.5

Klockheed Martin: Same as KineTechAnimation

Module Manager: 2.1.5

ModuleRCSFX: 3.1

MP_Nazari: Evidently this is a hotfix for B9 and HotRockets that comes bundled with B9. This would thus be for B9 5.2.5.

Open Resource System: Whichever version was bundled with Interstellar 0.13

ORSResourcePack: Same as Open Resource System

KW Rocketry: 2.6d2

Novapunch: 2.07

NearFuture: All the sub-mods in version 0.3.0

Also I checked; removing KW and keeping NP and NFP didn't fix the problem. I could run all 3 if I remove KAS, though (though I can't run my whole modset.)

[Whovian]

I managed to get these and more mods working; I'm pretty sure it was a combination of turning up ATM and removing PWings (which I should note was one of the other mods.) I tried a lot of things, though, so it may have been something else.

Also, if you're using Real Fuels, make sure all your configs are updated for the recent overhaul. I'm not sure if that was what was causing one of my freezes, but KSP.log made it look that way.

EDIT: Turned the graphics and ATM back to what they were when it was crashing and it worked, albeit with slightly low framerate on the runway. PWings wasn't in the modset it was crashing with, so I believe the only difference is I added stuff (minus PWings) and messed around with one of my Real Fuels configs. Curiouser and curiouser.

Edited October 22, 2014 by Whovian

[Whovian]

I found another possible reason; check your Player.log. If the last thing is something about a NullPointerException involving PWings, the problem is that the latest version crashes if you don't have FAR or NEAR installed. There's a fixed .dll that doesn't do that on page 92.

[Felbourn]

I created an empty CFG once (thinking I'd create the file, just to have it ready for edits, and fill something in later) but discovered that an empty CFG causes the game to halt. The last thing in your Alt-F2 or .LOG might indicate where to look to find an empty or "bad" CFG file.