[Kerbal Space Program patch 1.1.2 is now live!]

8 hours ago, Waxing_Kibbous said:

I think this http://bugs.kerbalspaceprogram.com/issues/7570 needs to get a higher priority regarding VAB crashes. KSP is working extra hard in the VAB now for some reason, and I'd guess crashes are either from bad code and/or overheating.

Really sad to see a changelog in 1.1.1 and 1.1.2 addressing petty "bugs" that ONE guy will submit in the tracker. Also considering that these bug fixes are the lowest common denominator. The obvious priority here is the VAB CRASHING IN 64bit. Unstable .25 builds from 2014 ran alot more stable than this. And the funny thing is modders would not touch it. I will say that Squad please take yur much needed break. You deserve it. When you come back please address the real problems with the game. 

 

6 hours ago, Steel Dragon said:

I do apologize if my statements seam hurtful or negative. I don't respond well when a developer issues a major release 1.1 then patches 1.1.1 and rapid fires a hotfix 1.1.2 then says there taking a vacation. My issue with this is where is the QA in all this? I wouldn't be as vocal if the game worked, but it does not. You can not build a ship to even see the other issues and they are going on vacation? Why do developers feel they can issue products that don't work. Example just this year XCOM 2 (a series i love) launched DOA and I still can not play it. Now KSP is RIP intell they can at least fix the VAB bug. So forgive my negativity but I'm tired of wasting my free time attempting to enjoy myself just to have the product I payed for fail.

The thing about the QA is people are just using it to play the game rather than truely test it. 

6 hours ago, Kerbart said:

I can understand your frustration, but it is very easy for the outsider to interpret your post as “overreacting.” The game is not totally broken; if there are issues in the VAB there might be something wrong with your install; I haven't seen a lot of posts about it in the forum and for me personally the VAB works fine (aside from a few minor issues, but good enough for gameplay).

Fresh install do this

5 hours ago, mciann said:

People - the CTDs appear to be related to performance.  I haven't seen any, either, but then again I'm running a quad core i7 i4770 3.5 machine with an MSI high performance gaming motherboard.  Not everyone has access to hardware that can survive whatever is going on in the VAB/SPH.

NOPE!

core i7 4770K

16 DDR3 Corsair

AMD 7870

Win 10 

CRASHES after every 7th part in VAB and 40% CTD when changing scenes

Game is simply not addressing memory correctly. Its like the game code is ignoring the fact its 64 bit 

 

5 hours ago, Kiro said:

Well after several hours of playing in career mode I was very happy to report no CTD while in VAB, ironically, as I was exiting the game, the game crashed as it got back to the main menu. I'll take it though, must be a memory leak somewhere I presume. If any DEV would like to see an output file for this, let me know.

 

 

I have an i7-5820K, 16Gb Ram, a GTX Titan X, on an ASUS X99-A motherboard. I've been having massive CTDs. Its not my hardware

DITTO , your not the only one

 

Squad needs to address the game inhibiting issues and stop wasting time on wheels. And to think that all that work on wheels was a waste due to them needing even newer version of Unity to pull it off. Just focus on what you can fix and stop the nonsence hotfix hyper releases that keep putting bandaids over the top of bloody bandaids. Heres an example of a bug fix that seems to be such high priority over serious CTD problems:

* Fixed an issue where Kerbals were able to be renamed through KB.

Seriously?

 

I do wish Squad all of luck. Constructive critic out

[Kerbal Space Program patch 1.1.1 is now live!]

2 hours ago, KocLobster said:

 

I can confirm that this is a big issue for me; I experience this crash a lot (so much so that 1.1.x is unplayable), along with crashes in flight as well. I do not know if the inflight crashes are related, or something else entirely. Going off of everybody's comments on the bug tracker, it is the same bug. The crash in-flight also produces no crash log. Very frustrating and random.

I can also confirm that this has not been fixed, as I still experience this problem with the new 1.1.1 update, on both completely fresh, unmodded installs. Having mods or no mods seems to make no difference.  

SAME here!  This build crashes more often than the non-supported 64-bit people ran back in the day. We now have massive performance, but the code was never updated to fix the crashes. Its unstable due to Unity not EVER playing well with windows. I bet 1.1 on linux is stable as hell, but if you play on linux you lose that performance gain you had on windows. I wish Squad would take this seriously.

[Kerbal Space Program update 1.1 “Turbo Charged” is now available!]

Although im somewhat relieved that 1.1 is now officially out. There is still the other half of the battle before people get too excited.......mods