That is the best news ever!

@jmarkows Yes, I always exit using End Flight or Main Menu, depending on if I want to go for another flight or finish up for the session. I have never exited from the Sim using the Stop button in Steam or closing the window via Windows, unless it's frozen. Either way, the state saving doesn't function as expected. See testing performed recently in this thread: Aircraft Configuration Not Saved In MSFS 2024 @Tadeus72 Yeah, I didn't notice a difference between either the End Flight and Main Menu button exit methods either; both seemed to result in the same aircraft state upon reload when tested in the previously mentioned tests.

@Mark said in Aircraft Configuration Not Saved in MSFS2024: All of the items listed are included in our state-saving logic (and I have seen them save/recall correctly in the current build), but there is something which is causing discrepancies with the state saving with each load of an aircraft in a session. It's something we are actively investigating across various products. Mark - Just Flight @Mark Thanks for the heads up about the other thread. I have commented on that one as well and put in on watch in hopes something will turn up one day about it being resolved, or at least a work around of some sort. Although, as things tend to trend with MSFS from version to version, it might just be broken the next update. It's interesting that you mention you have seen them save/recall correctly in the current SU4 build; I would believe that. When testing earlier, there was an inconsistency in the behaviour of state saving, as not all items saved and recalled correctly on the first try. During the initial tests mentioned previously, the Fuel Pump Switch state reset back to OFF, even though it was switched ON before exiting the flight. However, all of the following tests it would remain in the ON or OFF state as expected upon save and restart. Likewise, the Transponder Code wouldn't always reset back to 7000, but would rather reset back to another value such as 2000, 7004, along with the standard 7000 - it would never set back to the pre-save value of 1200 though. The inconsistency adds to the frustration and makes it more difficult to debug, especially if the person trying to debug it doesn't have the code in front of them. Question for you and others on this thread: Have there been any workarounds that seem to result in an improved state recall, or has it just been inconsistent no matter the method? Thanks.

I have my fingers and toes crossed for this. I honestly believe I wouldnt fly anything else if we had G3X in the Bonanza and Barons.

Just tried it. Secret was to choose gear up option on PRESS and same button for gear down on RELEASE Anyway, sorted now

Glad to hear that you're enjoying the Bonanza. I recently found that I missed including the vent variables in the temperature simulation, so currently they only influence the rate of temperature equalization if you are not actively heating or cooling the cabin. I'll fix this for the next update. You are also correct that the door seals only serve to reduce noise in the unpressurized Turbine Bonanza. Let me know if you have any more questions! You know where to find me.

Hey Nick, hope you are well. Looks like i'm not the only customer looking forward to a G3x integration... Any news? Xavier

I think this is the well-known MSFS24 problem with turbulence settings in conjunction with terrain and real weather (wind changes of 30kts or more in less than a second, perhaps poorly simulated windshear-stuff or updrafts/downdrafts). There is also some discussion about this in the MSFS forums. I experienced this myself last week in Nuuk (BGGH, RWY22). For several hours (under real weather conditions), there was a repeatable effect where ANY aircraft would simply drop like a stone about 200 meters before touchdown because all lift was completely gone in a fraction of a second. This could only be fixed with turbulence set to medium or low. I suppose, because Starship's front wing stalls first, the aircraft goes hard nose down.

Well, you learn something everyday. Makes sense. Thanks for replying.

@Black-Square Disabling AI Trim helped. The noise is gone. I also had the noise in the Piston and the Grand Duke; it seems to affect all BlackSquare aircraft.

It's looking like a TDS issue, there's a beta fix available on their discord, in case anyone else ends up at this post looking for something similar.

Thank you for your reply, but not what I'm looking for. I'm talking about things like RNP AR, LPV and RF-leg capability etc. The kind of info you need in order to figure out if a certain RNP approach is allowed or not. Operator approval is also a factor, but that's going to vary from airline to airline.

@Mark, Many thanks for getting back to me. The only odd thing is the entry lights. When you start the APU or connect the GPU in the dark, the cockpit is illuminated well as the panel flood (X2) and console flood are all lit - making the entry lights a bit pointless. Also, if you switch the entry lights on using either of the cockpit switches - it also turns on the entry lights in the galley - but the galley entry light switch then has no impact. If entry lights are off in the cockpit then the galley switch turns the galley entry lighting on/off as expected. Just seems a bit illogical to me, however, maybe that's how it works on the real aircraft. Regards, Neil.

Hi @haggster -> This has also been driving me nuts as well since I bought the Professional package lately, always happends after a landing after shutting engine off, did some troubleshooting & might have found the issue, for me it seem to help (issue gone) after turning off AI Auto-Trim in FS2024 - Settings / Assistances / AI Auto-Trim (OFF), strange thing is that this seem only to be an issue when using the black square Bonanza & Baron Professional (the only 2x planes I have), try and see if changing this setting also helps in your scenario.

@Derek said in PA-28R Turbo Arrow IV FS 2024 displayed wrong: Have you tried contacting Just Flight Support about this? It sounds like the kind of problem they could advise upon. https://community.justflight.com/topic/2/product-support Thanks, and sorry to the forum, I have sent a ticket, maybe this post can be closed.