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.

@SadBucket said in A36TC POH: @Buzz No worries, my reply may have come out more accusatory than I meant... Just trying to help too. *Also, as far as I am aware, FAA does not require an engine or induction-system STC to provide any replacement of the manufacturer’s performance section so long as performance is not degraded... Maybe someone has done it, but it is not required to be in the POH. The STC only has to provide compliance with engine limitations and safe operating procedures in the AFMS. Please correct me if I misinterpreted this... The FAA DRS is your friend. Item 8. Apparently this STC requires the included supplement to be in the AFM/POH. https://drs.faa.gov/browse/excelExternalWindow/DRSDOCID128380987620240925140721.0001

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

@SadBucket yup that's what i find very strange too. that's why i thought it might be some aircraft related bug... i did 3 flights yesterday with the fenix a320, even with 100% sai intentions traffic and like always butter smooth. no problems whatsoever. i then thought maybe it's because i have TOO many fps in the tbm, but when using "cheap" vanilla stuff it does not happen either. and limiting frames didn't help as i already said. so the problem is also not a high fps count. i don't want to mess with any driver stuff right now, because as i said, i don't want to risk that other things might break, because in general i am very happy with the sim and its performance and i don't want to introduce problems to something that works well right now. and i also don't want to sacrifice DLSS for 1 plane tbh. yes, i already tried deleting the rolling cache file. and created a new one. i always had a rolling cache of 64GB. problem still persists in the tbm and i disabled gsync in general because i don't like it. at this point i think it might be just my exact system configuration reacting allergic to black square aircraft. lol because i can't explain why it happens and as it seems no one else can. i don't even run anti virus software, only windows defender so i am basically clueless at this point... i also don't run other software in the background. no browser, no background tasks, no steam, no iCue, nothing. just msfs. for now i just give up and fly other stuff until the next sim update and then try again. maybe this will change something in the background which resolves this. it's a pitty because i would love to fly the tbm, but at this point as it seems to be my only option.

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

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

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