Version 1.0 (1.0.1/1.0.2? [steam v on auto update]) Windows 7 64-bit (AMD chip & GTX gpu's, standard stuff~) Stock KSP, no mods Simple crash: In flight, 10-30 kilometers above Kerbin, during 4x physics warp, scene change from flight to map, back to flight, sudden crashes. This first time this happened I was flying a simple jet to Kerbin's north pole for science collection. I didn't think it would be persistent so I don't remember the exact conditions. Simply flying 4x acceleration to get there quick, over an hour of flight I'd say, and then a crash. I was quite frustrated so I made a new vessel (simple rocket with science modules), enabled cheats (infinite fuel, no destruction to parts, hack gravity) and again, in flight to north pole, physics warp, scene change, game crashed. Knowing KSP, knowing Unity, and knowing my PC, it tallied it up to bad luck. But this morning it happened again. No mods, beefy PC, no random software that would interfere, I'm at a loss. I haven't been able to find this bug on the forums, and it's getting rather annoying, I imagine it might have something to do with new aerodynamics (I haven't played since v0.23 or so) and maybe I'm pushing the game too hard with physics acceleration and rapidly changing back and forth from map to check my trajectory. Perhaps dual monitors and KSP in full screen causes graphics crashes? Maybe this is just something that was caused by patch and will be fixed soon as it could already be known and in the works for a fix. Crash does not seem to produce an error log, though that might be something Steam alters. I've put off playing KSP for the full release since last summer probably because I was hoping to avoid this kind of frustration inducing bugs; with any luck, it's something I'm doing wrong and not the game itself. Anyone had similar experiences? *Edit: Tried again, this time, no physics acceleration. Managed to land near pole, collect science data, went to map to reorient and head back to KSC, left map back to flight scene, game crashed. Scene changes have always been an issue for me, I really hope this is fixed soon. It's frustrating not being able to utilize simple game elements like the map. Gonna check the forums to see about map issues, and delete this post and comment in the appropriate thread if necessary. *Edit #2: Still haven't seen anything quite like this in Support. Tried again.Simple rocket launched from KSC, en route to north pole region of Kerbin. Debugged no max temperatures, infinite fuel, unbreakable joints, no crash damage, entered a suborbital trajectory. On reentry, this time, no physics acceleration, coming in hot, throttled engine to slow decent, game crashed, not even an error window popped up, the game just vanished from desktop. Maybe this is the 64 bit version, but I figured on Steam it would be the stable 32 bit, as there's no way I know of to specify which version you want to download. I did actually get an error log, it's a jazillion pages long. This is the craft. Beginning of Error Log: "Unity Player [version: Unity 4.6.4f1_99f88340878d] KSP.exe caused an Access Violation (0xc0000005) in module KSP.exe at 0023:012fae2b. Error occurred at 2015-05-03_120014. F:\SteamLibrary\steamapps\common\Kerbal Space Program\KSP.exe, run by Karl. 41% memory in use. 0 MB physical memory [0 MB free]. 0 MB paging file [0 MB free]. 0 MB user address space [104 MB free]. Write to location 00100000 caused an access violation. Context: EDI: 0xffcb37d4 ESI: 0x536462bc EAX: 0x00000000 EBX: 0xffcb37d4 ECX: 0x00040001 EDX: 0x00000000 EIP: 0x012fae2b EBP: 0x0015f304 SegCs: 0x00000023 EFlags: 0x00010216 ESP: 0x0015f2f8 SegSs: 0x0000002b" I of course have no idea what that means, or how to interpret the Stack after it, nor the output log which changed normal line reading to this: "DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory! Trying to allocate: 2097152B with 4 alignment. MemoryLabel: DynamicArray Allocation happend at: Line:334 in Memory overview" Essentially I feel like anything at this point can trigger a crash. I guess I'll go back to waiting for the game to get a stable patch.
