AlamoVampire

two more data points: first run lasted about an hour before I had to run errands. second run lasted 6 minutes 58.46 seconds in the initial screen after loading, then only another 1 minute 17.93 seconds after hitting resume saved. crashed in VAB, tier 3, edited a saved ship for all of like 10 seconds before POOF failure listing yet again NTDLL.DLL. @Claw side note: all times are from telling UAC that, yes, I trust KSP now let me play.

slick lookin!

@Claw Its curious to say the least. I will try for another data point tonight for you.

@Claw Some data for you. Ive been running KSP as admin and so far its looking stable. First try is listed a page back with me having 53 minutes of stability before ending and now i had 3.5 hours before ending the session after building part of a jool mission. I know its not a large sample but its something. I just saw your mod havent tried it but my vab crashes were all in sandbox so tier 3?

New data point on my observation of "run as admin": ran 3.5 hours this time. Built a jool mission. I ended the session after doing 7 flights to build the mission to its current status. Request for more input and data from all please

two things. gathered a second data point for the crashing threads. and spent 3.5 hours building a big ship to take a tiny probe to Bop. has 4 more docking ports, maybe i will send up some satellites for the rest of the jool system? anyway, here it is after its fourth assembly flight: If you look closely in the above picture, you will see 2 clamp-o-tron seniors, above that with 1 of those aforementioned docking ports is the probe for jool. ya, i think i just channeled @Whackjob by going with 25 nuclear engines to punt such a small probe to Bop. Which is why I may send 4 small satellites to the thing to make it seem worth while lol. here it is after its 6th assembly flight - prior to flight 7 with fuel:

firstly, another one of these threads? Short answer WHO CARES? I mean really, who cares? All this type of thread tells me is, some person feels insecure about what they are doing in KSP and need some external justification one way or the other in order to validate or invalidate themselves. This kinda garbage needs to stop. Hyper edit, is that cheating? cheating fate possibly. is it kraken bait? absolutely. do I care who uses hyper edit? unless I put forth a challenge and specifically forbade that mod, nope. not one bit. is mechjeb cheating? NOPE. It gives vital informations that KSP sorely lacks, and it has autopilot. both win win. both very needed <unless you are the type who enjoy performing the same launch profile ad nauseum or enjoy babysitting long burns> in this game. I use mechjeb and am bloody proud to use it. secondly inb4 lock. oh and as a side note. remember that whole same launch profile multiple times? well, if it wasnt for mechjeb and its wonderful autopilot, the 7 flights it took to just reach THIS point, id have lost my mind. for the record, the flights: 1. central core.| 2. Probe atop the central core <above the 2 clamp-o-tron sr> |3. nuclear core 1. |4. nuclear core 2. |5. nuclear core 3.| 6. nuclear core 4.| 7. refueling mission.| mission 8 will most likely be the first of 4 satellites to dock to the other 4 docking ports, which means mission 12 will be a manned mission to check out and modify as ground testing would suggest for proper mission readiness for Jool. SO, in total that will have been at least 12 nearly IDENTICAL launch profiles for a mission for jool. Here is the picture:

Tinkered a bit with a station

Potential Data Point: I know, one trial a data point does not make, but, that is why I bring this up here, has anyone who has had these crashes tried running in Admin mode? I did tonight before I wandered off to play a diff game, and got a decent 53 minutes of solid stable play. any other thoughts? I posted this same thing into my own thread so, its in 2 locations now.

possible new data point. for the record, has any of the affected players tried running the game as administrator? I tried that myself this evening and got 53 minutes and change of play before I decided to wander off to do something else. one trial and one data point a viable test set do not make. we need more input.

@steve_v i am neither defending nor attacking how this went down, but, from what I can tell this is a unity thing what with all my crashes since 1.1.X came to be list with it showing NTDLL.DLL <caps for illustrative purposes> as part of the issue, and the thread I started on that particular subject lists this as Unity and its MONO/memory issues...so im not sure who is at fault here, squad? unity? both? i cant and wont say, but, its a mess pure and simple.

i would have preferred they NOT release 1.1.0 at all until after taking the proper time to completely check it out. rushing it out the door followed by two rapid fire patches that did not fix the huge issues we have with the crashing did not help their image. They should have said we are going to go on vacation to get some rest and come back, finish up 1.1.0 and then launch it. meeting deadlines is fine and well, but, when you meet deadlines with broken products or products that are badly flawed is just failure. Some how, not sure who is to blame here, but, some how, the issue with unity slipped past someone or everyone or no one <last one scares me to death> and 1.1.0 was launched. then 2 swift patches that did nothing to address the major issue didnt help. I hope they got the rest they sorely needed, I really do, because they have a mountain to fix now. MAYBE 1.1.3 will start the stability and 1.2 will weld it down, but, it needs fixing. Now, if you dont mind, I am going to go and cry for my cat now.

Nope

for me, its unplayable. I am holding onto the faintest hint of a whisper of a shadow of a boson particle of hope that the patch sometime in the "next few weeks" will make the game more stable, but, until then, for me? its 100% unplayable. the crashes are too random and too unpredictable for me to do anything.

i cant. too unstable.

@Tw1 Oh we have issues for sure. Unity has issues with mono and its causing random and fairly untraceable crashes keeping people from playing.

@mciann Anytime

@mciann they KNOW of the issue. @Claw has a thread that has or rather IS compiling information and has multiple threads linked to it, one of which is my thread on the crashing. My personal thread on this issue has the hypothesis that it is not Squad's fault, but rather an issue in Unity itself with regards to Mono and how memory is handled. I encourage you to go read through my thread, if you know a thing or two about coding, it will be enlightening to say the least. With that being said, IF it is a Unity issue, what ever patch they have in the works right now for Unity, 5.3 or 5.4 <not sure which it is, I do not follow Unity as I do not code> that may deal with it. In the mean time, from what I have gathered via converse with @Claw Squad is looking into this, what they can do or not do has not been made publicly clear. Is it disturbing that such a HUGE error slipped through? Yes and no. Given how random all of this is, how some <most I think> are affected while others like Das Valdez seem completely untouched by this issue. Crashes as a result of this particular issue <the memory handling and mono and all that as listed in the linked thread> tend to not leave crash logs in the game, have almost no common predictors or causes to trigger it. I have had it hit me 5 minutes after double clicking the icon to start the game, and up to 2 HOURS after double clicking. I have had it on the Space Center Screen, VAB, SPH, Pad, Ascent, orbit, transfers to various SOIs, descent, under chute, everywhere. Its totally random. The bottom line is this, Squad busted every hump from here to alpha centauri and back to get 1.1.0 out and yes, the patches that followed were rushed, but, they tried to deal with what they could. They needed to recharge their batteries and get a change of scenery so that now, they can look at this fresh and see what if anything THEY can do until Unity does something too. OH and @mciann it was publicly communicated by @Claw take a gander: edit: all of the above aside, I wish I was back in 1.0.5, but alas, I do not have a backup copy and the mods I ran for that variant are no longer available in that format, so, I must wait.

any further data points ladies and gentlemen?

Eeloo is a monster of a moon!! It has consumed its parent planet and Dres was the only witness but Eeloo being the meanie that it is convinced Dres to gather attention towards itself begetting the Dresian War that we all know and <your position here>! Eeloo is a monster of a moon!! It has consumed its parent planet and Dres was the only witness but Eeloo being the meanie that it is convinced Dres to gather attention towards itself begetting the Dresian War that we all know and <your position here>!

Then it's all our machines, at least those affected, which is less likely than it being unity, which seems the most likely given evidence at hand.

Its not my machine. I ran it through a series of checks as well as the game files by steam. The crashed keep indicating memory issues, which evidence indicates its unity.

<peeks out from his corner> The system is borked badly, yes it is. It needs major work, that it does. The fact that these issues have gotten to where they are <not that I am defending anything here, that I am not> is a good sign they are over worked, that they are. Rest is what was needed to bring fresh eyes into this to fix this unholy mess we have here. Now with vacation looking like it is over, fix this they can, that they must. Or more avatars and skins of evil will come forth, that they will, yes indeed.