This comes up from time to time with all my aircraft when astute observers notice it. This is just the behavior of the native MSFS autopilot implementation in approach mode, I'm afraid. Some 3rd part avionics developers have undertaken the substantial effort of developing their own completely independent autopilot can avoid this shortcoming. Starship would be an ideal candidate, if I was ever going to explore doing this, because my other aircraft are hamstrung by 3rd party avionics support and interoperability.

@Mark Are you still in discussions with Asobo on this issue? I see it's still not resolved in SU5

Could I kindly ask you to open a support ticket via the following link: https://www.justflight.com/support In the ticket, if you could provide the same information you have in your forum post for how we can reproduce the crash (departure airport, SID, etc.), then our support team will be in the best position to be able to look into this further. Mark - Just Flight

Thank you for your interest, and it was great to meet so many passionate community members at FS Weekend! We have been posting a few updates on our social media channels over the last few weeks, highlighting the latest progress. Our latest in-development article (and an updated Detailed Description) can be found here: https://www.justflight.com/in-development/f70-f100-professional-bundle The finish line is in sight now, and we can't wait for everyone to experience the F70 and F100 in their simulators. Mark - Just Flight

Thanks for the interest. The F70 Professional and F100 Professional will support the MSFS 2024 Walkaround mode with interactable doors and ground equipment. The full feature set can be found on the in-development page: https://www.justflight.com/in-development/f70-f100-professional-bundle Mark - Just Flight

Thanks for the interest! The information in the 'Detailed Description' section of the in-development page will be the feature set of the release build: https://www.justflight.com/in-development/f70-f100-professional-bundle As with our other products, we will support the F70 and F100 for many years after the initial release, and during that time, we will undoubtedly add new features and improvements. We're not ready to commit to what those may be at this stage, but a big part of it will be driven by community feedback. Mark - Just Flight

Probably a typo. Restarting the flight (open the menu and click Restart) and then quitting is the community workaround until Asobo finally fixes it for good.

Before agreeing, is the HOBBS unique to livery, if it is not I have see the same. back to 0.

Thank you all. You both nailed it. Changed fuel type to Jet-A (external TDS interface) [image: e424cccc-c1e2-4602-a7fa-eafbedf9a39b.png] Issue fixed [image: 5ccdc9ea-7cf9-4daf-9600-a042aece7912.png]

Finally problem solved, I contacted JustFlight support directly and the correct file was made available. They claimed that they sent the correct files to simMarket, in short it was a problem with the store's support, and only today (8) did they correct the problem by making the correct aircraft file available.

I suppose the quality might be objectively better, but I actually prefer the Duke soundset overall - much 'growlier'. Just goes to show this kind of stuff is in the ears of the beholder..

my 2 cents. i have no need for hot swap. i am fine installing the variant i want, so GTN or GNS. and cant you reduce your variants offered. do you really need single dual GTN, 750, 650, GNS GTNXI each and every combination. i understood that Avidyne is a one to one replacement for the GNS530, so no changes in the 3d model needed. would love to see the Avidyne in the Duke for example or TBM850.

Ah, thank you for uploading the video. That's exactly what I needed to see what you were talking about. That is an artifact of MSFS 2024's exposure compensation. You might be familiar with exposure compensation as the bright white skies you experience for a few seconds when looking up from a dark instrument panel. There are settings related to exposure compensation in the simulator's graphics menu, and you might be able to find more online about how to fine tune this feature. Please let me know if there is anything else I can do for you in the meantime.

Yes, the multimeter is on the generator setting, and the generator is on line. As for the prop heat, I'll give it a little longer after switching it on to see if it changes. Thanks for your help.

@Black-Square said in V1.2. update and fuel tank selectors: (A:TURB ENG TANK SELECTOR:1, Enum) 0 == (A:SIM ON GROUND, bool) ! and if{ 1 (>K:FUEL_SELECTOR_SET) (A:TURB ENG IGNITION SWITCH:1, bool) ! if{ (>K:TURBINE_IGNITION_SWITCH_TOGGLE) } } Thanks for the reply... but no, the starter still does not engage. I can flip the starter switch with the mouse, and that gets the engine going again.. After a couple of tests, I have found that this step is actually quite straight forward, and the engine responds quickly enough that I can avoid big trouble

The external pilot is still a "multiplayer - group flight" feature in SU5. I am guessing that this is not a priority bug, but I would like to see it addressed.

Thanks for the anwser. Guess I will find out. Also thanks for the amazing products. Really enjoy them.

@jmarkows the L:var_WindShieldDeiceSwitch_IsDown is not available

@Black-Square Yes, the protection activated even with both items in failure. Regarding the injectors, wouldn't it be better to treat this as a general failure rather than a clog? In the engine animation on the tablet, you can notice the absence of fuel injection (it looks like a small droplet). And finally, in the case of the R ENG DRIVEN FUEL PUMP, the logic is just reversed for it to be activated on the correct engine.