@SadBucket I would assume it would come with POH supplements updating new limitations and new performance tables. That was easy to find.. https://taturbo.com/AFMS-550%20Rev%20J.pdf

Oh, I was going to send you a link to another thread where I explained how I fixed this, but I see that you were the one who started that thread. Yes, this is already done for all my aircraft, and will be included in the next update for the Dukes. Enjoy

This is an unfortunate issue with the Just Flight installer that has existed for a while. I know that they are investigating a fix, and I believe it's being tested right now with other products. In the meantime, there are workarounds posted on the Official MSFS Forums, or you can contact Just Flight support, who will send you a guide on exactly how to solve the problem. Sorry for the inconvenience!

@dave_pilot I find it very strange that you only see studders in blksqr, but not in more performance demanding aircraft like the fenix or 777... When I had performance issues I did this. You can try if you want: -Ran DDU and reinstalled an older confirmed stable driver from scratch since the latest Nvidia driver is pretty broken last I heard. Say Intentions Recommends 581.80 and that is what I'm on right now with no issues: https://www.nvidia.com/en-gb/geforce/drivers/results/257569/ *run DDU with internet disconnected to ensure windows doesn't install any compatibility drivers: https://www.guru3d.com/download/display-driver-uninstaller-download/ -Try turning off G-Sync under monitor technology in Nvidia Control Panel for MSFS2024 -Delete ROLLINGCACHE.CCC in %AppData%... \Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache -I also recommend running TAA instead of DLSS and turning on Dynamic Settings in MSFS graphics settings and in Online settings set Rolling Cache to 32GB.

Yesterday and today (2.1.2026) I had very aggressive pitch down in a reproducable setup on short final at ELLX runway 24. The airport is on an elevated plateu, together with the wind 25012KT this creates quite some turbulence when entering the plateu. However, with Starship this seems especially bad, causing a pitch down that I couldn't recover from (AP and handflying) at first, and finally managed to just barely catch with full elevator deflection when expecting it beforehand. I tried the approach with another aircraft and while it got violent turbulence as well, there was not nearly as much pitch down as with Starship. Speed is not the issue. With calm weather there is no issue. Is Starship especially vulnerable to this kind of turbulence? Should it be? I also had something similar happen at Rimini in the meantime, though it was higher up and gave me a chance to recover.

Hi Mark, thank you so much for the quick response. Something must have been changed with the parking brake, because in the past it definitely behaved as I described. The pedals were not depressed when the chocks were engaged and the parking brake was released. No indication of pressure at the gauges. The chocks could also be removed at any time. Thank you so much for looking into this! I also recently had another problem with the state saving – the file must have been corrupted for reasons unknown to me. The switches in the cockpit were randomly set and completely jumbled up. The clickspots in the EFB were ineffective (cold and dark, etc.). After reading through the forum, I found the file path and deleted it (StateSave.ini). Now this problem is resolved. Are there any other files I could try deleting? Perhaps that will solve the parking brake issue? (Previously, I had completely uninstalled and reinstalled the aircraft. However, the StateSave.ini file was not affected by this...) Greetings Volker

I've tried to bind a variety of ground operations using Axis and Ohs, across quite a few planes -- and I think the only thing I've ever bound successfully is toggle jetway, which works regardless of aircraft, but is a bit airport dependent.

The navigation logic used in the PA28 largely depends on what GPS is selected at the time. If the GPS100 is selected, the aircraft will be using our in-house autopilot/navigation code. If the Working Title GNS530, PMS50 GTN750, or TDS GTNXi is fitted, then the respective GPS autopilot/navigation code is used. There will be some differences in logic between each GPS as each GPS is developed by a different developer, and there will likely also be differences between MSFS 2020 and MSFS 2024 due to differences in framework between the GPS logic in both simulators (particularly with the Working Title GNS530 and PMS50 GTN750). However, with all of the GPSs, it should be the same steps to get the HSI displaying the GPS flight plan: Load a flight plan into the GPS (in MSFS 2024, this can be done manually or via the MSFS 2024 EFB) Press the CDI button on the GPS so that "GPS" mode is active (this should also be linked to the NAV/GPS switch on the console). If you wish to track a navaid with the GPS, press the CDI button again so that VLOC mode is active and then tune the VOR frequency into the VHF radios (remembering to flip the frequency from the standby to active field). Hope that helps. Mark - Just Flight

Thanks for reporting this. The ROLL mode should re-datum when the AP SYNC button is depressed, so I have logged this on our internal tracker as something to investigate ahead of the next update. Mark - Just Flight

You are correct. the jetway is connected!

Thanks for reporting. We have this logged on our internal bug tracker and it will be investigated ahead of a future update. In the meantime, airports can be added to FS Traffic manually via the "Adding a new airport" method listed on Pages 26-28 of the FS Traffic manual: https://downloads.justflight.com/products/JFF003616/FSTraffic_MSFS_manual.pdf Mark - Just Flight

Schedules can be regenerated by clicking the 'Edit' icon next to your airline's name at the top right corner of the dashboard (highlighted in the following screenshot) [image: c1ebf0d4-ae86-46d7-8e91-1117c28ac2f6.png] When you generate routes, any add-on airport will be displayed with a red pin on the map, and any default airport will be displayed with a white pin. Clicking on any of these pins will disable that airport, and prevent it from being included in the schedules. [image: 3efb7f52-5e6f-44d8-aec6-38f00279778a.png] Specific airport ICAO codes can also be excluded from the schedule generation via the Advanced Options page. [image: 1ee433e6-d0fc-403d-9a24-63b437e02968.png] Hope that helps. Mark - Just Flight

We would recommend following the steps in this FAQ: https://support.justflight.com/en/support/solutions/articles/17000149226-uns-1-how-to-disable-msfs-atc-integration Mark - Just Flight

It is logged on our internal feature request tracker, but it's not something we are currently working on. It is something we will be considering for future updates and/or upgrades to our PA-28 fleet. Mark - Just Flight

We released v1.5 last month which fixes this behaviour that was introduced with Sim Update 4. Changelog: https://support.justflight.com/support/solutions/articles/17000143705-rj-professional-msfs-changelog v1.5 is available to download from all retailers for PC (MSFS 2024). The in-game marketplace version for Xbox (MSFS 2024) is being processed and should be available in the next few weeks. Mark - Just Flight

in bush flying this is not possible i am always getting penalty's because sometimes their is not 1000 ft, in the entire runway

Hello! Any updates perhaps - either the manual that precedes the plane or maybe just a word on project that precedes the manual? Regards

Already discussed here

Thank you for your reply, I started to use the UNS-1 which is way more fun anyways, and the two units are fully independent.

Has this been fixed? I mean, I expect precision form a PROFESSIONAL titlted simulation which is in the price range of PMDG and the like which truly deliver precise, real-world matching performance. Why no one replied to the previous post, when a legitimate question was asked?