Thanks for mini-FCU profile!!!! I'm. Unfortunately stuck at work at the moment, but hopefully there's a decent Starship turnout for the FSExpo VATSIM activities tonight!

Hey again For what it's worth, there's another typo in the RTU events: Rtu_TransponderStandbyButton_L should be Rtu_TransponderStandbyButton_1

Without knowing which exact annunciator has lit and under what circumstances lead up to it illuminating, it's a tricky one for us to confidently answer. The ANTI SKID FAULT annunciator will light if there is a fault within the system. The ANTI-SKID INOP annunciator will illuminate when the system is inoperative. With the latter, I believe it would only illuminate if the ANTI-SKID switch is set to OFF, or if the system does not have electrical power (Anti-Skid is supplied by DC Bus 2). If that behaviour occurs again, could I kindly ask you to raise a ticket with Just Flight Support via the following link: https://www.justflight.com/support If you could attach some screenshots or videos of the behaviour with the ticket, then our support team will be in the best position to investigate this further and assist with further troubleshooting. Mark - Just Flight

The real-world aircraft does have a difference in elevator deflection angles on each side of neutral (+16 degrees and -8 degrees off the top of my head), so it is expected behaviour to see the difference in movement range. However, from my discussions with our flight model developer, the difference in elevator deflection angle on either side of neutral is something MSFS doesn't handle all too well, so the small deflection angle is necessary in order to preserve the handling qualities of the aircraft. Essentially, even with that small deflection angle that you are seeing in the latest build, the aircraft should have a similar level of effectiveness as if it had the larger deflection angle. Hope that helps. Mark - Just Flight

The FS Traffic fleet is all set up with the correct airline ICAO/IATA codes in their config files, so that if airline codes have been assigned to specific gates at airports by the scenery developer, the aircraft will generate at the same gates as they would in the real world. The main limitations of this are that it does require airline codes to be assigned to gates by the scenery developer, and they must also be set up correctly. Typically, they are set up correctly on payware third-party airports, but the default, auto-generated MSFS airports likely won't have airline codes set up, so the aircraft will generate wherever there is a free gate/parking position that can accommodate that aircraft type. Hope that helps. Mark - Just Flight

It’s a fair point. Initially, at least bringing the Flighsim own EFB into the tablet would be appreciated.

Do you have any other details, which could help identifying the issue

Nick has already integrated it in the Dukes (my "weapon of choice" ever since its inclusion), so he is certainly aware of the unit. The KLN-90B is technically only certifiable for RNAV2 at most, and other than DME arcs, it also doesn't do any of the fancier leg types AFAIK. There is an option to not filter out RNAV1 procedures, but otherwise the capabilities will not really be beyond the build in avionics I would think. So while I always love to see the KLN90B in more planes I don't think it should be a high priority thing at least.

I just watched a video on this exact topic. link text

The MSFS version of the 146 Professional does list some 'non-standard' control assignments at the very end of the Operations Manual. The X-Plane versions of the 146 Professional do not list control assignments in the Operations Manual, however, I believe most control assignments in X-Plane are quite well named for their purpose. Please don't hesitate to reach out if there are any specific control assignments that you would like to know. Mark - Just Flight

v1.0.8 is an MSFS 2024 only update, primarily focused on bringing MSFS 2024 compatibility to FS Traffic. However, there is an update in development for MSFS 2020, which will bring across some of the bug fixes and improvements that are included with v1.0.8. Mark - Just Flight

Then turn off the traffic injection from the FS Traffic injector! Open the Control Centre. Go into options and disable FS Traffic.

We don't list the TDS GTNXi as compatible with the PA-28R Turbo Arrow III/IV (X-Plane 12), so I suspect there won't be any required code in the Turbo Arrow to make the GPS functional. We will, however, log this on our internal feature requests tracker as something to potentially look into adding support for in a future update. Mark - Just Flight

Thanks for the feedback. Although it might be nearly invisible to the user, so much has changed in the effort to eliminate that bug. Please let me know what you think of this new version!

We're aiming to finish work on the 146 upgrade and MSFS 2024 compatibility in July.

The Traffic Control Centre executable for MSFS 2020 (named trafficControlCentre.exe) can be found within the MSFS 2020 Community folder at the following file directory: ...\Community\justflight-fstraffic-controlcentre\Data\trafficControlCentre The Traffic Control Centre executable for MSFS 2024 (named trafficControlCentre2024.exe) can be found within the MSFS 2024 Community folder at the following file directory: ...\Community\justflight-fstraffic-controlcentre\Data\trafficControlCentre Hope that helps. Mark - Just Flight

If you mean physically on your computer, unfortunately, Asobo does not allow file write access from JavaScript instruments.

See here.

Seems like it.

Glad you're enjoying it. This was a very purposeful design choice on my behalf. Calling some of today's pilot's "children of the magenta line" has become such a common utterance around the airfield that it occurred to me that I might be foolish to create a map display without the proverbial magenta line. Hopefully you can understand that I probably would have received far more complaints about not knowing which leg is active, than your single well researched critique. This was originally due to a simulator limitation, but I thought of an elegant way to synchronized them recently that I will try. (the issue is that I don't want there to be a visible delay between the two if they have to synchronize after becoming out of sync for whatever reason.) Fixed. I actually already had the rounding in there, but forgot to put in the divisor. Thanks again, and always feel free to send me anything else I missed!