AlamoVampire

blunt mode activated: until they fix the constant crashing and the plethora of other bugs, anything else is fluff. <drops the keyboard, walks off>

i would agree but im too scared to agree. so, ill just whistle quietly in the corner.

To whomever said you are not getting beyond kerbins soi with out a dv read out, look at my signature. Those ribbons represent various SOIs in ksp. I went to each without knowing my dv. Moho to eeloo . Manned to moho, duna, jool, eeloo, mun and minmus with probes to all bodies. That all being said, its almost beyond unfathomable basic information readouts are not stock.

I was thinking about this while playing a different game. Asking if KSP should have basic information like delta v or twr is like asking do liquid fueled or solid fueled rocket motors require fuel? do you need parachutes to land a capsule with no other means to slow it down? do you need electricity to power a probe core? its a BASIC thing that MUST be in game if you want to be logical about it.

from what im seeing in @Claw 's BUST thread, its starting to look more and more like a memory issue with Unity 5. as to WHY some get hit and others do not, I couldnt begin to guess.

@jedensuscg sing it man sing it! no truer words spoken.

@mikegarrison which lends MORE credibility to the memory issue, which I THINK is a Unity issue. Would you mind tossing that observation into my thread on the subject?

@Spoonman are the mods in question the most current version of the mod, for 1.1.2? i know its a silly question, but, its one that needs be asked. Edit: ScienceAlert NOT UPDATED for 1.1.X. last known update was for 1.0.4. (the fact its still showing KerbalStuff as its location AND the fact it shows its last update from almost 1 year ago is how I make this particular claim) Automated Science Sampler: Updated for 1.1.2 KSP, Last update was on May 5, 2016 to version of the mod: 1.1.3. obtained here: https://kerbokatz.github.io/#AutomatedScienceSampler

the root cause for high speed updates and patches that clearly are broken? money. that simple. They rushed <yes, RUSHED> 1.1.0 out the door well before it was ready, then rifled out 2 additional patches that fixed minor things and ignored huge glaring issues, like the current plague of game breaking crashes. While, that I think is more of UNITY's fault and not Squads, they should have seen the issue and held release off. At least then the MAJORITY of us could still play.

yes. on vacation. <grouses and walks off>

i hope to NEVER and I mean NEVER see multiplayer in this game. I am sorry to all the multiplayer fanboys out there, but, this is NOT a game that lends itself to multiplayer. There are too many ways it can go wrong. The biggest problem is, this game is so broken at the moment that its obscene to think they are considering it. They need in order of priority of things that MUST be done: 1. Fix this constant crashing. IF you are not affected by it, I am happy for you, but there is an issue either in KSP itself or Unity <leading suspicion is Unity> that has problems with memory usage that is causing ntdll.dll to yell out in frustration. 2. Address any other bugs that CAN be fixed <looking at you wheels with all your funny work arounds for one> 3. Polish career mode: as in, make it make SENSE, give people a reason to play it, give us an emotional investment. Do things logically, not just, well the player made orbit, lets have him or her try for eeloo or duna. that isnt logical, nor are those pointless go this fast use this, free money....sheesh 4. Add GP 2 and have Eeloo finally become the moon we know it is. 5. Polish graphics, add in the warm fuzzy fluffy stuff like clouds and city lights. yes, i know mods blah blah, im talkin all this as stock! 6. Double Check everything is kosher and smooth across ALL platforms, PC, Mac, PS4 and XBONE. 7. Find solutions to ALL POTENTIAL issues that WILL come up in multiplayer. Timewarp, part counts, mods, trolls, trolls, trolls, trolls, trolls, malware. 8. MAYBE consider multiplayer 2-3 years from now. Yes, I figure that is enough time to get through just points 1-4 and make sure everything doesnt break as they go. All points are my opinion, but, I figure points 1 and 2 are absolute MUSTS <game breaking issues in number 1 for a ton of people, myself included, so unstable it is right now, its unplayable> 3 just makes sense, 4 would be nice, as is 5. 6 would be mandatory imo, as not breaking things is key. 7 makes or breaks multiplayer. In 2-3 years this game MAY be able to have multiplayer, its too young, too unfinished for multiplayer to be even remotely considered. No, Multiplayer needs to take the same amount of time resources did.

@mikegarrison This adds support to a strong and growing even stronger hypothesis that its a memory call or something like that issue in unity. See my thread @Clawhas linked at the start of this query thread, it goes into detail.

I think a second runway oriented polar would be nice as well as a second pad. Associated taxi ways crawler ways would be nice too. Also some pads around kerbin would be good too. Yes i know a mod blah blah im talkin stock hehe

@Claw since i am no programmer, i can only mention what I um "hear" on here lol. BUT, again, for me, there is no sense of rhyme or reason to it, its entirely random and entirely debilitating to my ability to do anything of significance, which is why ive not touched KSP since april. I have had crashes in the VAB, SPH, pad, ascent, orbit, trans soi <read: going anywhere away from kerbin, mun, minmus, anything really> and once in the space complex screen, the one with all the buildings that practically do nothing in sandbox lol. I hope my hypothesis is of use to the team, I really do. Any chance the hypothesis can be brought up to all of the user base via a devnote or somesuch to try to focus on that area? if not, thats how it is, just a thought

@Claw the going theory in the thread i pointed at to you is its a memory call issue which may be native to unity. there is a rumor unity is going to upgrade with a patch or something <not sure how it works for game engines to be honest> to that extent in June if I remember correctly. Will you guys be using the updated engine as supposedly it will address things like the memory thing and possibly wheels? I know when <before I had to frankly give up on KSP at the moment thanks to this crashing> most of my crashes in 1.1.0, 1.1.1 and 1.1.2 all showed ntdll.dll as a contributing factor or something like that.

I have been forced to give up on KSP because of the crashes. I miss the game but the unreliable nature of the game makes it impossible to do anything larger than lob random stuff for giggles. until squad or unity correct the issue for me there is no ksp

Anyone else?

@Claw This thread should be linked into your op. some good info here on the crashes.

ive been to all bodies via probe but kerballed to moho, kerbin ofc, mun, minmus, duna and eeloo. Got it on steam at .21 fwiw

@Alshain What i am doing and succeeding at is showing situations that can happen. Remote though they may be, a chance they are. It is not my fault that you dismiss anything with less than a 85.75% chance of certainty. I can not control your exceptionally limited breadth of scope but dont you dare say my breadth of scope and accounting for possibilities down to 0.025% chance as failure. I account for things down to that small a chance, you clearly do not.

which is a bad thing. too many things can and will go wrong. this would lend itself to making your world <save> being constantly available to anyone which again = bad.