@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.

@OELVA Saucer of milk?

@Black-Square sweet!

I myself am aware. But Im just dreaming and hoping. I appreciate the invested time and effort you are doing with all the new stuff, dont get me wrong. I'm just being wishful. Please keep up the AWESOME work!

@Derek Hi, I completely forgot to put Just Flight and Black Square

@Black-Square flagging for your attention - we need our furry friends in the cockpit! Thank you

@CdnCptMoustache I just looked into this, and that variable is only set to zero in the Turbine Duke, and Starship. There's a high probability it was a mistake, and I copied it over to Starship, but I will test things out and see if that's the proper solution before the next update. Thanks for pointing it out. This problem was on my list, but I haven't thought about it in a while.

Glass out does a pretty good job of finding most screens and instruments (not all). Most of these are from glassout - they look exactly like the starship cockpit above. [image: 3c0b01b5-61dc-413a-9454-08c6e6eafa5a.jpeg]

I have raised a support ticket for this as it seems broken and also same on the Arrow III / Warrior II and Tomahawk as I have just tested. Can not be sure but perhaps this issue arrived with the new Configuration option on the EFB for Fuel and Payload? Hopefully the save state across these aircraft can be checked and fixed where needed as it is always nice to get into an aircraft in the state it was left. Cheers Matt

Indeed, I am suffering from this bug as well, but only in MSFS2024 - in my case in every flight in MSFS 2024, also not using any addons that could interfere with the flight model. In MSFS2020 both F70 and F100 fly very accurately and there are never any issues with the autopilot being unable to follow the path as computed by FMC.