OK, I have this philosophy of not upgrading or changing anything if I'm happy with whatever it is I'm using. So, the NGX has been working fine. I'm not 'into' the plane as seriously as some of the guys around here. I mean I'm not a RW pilot, I don't fly 737s for a living and I don't use every single switch to fly the plane. I do however, strart from dark and cold, programme the CDU and instruct a proper flight plan. So why, I ask myself should I install SP2, 'cos that's what you're supposed to do I told myself. After installing SP2 last week, I have no longer been able to start a flight at an airport without first loading a default aircraft. This was not the case prior to SP2. Anyway, I understand lots of guys recommend this anyway, although it has never been a problem with me. I have now been following this procedure. Yesterday was the first time I have had a freeze since building my new rig three months back. It happened while reprogramming info in the CDU during a flight from EGLL. OK I thought, I'll reboot and use one of the last saves from FSUIPC, a brilliant aspect of the program. Anyway, you guessed, the flight would not load. No way would it loaded. I tried loading the plane on the ground in similar scenery and then reloading the saved flight, I tried loading the flight with all scenery sliders turned down, to no avail. In other words my entire flight and pre flight had been wasted. So, it appears this may be a problem attributable to SP2. It is not, or has ever been, a problem with SP1. So today I have uninstalled SP2 and gone back to SP1 and it all works fine. I can load the aircraft at an airport and the autosave feature works flawlesly. Interesting. Has anyone else experienced this? EDIT: BY SP2 I MEAN SP1b

Edited January 5, 201214 yr by Rockliffe

By SP2, do you really mean SP1b? Or do you mean SP1 as the original release and SP2 as SP1?If latter is the case, be advises, that save files, as well as panel state files, and aircraft config files, are not compatibile between versions.

By SP2, do you really mean SP1b? Or do you mean SP1 as the original release and SP2 as SP1?If latter is the case, be advises, that save files, as well as panel state files, and aircraft config files, are not compatibile between versions.

Sorry, sure, I mean the latest release SP1b. No, the save states were not saved from one version to the other, these were clean saves made from within the new install.

If you have the plane set to load the cold and dark panel state at startup this will definately cause problems when trying to load an FSUIPC Autosaved Flight. This is an absolute do not do!Here is how I do it. Load up the NGX in the default configuration with the engines running. Then go to the FMC and select Load Cold and Dark. Doing it this way I rarely ever have trouble loading an autosave whether it is on the ground or in the air. I had the same problem like yours when I had set the FMC to automatically load a cold and dark state at the begining of every flight. Once I removed this and went back to the default NGX state it works fine.Give it a try and then come back and let us know how it worked out.My guess on what is happening is this. If you have Cold and Dark setup by default it overides FSUIPC Autosave and you end up with a Dark Cockpit.

Edited January 5, 201214 yr by UAL115

Try here:http://forum.avsim.net/topic/352155-post-sp1-do-not-use-old-panel-states-and-option-inis/Sounds like that's most of your issue. It's more than just installing the SP. There's a little work that needs to be done on the end user's side unfortunately.

Thanks for clearing that up Paul and also Kyle for the link, cheers.

You're welcome. Hopefully that helps.

Going to give it a go shortly so I'll let you know how I get on