Thanks for the clarification, Ryan..'nuff said..pause here I come :)..I reckon I'll need to use two PC's now..ho hum :(

The only way to make something like that save would be to model it inaccurately and non-dynamically.

And we don't want that. :( I asked what I did because I thought it should be possible, but now I know it isn't, that's ok with me. I hardly ever have to save a flight in mid air: the last time I did it was because I wanted to change a setting in FSX that required a restart: nothing really important and the next time I will simply finish my flight and change that setting later on. No big deal. Thanks for the reply!

I don't understand pausing and saving a panel state, then saving the flight through FSX. I just save the FSX flight and a panel state save is created automatically. Is it really any different by hitting pause? Can someone elaborate a little on this?

Bump.

I don't think it is any different whether you only save in FSX or save in FSX AND save the state in the 737NGX. When you save a flight, the state is saved anyway, so... it's all the same and both ways of doing things aren't guarenteed to work.

I don't think it is any different whether you only save in FSX or save in FSX AND save the state in the 737NGX. When you save a flight, the state is saved anyway, so... it's all the same and both ways of doing things aren't guarenteed to work.

But if you save a panel state, doesn't it save only that and not your FMC settings?

For me when I save a flight through the FS menu, it will save the flight, and it will create a panel state too. In that it will have the FMC settings, so when I go to load a flight that is in the air everything is all set. But, there are times where the screens stay blank, the VNAV refuses to work, or other weird things.

Guys,There's a very good reason certain things can't be saved properly in the panel state: The NGX is essentially a giant dynamic calculation and the systems are always responding to values being fed into them by other systems and so on. When the plane is first loaded, some of these system don't have values until everything else gets going - this is the reason you see VNAV disconnected and stuff like that. It's just the way it is and the price we pay for simulating the systems in this way. The only way to make something like that save would be to model it inaccurately and non-dynamically.

Ryan, those reasons are understandable. However, I experienced some strange situations that I wanted to recover a flight (even on ground) where the saved situation just gave me back a blank panel with no function at all - it even did not work when loading a situation 3 or 6 minutes before (stored by Autosave). It's seldom but it happens, recently even in a quite remote area with no real memory and CPU load.