MSFS Products

@JRHorse that's essentially the point... (within safe margins)

@jmarkows said in OK ... I'll be the one to ask.: @Black-Square said in OK ... I'll be the one to ask.: No rest for the wicked over here. I'm waiting for SU3 to see if I can enable the custom registration numbers before the next update. About this, do you have it disabled for the entire plane, or just the liveries that came with it? I have a friend who dabbles in photoshop and does the liveries for our VA; he made one for Starship and insists the dynamic registration has never not worked for him in 2024, whereas it's never once worked for me. Since SU3 Beta, it has not worked for me 90% of the time. However, if you are patient, you CAN get it to show up. First of all, the system needs to be enabled. I did it for all liveries (default and my own) by removing the "//" at the appropriate part of the panel.cfg. Then, I open a default airplane e.g. B748. I configure it and set the registration number of my Starship. Save & Go Back. Once on the home screen, select the Starship and your particular livery. 75% of the time, after the prop brake populates on the model, your registry will also appear. If not, go back and forth between the default and Starship. It's shameful that something like this has a mind of its own. But at least I can fly with a reg. 100% of the time in SU3. Only the amount of patience varies a bit.

@miked176766 I think I have found the problem. I purchased the PA38 Tomahawk on the MSFS 2020 Marketplace and this updated in MSFS 2020 on Friday (20/06/25). This worked fine in MSFS 2020. I ran MSFS 2024 and looked in my Library for the PA38 Tomahawk which still shows as the 2020 version not certified for MSFS 2024. I set this version to install and stream. On running the aircraft it loaded and allowed me to enter the cockpit. I tested for full control movement stick and rudder which both showed full movement. On starting the engine I could only get aileron movement, no elevator or rudder. With this version still set to stream the loss of elevator and rudder is passed on to the PA28’s that are installed as MS 2024 certified. If I then set the PA 38 to disabled the PA 28’s all return to normal rudder and aileron behaviour. My conclusion is that until we have an MSFS 2024 certified copy of the PA38 Tomahawk in the marketplace this problem will persist.

@Delta558 thanks for checking! Of course not, but knowing pilots making error (which is how I ended up even thinking about this)

The F70 and F100 won't have a failure system at release, but its on the feature request tracker as something to consider post-release. Mark - Just Flight

@kutyafal I’m having the exact same issue.

Injected aircrafts will be only displayed if I really near. Is it possible that I see it from a greater distance?

The throttle axis snapping between IDLE and 100% is likely the result of the control conflict. Do you perhaps have any controls assigned to "TOGGLE ENGINE 1 FUEL VALVE" or "SET ENGINE 1 FUEL VALVE"? Those assignments are used to move the throttle lever between the HP OFF and IDLE positions, so they could be 'fighting' against the throttle axis position. Mark - Just Flight

Thanks Mark, I can use the joystick on the index controllers so I've got a work around in the mean time. Appreciate the response!

The real-world aircraft does have a difference in elevator deflection angles on each side of neutral (+16 degrees and -8 degrees off the top of my head), so it is expected behaviour to see the difference in movement range. However, from my discussions with our flight model developer, the difference in elevator deflection angle on either side of neutral is something MSFS doesn't handle all too well, so the small deflection angle is necessary in order to preserve the handling qualities of the aircraft. Essentially, even with that small deflection angle that you are seeing in the latest build, the aircraft should have a similar level of effectiveness as if it had the larger deflection angle. Hope that helps. Mark - Just Flight