MSFS Products

I am now routinely checking this and can unfortunately confirm that this is always the case. The FMS is simply unable to calculate accurately. It regularly estimates the aircraft to reach the T/D - which is often 80-110 nautical mile before the destination - only 1-2 minutes before reaching the destination. Obviosuly, the closer you get the more realistic the estimation will gradually become, but this is not how the real FMS works. PMDG, Leonardo, Fenix programmed their systems to do very accurate calculations. I hope Justflight will refine this aspect, it is certainly more important from the pilot's perspective than to be able to play nice boarding music. [image: e63b4a94-7da8-4b50-826a-4581304e895e.jpg]

For what it’s worth, FlySimWare recently escalated the state saving bug to Asobo too. There’s definitely something broken with it after SU4 which Asobo has to fix. FSW implemented a temporary workaround for the Learjet but they use WASM. They mentioned another workaround (before their custom fix was implemented) is to end your flight, start a new flight, then exit the game once loaded in and that may cause things to save correctly. That trick may work for the Baron/Bonanza too but I haven’t had a chance to try it.

Just updated to a version 1.5. Uninstalled previous one, restarted the PC. Runs just fine. Hmm you may have some other stuff conflicting...? Not sure.

I've just checked this on my side, and the following control assignments can be used to control the CLIMB/DIVE switch on the throttle quadrant: INCREASE AP PITCH HOLD REFERENCE DECREASE AP PITCH HOLD REFERENCE Note, those will only control the aircraft's pitch when the autopilot is engaged, and no other vertical modes are engaged. Hope that helps. Mark - Just Flight

Thanks for the feedback. I'm glad to hear that you're enjoying the F28. Whilst we don't have any firm plans for futher upgrades at the moment, I'll be sure to log this so that our sound artist can see what's possible.

said in 146 Professional MSFS 2024?: @Mark Does this also apply to the X version, or is it only for the PC marketplace? Thx

I've noticed the same problem and sort of know why it happens. First flight works fine and shows traffic. But If I do another flight at another location there is never ever any aircraft. What I do is shut down the PC and restart and traffic is there. So to me the problem is if I do a second flight at another location - No Traffic-

Chill, bro There is a general bug in MSFS: Button trim speed depends on FPS for all planes. Measure trim time (0-100% on the HUD), then enable frame limiter and measure again! It's different, reverse proportiknal with fps. This is true FOR ALL Planes! This is dumb, it should depend on the time duration the button was pressed, independent of FPS! So maybe the only way for the JustFlight guys to make a usable trim button was to make the trim very sensitive, so it can be trimmed in a reasonable time. As a side effect the tailplane position indicator cannot be used to check trim state, we need to enable "hud in cocplkpit" and then you can checkthe 0% trim before takeoff. And God forbid, use an axis contrlol for pitch trim like the saitel trim.whreel. move 1 percent (few mm) and it's at full trim. Move 10% plane stalls/spins/disintegrates!

thanks Martyn for letting us know, I appreciate the teams care on this planes. Have further great days to get save into 2026. Dierk Kaller

Hello JustFlight, I'm really interested in the Arrow III, but for nostalgia's sake. Since the GPS 100 isn't really functional and the MSFS 2024 version have been released awhile back, I'm wondering if you are still considering this request. Would be nice to have a classic GPS unit in a classic aircraft.