ups,fdx,dhl

thanks ill try that i already knocked a few out hard to weed thru

Agreed, same reason I only ever use the G530 and G430 combo.

ILS 17 in to Porto with both ND's showing critical nav data to the approach. [image: 61e7a1d6-5abc-42e3-94a5-5191e75c9201.jpg] [image: 802b7776-606b-4b27-a408-ab2643c98855.jpg]

Thank you, I will try to find the solution in the MSFS Forums.

Hello! I took advantage of the sale to get a hold of the program in anticipation of the custom route feature that will come out over the coming months. I have been playing around the program and have found the 16 aircraft limitation a problem for me too. I hope this will change in the next big update. Counting all the variants of the planes I have in my hangar, NOT counting long haul planes that are sometimes used for short haul: Airbus narrow body (4 variants) F28 (4 variants) Bae 146 (3 variants) Avro RJ (3 variants) Boeing 737 (4, including the MAX8) CRJ (4 variants) Boeing 727 (3 variants) MD-80 (3 variants) NAMC YS-11 Thats already about 30 planes and that's not counting the F70/100 that will come out eventually. I think you get the point. So, I think the best solution is having the ability to have unlimited aircraft profiles and not stick to a specific maximum. Changing the interface where the profiles are picked from buttons to a list box would make more sense.

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

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

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

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

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.

@SkipperMacz I actually stopped participating in betas back with 2020 because half the issues reported with them were never fixed before the SU was released in full. Sometimes I wonder what they're actually doing over there.

Amazing customer support and nick is cool as hell

The script from my last post I assigned to my switch position in AAO with "Assigned Buttons" and there via a key down event. For "MAN" I use the script: 2 (>L:var_surfaceDeiceSwitch, Number 1000 (>L:var_surfaceDeiceTimer, Number) 3 (>L:var_surfaceDeiceSwitch, Number) and I assigned it to the other position of my switch with another button assignment via key down event. For the centered off position I use the script 0·(>L:var_surfaceDeiceTimer,·Number) 1·(>L:var_surfaceDeiceSwitch,·Number) and I added two seperate button assignments via key up event to this script for the upper and the lower switch position.