1.0 for Windows released too early?

[xtoro]

I usually play the Linux version, always have, because it just doesn't crash. With 1.0.x, I assumed it was safe to install a windows version on my windows partition. Unmodded, it crashed often. I even installed ATM to solve memory limit issues, and still get lots of crashes.

So my thought is that Squad really jumped the gun on releasing a 1.0 version. It's not stable IMO and should still be a Beta version at this point. Pretty sure if any other game dev released a game that crashes all the time, there would be outrage from the buyers. Anyone else think that we shouldn't be at 1.0 yet or is it just me? Mature replies only please....

[Cuky]

you may experience crashes due to temperature gauges causing memory leaks. I have them disabled and can play a bit modded KSP for 2 hours (haven't tried for longer yet) without crashes.

I am using Win 8.1 Pro, Intel Core 2 Duo 1,86GHz, AMD Radeon HD5450, 2GB RAM

[eddiew]

Kind of forced to disagree with you. My 1.0-1.0.2 Windows install has never crashed except for hitting memory limits - so I pay attention to how much it's using, and restart the game when it's creeping up past 3GB. In OpenGL mode, that can easily be 2-3 hours play time.

I do get hangs when a mod goes nuts and spams the debug menu, but it never happened with a pure stock game.

But investigate your error log and see what it's telling you has gone wrong, you may be finding something unique to your flavour of hardware.

[Temeter]

I'm windows only, and I don't think my KSP crashed a single time outside of the gauge memory leak thing.

[Alshain]

The only time my game has crashed was due to the temperature gauges.

[KSK]

I usually play the Linux version, always have, because it just doesn't crash. With 1.0.x, I assumed it was safe to install a windows version on my windows partition. Unmodded, it crashed often. I even installed ATM to solve memory limit issues, and still get lots of crashes.

So my thought is that Squad really jumped the gun on releasing a 1.0 version. It's not stable IMO and should still be a Beta version at this point. Pretty sure if any other game dev released a game that crashes all the time, there would be outrage from the buyers. Anyone else think that we shouldn't be at 1.0 yet or is it just me? Mature replies only please....

I was experiencing a lot of crashing myself under OS X (fortunately fixed by turning down the texture quality), so until recently I would have agreed. Not being able to play with full graphics settings is unfortunate but is a long way from being a gamebreaker for me.

I would actually flip that statement on its head and argue that the seeming lack of outrage so far (and I've personally never known a gaming community of any stripe that was shy about complaining about bugs and crashes), suggests that the game is stable enough for most players. It's not exactly representative, but taking the Steam reviews for example, I'm seeing 21,265 positive reviews to 385 negative ones. From a quick skim of a couple of pages of negative reviews, there are quite a few complaints about bugs, together with a mix of others including a number of variations on the theme of 'this game is too hard' or '1.0 is less fun than 0.9'. It's also difficult to tell whether 'bugs' on a Steam review are serious game-crashing bugs, minor annoyances, or intended features that aren't working as the reviewer expected. So even out of those 385 negative reviews, it's unclear how many are due to game instability.

So, OP has my sympathy and I hope whatever is causing the crashes gets fixed soon, but I don't think Squad were jumping the gun on 1.0.

[adinfinitum]

Same thing is happening to me, and at least a couple other people. In my case it isn't happening due to temperature gauges, it'll crash even if they've never shown.

[xtoro]

Thanks for the tips on the temp gauges, I'll try disabling them and see what happens.

As for rating the game positively, I would do the same, I love KSP. It's just from a bug /technical point of view, it's a poor release for being 1.0 and out of beta. Technically, it should still be in beta since it's not 99% stable, and needs tweaks or things disabled in order to get it to work properly, which is really my point.

[boxman]

Kind of forced to disagree with you. My 1.0-1.0.2 Windows install has never crashed except for hitting memory limits - so I pay attention to how much it's using, and restart the game when it's creeping up past 3GB. In OpenGL mode, that can easily be 2-3 hours play time.

I do get hangs when a mod goes nuts and spams the debug menu, but it never happened with a pure stock game.

But investigate your error log and see what it's telling you has gone wrong, you may be finding something unique to your flavour of hardware.

When it leaks so much memory that you only get a few hours of gameplay before running out, then that is a pretty damn serious issue.

With older versions I could play KSP all day without restarting it at all.

The only reason you did not get any crashes was because you kept restarting it.

[hellion13]

I've only been dealing with the memory leak. CKAN has a gauge killer in its list, decided to try it. Game didn't crash at all this morning.

[godefroi]

I've played on Windows for hours (8+) at a time, and never crashed 1.0.2. My current modlist is 27 long, though I don't use a bunch of big parts packs (no B9, no KW).

I do turn off the gauges whenever I see them, though.

[Temeter]

I've played on Windows for hours (8+) at a time, and never crashed 1.0.2. My current modlist is 27 long, though I don't use a bunch of big parts packs (no B9, no KW).

I do turn off the gauges whenever I see them, though.

There is a mod to autodisable gauges.

[xtoro]

Again, shouldn't have to disable things to make an out of beta version work.

[ghostbuzzer7]

Are you running the 64 bit version of KSP? Do you have enough RAM allocated to it? CPU Specs? All of these determine whether or not your computer will crash or not. For instance, I typically crash my game with 1,000 part contraptions because it can handle that amount. I don't think they rushed into it. Or may'be a little

[xtoro]

Are you running the 64 bit version of KSP? Do you have enough RAM allocated to it? CPU Specs? All of these determine whether or not your computer will crash or not. For instance, I typically crash my game with 1,000 part contraptions because it can handle that amount. I don't think they rushed into it. Or may'be a little

There is no more 64bit for windows. In Linux I do run the 64bit but I'm talking about the windows version, unmodded.

My PC is more than enough and I can launch a 600 part ship that runs just as smooth as a 2 part ship with the clock time still in green:

CPU: i7 4790K overclocked at 4.5Ghz

RAM: 16GB HyperX Fury overclocked @ 2400

Motherboard: MSI Z97-GD65 Gaming board

GPU: 2x Radeon HD 5830's crossfired and overclocked

When ships get around 1000-1200 parts, then the game starts to lag.

But my crashing issue is with ships that have less than 80 parts as well.

[WOODY01]

My memory use goes up evertime I switch focus to another vessel or launch. With the mods I am using I can switch focus or launch about 8-10 times before crashing.

[adinfinitum]

My memory use goes up evertime I switch focus to another vessel or launch. With the mods I am using I can switch focus or launch about 8-10 times before crashing.

That seems to be the problem for me. The more I switch views, the faster it crashes.

[be77solo]

I don't run many mods, mostly stock (actually just "plane mode" that swaps yaw/roll), and have yet to have a crash with 1.0(or .02).... played a good bit recently, several hours at a time, without issue. I'm actually really happy with the current state, and glad they did push the aero and final features in a timely fashion. Very pleased with the game, best version yet by far IMHO. I've never monitored memory usage, have no idea what it is using.

[Bill Phil]

My install only crashed after about 5 hours of play for 1.0, and my hardware is pretty low end. All stock. 1.0 gave me a huge performance increase.

It did freeze for a minute a day ago, but I was doing a lot of science. Normally I would click on the window and it would say, "KSP is not responding." Then I'd end it. But I let this one sit a bit and it worked out pretty well.

[WOODY01]

That seems to be the problem for me. The more I switch views, the faster it crashes.

I did not have this problem pre 1.0. The only crashes I suffered previously was a result of me trying to push the limit on the number of mods I used.

[TheMoonRover]

Personally I've had nothing I would consider to be a major problem with 1.0

I have had precisely one game crash, and that took me quite a lot of effort. I was trying to verify the temperature gauges memory leak. It took me a good half hour to do so.

As for noticeable bugs, nothing except for one occurrence of the hell kraken, and I was definitely taunting it, having so many kerbals on EVA in one place with an outdated planet mod installed. (That's been removed now)

So I'd say that's fair

Although it still lags a little too much for my liking. I doubt it'll improve much until the Physics engine is multithreaded*. 64-bit would be nice too. But apparently that's coming Soon

*Yes I know the game is multithreaded, but the Physics engine is single-threaded, so it can only use one-quarter of my i3 processor.

[adinfinitum]

I did not have this problem pre 1.0. The only crashes I suffered previously was a result of me trying to push the limit on the number of mods I used.

I never really used many mods other than KAC and KER before 1.0.x, and I don't recall ever having an issue with the game crashing. Now it seems to be almost every hour of playtime.

[Bobnova]

Memory leaks are the sort of thing that the beta phase is supposed to fix, so yes it was released too soon.

A memory leak in a finished game is a big issue, very big.

I love the game, but I'm disappointed that something as buggy as the 1.0.0 was a "full release".

[Bill Phil]

Memory leaks are the sort of thing that the beta phase is supposed to fix, so yes it was released too soon.

A memory leak in a finished game is a big issue, very big.

I love the game, but I'm disappointed that something as buggy as the 1.0.0 was a "full release".

It was great, in terms of bug fixes.

And the the heat bars are optional gameplay mechanics. They aren't essential to the game... And they have the biggest bug since 1.0.0.

The fairings are a bit quirky, though.

[Merinsan]

I have to say, version 1.0 seems to be significantly less stable than 0.90. I used to be able to play all day without an issue. Now the game crashes fairly regularly.

In fact, I've had a total of maybe 10 crashes ever while playing KSP. 9 of those were in 1.0.