Mike S KPDX

FSLTL does not recommend using Aiflow with their product according to their Discord site.

MSFS, please for the love of all, do NOT do windscreen wiper effects as shown in the race sim example provided - that is just horrible.

I have been using P2ATC for 8 years, never once have I used voice recognition - the program works beautifully and is not mandatory in the least. I felt I needed to correct this for the other readers on this thread.

I always find these types of posts fascinating. I have tried to move programs in my up to date win10 system but have never seen this 'move' command. As described above, I go to APPS AND FEATURES, scroll down, find the program, left click - and the only option boxes displayed are MODIFY and UNINSTALL. However, event the modify box is greyed out. This is true for every app in the list. I have full admin rights to everything too. I have simply never got this 'feature' to work or even display as I suspect it only works in 'apps' (vs programs) installed via the MS Store. I do envy those that have that ability.

in the US you will almost always fall under vectoring control, in other words - many of our procedures are 'disconnected'. Still blows me away that Chicago O'Hare has no SIDS's - simply crazy.

40 would be a dream for me, usually around 12-15

Are you speaking about the airflow arrows around the aircraft when viewed from the exterior? That would be part of the analysis that is toggled on in the Developer Mode menu system.

this is what I found... Re: Difference between FSDT Live Update and Update via FSDT Installer ? « Reply #1 on: October 12, 2023, 12:01:11 pm » Quote They are exactly the same program (same .EXE), just with a different user interface that changes depending on the icon you start it with. However, what the Live Update does, is the same as if you pressed the "Update All" button in the Installer interface, and this function does some extra cleaning of wrong settings in your system, which might explain why you see a difference that, under normal situations shouldn't be there. Some of these settings are related to clearing some registry settings by wrong compatibility flags Windows might have set to "help" you starting a program that might not have started, or crashed, for any reason, which we reset back to default, fixing the issue.

found this on their forum, may or may not help. Also keep in mind that they also have a very active Discord channel. This was in fact a problem we never considered: if you change your callsign in the airplane customization page, it will change the ATC ID reported by Simconnect for all your airplanes, until you change it again. Since the ATC ID is tied to the PMDG .INI settings for that airframe, if they don't match, it would cause GSX not being able to read the airplane configuration for that variant.As soon this was reported, we posted a small hotfix (no version change), which reads the ATC ID from the airplane.cfg first, reverting to Simconnect only as a backup in case the atc_id might be missing or the aircraft.cfg couldn't be read for any reason, and this should fix the problem, regardless if you changed the callsign or not.The fix is already online since a couple of day, just run the FSDT Live Update and make a "Check" on GSX Pro.

At no point are any of the items listed in the original post controlled by FSLTL. Please read their FAQ. You are complaining about the base sim and/or modified airports poor ground pathing.

The title of this thread is a given. In what possible way would this be 'unexpected'?

Ok ok, just saw this thread popup again and saw my post on it (above). It was only a few weeks after this that indeed KMSP not only released but is very well done. For this statement, I have to apologize and 'eat crow' as they say. However, I will stick hard to statements I have made about the Majestic Q400, that will not see the light of day for at least two years and will be made for MS 2020 and released midway through the lifecycle of MS2024. Anyways, just had to chime in and say I was wrong 🙂

Sounds good, I will keep my eye out for a video that actually shows the unit working with the Fenix product, as this video only shows a software install. Thanks for the heads up.

I quickly scanned the video as I assumed that this addressed the lack of the display digits in the mini unit, yet it seems it does not. I understand that this is issue is unique to the Fenix product. Did I miss something?

Curious, what bugs? I was under the impression that the last patch .05 addressed all known issues. What 'bugs' are you seeing?