Update - Just went through everything again, made sure my physical default control positions matched the proper pt6 “just started” state and everything worked as expected, no abnormal issues. I restarted everything and went through it a few more times and everything worked correctly. For now the problem now seems resolved for me.

@Cpt-Holden No, thank you! That makes my day to hear It's become one of my favorites too! "A proper cruising machine" I often think to myself.

I haven't, I learn better from reading and trying than videos personally(big props for the detailed manuals, I hate it when sim planes don't come with a good written manual). Haha on my first flight I was like 'huh, this thing doesn't have an HSI? Weird, seems like it would.' And then when I was just manually lining up with the magenta line I saw the lights start moving on the digital localizer and had the lightbulb 'oh that's what that's for' moment. Hey, thanks for always making such great planes and being so responsive to the community!

Would be good to hear about this. It looks a bit better on the actual aircraft in sim but I'm still not sure.

@Black-Square said in New and improved state saving: @Bishop I've been up all night monitoring the 114 release, so I've been slowly working on the code rewrites required to bring this to all my other aircraft. Glad tp hear you're looking forward to it, because this one is a lot of work. Wow, I recall you mentioning somewhere on the forum long ago just what a time consuming project that would be.... Many thanks and appreciation! Wild to get that kind of enhancement for free.

Nope. Not uncommon on piston singles to not have aileron trim. You can get it to fly straight if a bit uncoordinated with rudder trim, otherwise just need to keep a finger on the controls or turn on the autopilot

@Mark It does. Thank you for the reply! Absolutely love this plane!

@Black-Square Thanks a lot, Nick! Initially, I only wanted to change the carpet, but then one thing led to another!

Soooooo….. nothing yet ?

Done, Thanks

Thanks, I finally later found the solution by using simconnect flaps_incr but I have to add 16384 in the parameter field. I don't know why! [image: 4309032e-3be2-4e58-8706-d384da46b97a.png]

I know this is a REALLY old post, but with the success of the old and "new" aircraft from JF(146 and RJ along with the F28 and F70/100), I'm curious if you guys are still considering another old and "new" progression with the A300, doing the rest of the family once the A300-200 is done. I know ini already has their A300-600 and default A310, but they're really lacking in variants(at least for the A310 with only the pax 300 with GE engines), and they're a mile wide but an inch deep. I think you guys could do a stellar job with the A300-600 and A310s after seeing how well the RJ and F70/100 turned out, and I think the gap in the market to justify it is still there. I also am not a developer so I have no idea how accurate this is, but the relative commonality between the F70/100 systems(especially sharing the honeywell pegasus FMS) seems like something that could be leveraged to reduce development time and effort, but that's something for the real devs in the room to evaluate.

Thanks. Basically, yes, that's the same or very similar. In its simplest form, I save the control binding profile and livery for the Grand Duke, but upon next MSFS2024 startup, it's reverted and I have to select each of the profiles again (although from memory I think one of them is OK, but I can't be sure) - the livery certainly isn't and at least 2 of the 3 profile settings have to be re-selected. However, for the Stock Duke and Turbine Duke, the 3 x control binding profiles and the chosen livery remain in place from my previous 'save', even after shutdown and fresh re-start. It's only the Grand Duke that continues to fail in this regard.