For me, with PMDG planes, saving the scenario is indeed saving the panel state and FMC state.  It's the whole ball of wax.

I do restart the sim between each flight, every time.  In fact, I usually reboot the entire PC just to make sure I'm starting with a perfectly clean slate - who wants to spend 3 hours flying just to have the sim crash due to all the other programs you were using earlier that day?  Nope, something starts getting "carried forward" with 15+ scenarios in a row saved/loaded and minor odd things start happening, from stutters to the inability to use certain aspects of the Autopilot.  When it happens, I just consider it a good reason to hand-fly the rest of the journey, and then manually recreate the flight at the destination from scratch.  For me, it's small potatoes issue.

Mark

 

Did you try a default or known panelstate?

6 hours ago, SteveW said:

FSUIPC programmatically invokes the menu save-game command - producing the same fxml file as manually pulling down the P3D menu and saving. Forget FSUIPC for the moment as it's not a requirement, there's no need to confuse others coming to the forum.

Manually saving simply allows completion of the flight notes and to save the file with any name we like at the time.

You have to check the documentation that comes with an aircraft to see what, if anything, is saved automatically during the save-game. Also check it works when the save-game is invoked programmatically. If not then an auto-save tool is not helping.

If not then the FMC would have a save panel-state command. SO you might have to do that as well as save. Pause the flight - save the flight - save the panel state - restart the sim, load the flight - load the panel state.

Yea Steve, it's saving the panel state so the fuel and other stuff is being saved, but the actually aircraft state is NOT being saved.  I turned everything off before I saved and shutdown the sim.  When I launched it again, it loaded the panel state correctly, but all the buttons and switches on the overhead panel were back to what they normally are during the load.  I think it's the aircraft possibly.  I'm currently using the QW 787, and it does it's "initialization, please wait 30 seconds" thing when I load in.   

I have not tried with the PMDG 777 yet but I'm going to assume it's the same deal.  

I currently own your Ideal Flight addon but not for the P3D v4 yet, I only have the FSX version.  I can't remember if the saving in Ideal Flight saved the actual aircraft state or if it was just saving the parking location.

Maybe this is what you're looking for?

 

5 hours ago, joejccva71 said:

I currently own your Ideal Flight addon but not for the P3D v4 yet, I only have the FSX version.  I can't remember if the saving in Ideal Flight saved the actual aircraft state or if it was just saving the parking location.

Thanks for supporting. That app invokes the P3D save-game keeps the fxml and plan names cooperative since the panelstate's usually reflect the flight file name - that's a reliable method.

If an aircraft has to keep extra settings then it can sense the savegame event in the sim even if it is invoked by an app, but it's got to be checked first. It can save it's own setting and reload when the plane next starts - depends on the aircraft - hence my point about trying it all out first without automating.

5 hours ago, SteveW said:

Thanks for supporting. That app invokes the P3D save-game keeps the fxml and plan names cooperative since the panelstate's usually reflect the flight file name - that's a reliable method.

If an aircraft has to keep extra settings then it can sense the savegame event in the sim even if it is invoked by an app, but it's got to be checked first. It can save it's own setting and reload when the plane next starts - depends on the aircraft - hence my point about trying it all out first without automating.

Awesome Steve.

By the way, I did some more testing and the Quality Wings 787 series does not "behave" like the PMDG 777 does.  I tried doing the panel state saves on the PMDG and it saved everything (including the overhead panel switches) exactly as it was when I left it which makes me believe I'm using the exact same aircraft.  The QW787 does not.  It saves some things, but the switches on the overhead panel reset back to "ON", etc.

13 minutes ago, joejccva71 said:

Awesome Steve.

By the way, I did some more testing and the Quality Wings 787 series does not "behave" like the PMDG 777 does.  I tried doing the panel state saves on the PMDG and it saved everything (including the overhead panel switches) exactly as it was when I left it which makes me believe I'm using the exact same aircraft.  The QW787 does not.  It saves some things, but the switches on the overhead panel reset back to "ON", etc.

Yes, there's no doubt some aircraft systems go the extra mile.

It annoys the hell out of me when I am not able to save a panel state properly. The PMDG planes do this with style, which is one of the reasons why I am flying them exclusively these days. If the FSL Airbus A320-X and A319-X make the grade in this department, then hopefully I can look forward to flying those planes when I eventually upgrade to a 64bit version of P3D.

It's worth noting that when I refer to "saving a panel state properly", I do not mean having it saved automatically after every flight (which then transfers to my next flight, irrespective of whether I want it or not). The panel state in the PMDG planes is not automatically saved, but it can be saved manually. There is a massive difference.

Edited September 5, 20187 yr by Christopher Low

The TFDi B-717 has a persistent panel option that works quite well if your interested in arguably the best regional jet currently available. I get sloppy in my shutdown procedures sometimes I get reminded of this as I work through the checklist on the next flight.

The persistent panel option in the TFDi Design Boeing 717 is a classic example of what I do not want. It saves the panel state automatically every time that I leave the simulator, which is useless to me.

2 hours ago, Blaze said:

The TFDi B-717 has a persistent panel option that works quite well if your interested in arguably the best regional jet currently available. I get sloppy in my shutdown procedures sometimes I get reminded of this as I work through the checklist on the next flight.

This looks great!  I might actually buy this.  So you believe that this aircraft is on par with the PMDG 777?

Edited September 5, 20187 yr by joejccva71

On 9/5/2018 at 1:33 PM, Christopher Low said:

is a classic example of what I do not want

Sorry Man, I should have made it more clear I was referring to the OP, Joejccva71

 

On 9/5/2018 at 2:45 PM, joejccva71 said:

This looks great!  I might actually buy this.  So you believe that this aircraft is on par with the PMDG 777?

Well, they are apples and oranges in aircraft type and purpose but IMO at it's current state I think it's entering into that realm, they have put a lot of effort into it since it's initial troublesome release and I think it's arguably the best regional jet simulated in P3Dv4. I don't believe it has failures simulated which is something the PMDG 777 does but then again it has some options the PMDG 777 doesn't ie. TrueGlass, shared cockpit etc. It's a great plane, I'm sure you'd enjoy it. System wise it's very similar to the MD-11 which never made it to P3dv4 but in a regional jet platform. I'd also add it is a very enjoyable hand flying aircraft and I often fly the entire SID STAR before engaging the AP.

I always found it to be a rather strange aircraft to hand fly, as it refused to pitch up or down to any meaningful extent after significant changes to engine power. I have been told that this is how the real aircraft flies, but it seemed very odd to me.

To TS: With SmartStarter w/Maplog you have the very best PMDG start procedure.