Do you expect your crafts to still work in 1.1?

[Grumman]

I would suggest evacuating the crews back to Kerbin, but leaving infrastructure where it is. That way, if anything breaks you're not losing anything important, and it's an interesting challenge to pass the time until 1.1 gets here.

[lodger]

I think remember seeing a statement from squad about keeping save files compatible after the 1.0 release. (But loading and being actually usable could be different things)

Well, that didn't work either. Saves from 1.0.0 won't work on 1.0.2 or 1.0.4 without manually tweaking the savegame file (remember the heatshield issue). So no, I don't expect savegames to work in 1.1

However, it is quite likely that 1.1 introduces new parts, new features etc. so starting all over with a new game will be the best thing to do.

[DocMoriarty]

I don't really care. It has always been a good idea to start a new career in new releases due to minor, often hidden, incompatibilities. And there is still the option to copy craft files from old saves to new ones and refine them if needed.

[cantab]

I expect my craft to load and basically work in 1.1. Engines thrust, wheels drive, parachutes open, that kind of thing. I'll give a little leeway for things like reaction wheels maybe being taken out of probe cores. And of course the NotAntennaRange thing, but that's expected to be on a difficulty option anyway.

I don't expect them to perform identically. If an interplanetary probe built as an orbiter takes a delta-V drop that means it can't close its orbit, or a formerly-stable aeroplane becomes unflyable, that will be no surprise and won't bother me too much.

I expect my save to load, preferably but not necessarily without me having to tinker with it. In the unlikely event it doesn't, then after raging at Squad I'll get to jumpstarting a new science save to be as close a match as is reasonable. I'm certainly not going through the cookie-cutter early stages of it again.

[Dfthu]

I always get a fresh new save when a new update comes out.

[ModZero]

I do hope the update will make them work, yes...

[Aladran]

I just hope to finish my grand tour before 1.1. If not I fear for my probes and the probable antenna problem.

[Nathair]

Put me down with the start-a-new-career-anyway crowd. Will 1.1 make me dump RemoteTech, that's what I'm wondering about.

[Fearless Son]

I expect most of my craft would continue to work in 1.1. Some of my more distant probes might stop responding, but they are safely parked (in orbit or on a surface, depending on the probe) and should reactivate when they come within range of an appropriate antenna.

[Slam_Jones]

Eh, honestly, my designs are basic (uninspired) enough that I can replicate them as needed. Not really bothered if they break on update.

[steve_v]

I think remember seeing a statement from squad about keeping save files compatible after the 1.0 release. (But loading and being actually usable could be different things)

Aha, that must be why 1.0.3 broke all craft with a heatshield.

[RocketBlam]

I've never much cared one way or the other. Designing the craft is half of the fun. Just reloading an old craft that you know will work isn't much fun to me.

[Higgs]

I'd say with how major an update 1.1 is I fully expect everything to break. On a personal note I hope the stock fairings are replaced by better fairings like the mod procedural fairings, if not, ill still use that mod as its a thousand times better IMHO.

[Mitchz95]

I use a lot of mods, so probably not. But that's fine, I was planning to start a new game anyway.

[juanml82]

There are no changes to phsyics nor parts IIRC, so ships should work. The potential problem is the whole antenna thing for probes, which I guess it can be disabled.

Other than that, I doubt wheels will break. If anything, they should work better.

The other problem are mods, specially mod wheels, which are likely to take some time to update

[Rus-Evo]

I will have a vastly more powerful computer in a couple of months...... I might hold off till I get it running. Did someone mention use of multi cores..... As it will be my first quad core (bit out of the loop)

[cantab]

Aha, that must be why 1.0.3 broke all craft with a heatshield.

That was a bug for which a hotfix was quickly issued. Squad hadn't intended to break compatibility.

[Mister Dilsby]

1.1 is going to be a new experience for me; so far I've started my career save over with each significant rev and made all new crafts. This time I have story continuity to think of, so I want to keep the save even if none of the crafts work anymore. Hence I have a lot of work going on now "behind-the-scenes" to bring crews home from Mun and Minmus with as much soon-to-be-obsolete hardware as we can salvage.

[lost_in_space]

I just hope they make a working patcher this time. I've never bought a game before that had to be re-installed, with files copied over manually, whenever it was updated. I hope they make a patch that can handle all this automatically.

[Jett_Quasar]

To avoid disappointment always assume that you will have to start from scratch for each update. That way if things still work you can be pleasantly surprised instead of the other way around.

JR

[Caelib]

I nuke-and-pave my saves on every major update so it doesn't matter to me.

[dr_jt]

With every release I pretty much start over so the possibility of my saved craft working is never a consideration. I guess if I had extensive mining or station stuff going on I would like that carry it over, but I don't at this time so I'll just start over. I prefer Sandbox, but when the science first came out I played it through. I have yet to play contracts so maybe I'll try them out.

[artao]

Now that the game is a full, not beta- 1.x release, I would expect save games to be compatible across releases, yes.

It was in beta for so long, I think we all got too used to just re-starting with every new release.

But now that it's an official full release, I think we should be able to expect more. Having to re-start a career after putting countless hours into it really can suck .. particularly for people new to the game, that haven't experienced the dev cycle which broke saves. That's acceptable during alpha and beta phases, but I don't think it is after that.

That said, the fact that it's switching over to Unity 5 may very well, in and of itself, break game saves. I don't know. If that's the case this time, I'd understand. But once it's in Unity 5, I'd expect saves to remain compatible and stable throughout updates.

[Technical Ben]

A "save converter" is not totally unreasonable or impossible in most instances (assuming parts don't change, just their stats).