F28 Professional

@Voice-of-Reason thank you. I did wonder. The aircraft is otherwise excellent 2024. David

I think it must be the navdata for that particular airport. Possibly the third party addon messing with it. When I tried a different airport (KSRQ) it worked just fine. The SID from KATL also worked just fine in both flight plans.

At the moment, the F28 is MSFS 2024 compatible, which is built around an MSFS 2020 package that is made compatible with MSFS 2024. Therefore, it will still appear in the main menu with the MSFS 2020 style thumbnails and the "MSFS 2020" tag. An MSFS 2024 native update is currently in development, though, and shouldn't be too far away. The current status of all of our MSFS 2024 native updates can be found at the following link: https://www.justflight.com/articles/just-flight-addons-msfs-2024-compatibility-status Mark - Just Flight

As far as I'm aware, there is no logic in the F28 itself to vary the volume of the callouts. They should all play at similar volume levels as shown in the following video: https://youtu.be/_yf7IKD9zYk?si=QlhBYEg8OOC6eSX6&t=149 I've attached a screenshot of my Audio settings in MSFS 2024 (which I believe should be pretty close to the default settings). I would recommend trying a flight with those settings just to see if that fixes any audio issues. [image: be92467f-93e0-4f09-976e-ac8acaec9c71.png] Mark - Just Flight

I'd love to see this as well (similar to the ground air feedback supporting that recommendation I just posted). Would be a neat option to see implemented to offer some other variety with ground ops.

An old thread, I apologize, but I'd love to see this feature as well. Option for air starter and ground conditioned air; would love to simulate some alternatives to running the APU. Thanks for considering!

Just purchased the F28 and it is a great work. I agree that some level of failures would make this plane even more fantastic.

This is a known issue with v0.2.1. We do have a fix, and it will be included in the next update to the F28. Mark - Just Flight

This is most likely caused by GSX Seated Pax, and only in 24. I can't replicate this in 20. At least GSX Pax is the origin of that annoying ambient light for me. It also occurs in the Maddog MD-80 when GSX Pax is enabled.

The TCAS alerts are currently under investigation, and any fixes/improvements will be included in the upcoming updates to the F28 and RJ. Mark - Just Flight

This is something we have seen on our side too, and unfortunately, it's something that is being controlled by MSFS 2024 itself when the camera is moved a certain distance away from the textures. We have looked into a few workarounds, but haven't been able to find a suitable solution yet. We are continuing to monitor this, and we'll check it again once the upcoming sim update(s) release. Mark - Just Flight

The false TCAS alerts appear to be triggered by changing the simrate. Whenever I change the simrate to x2 or x4. the TCAS commence and the gauge indicator shows the conflict centered on the RJ. Reverting to x1 simrate (realtime) clears the TCAS warnings...

@MatzeH84 Here: https://alanmfernandess.github.io/f28/

@Mark D'oh. I was trying to click the UNS FMS and GNS 430 checkboxes and completely missed there being a 3rd, separate checkbox above. That worked. Thanks!

Any changes to the control assignment logic requires changes to be made in the core systems coding of the product, so unfortunately, there isn't anything that could be changed via a config file, etc. We do have an update in development for the F28 though, and our development team will investigate this ahead of the update's release. Mark - Just Flight