F28 Professional

For feedback such as this, we kindly ask you to raise a ticket with Just Flight support via the following link: https://www.justflight.com/support

Included with the ticket, if you could provide a video of the behaviour and/or steps on how to reproduce it, then that will allow us to look into this and log it as a bug if required.

Mark - Just Flight

We are aware of several map-related issues in MSFS 2024. These are currently under investigation.

Mark - Just Flight

Thanks for the suggestion. We have logged this on our internal feature request tracker for our development team to consider for a future update.

The current TCAS VSI / Analog radio transponder configuration is however accurate to our reference aircraft.

Mark - Just Flight

Replying to my own message in case this helps anyone! I had previously cocked up the checklist procedures so had hit the "cold and dark" option in the EFB but it appears that this doesn't reset the aircraft back to "defaults". The only thing that worked was restarting my flight in the simulator pause menu and everything worked correctly after that. Not sure if I'm not understanding the purpose of "cold and dark" or if this is a bug but I'm tempted to go with the former rather than the latter!

@GroverJ41 That's sorted it!

You need the parking brake off AND the chocks (which, in MSFS, is a duplicate of the parking brake).

I'll check things out on my next flight to see what you need to do in the air to get it to work.

Found e solution.... was a local mod on my Community folder.. Delete it now all fine!

That likes more like a flightpath being displayed from some in-sim settings ..

I think your suggestion resolved the issue. I have checked all electrical systems, waited a while, and the UNS powered. I'm not really clear on what made the difference, but the system is running. Thank you for your response.

Mark reinstall worked. I did take part in the MSFS survey and requested the old aircraft selection from MSFS 2020 that works so well, for the new sim. Thanks again Bob.

This isn't something we have reported with the F28 in MSFS 2024, however, I have found the following thread on the official MSFS forums from users having the same issue with MSFS 2024 in general: https://forums.flightsimulator.com/t/msfs2024-stuck-loading-57-since-patch-v1-1-10-0/680172/105?u=cajolingrain44

Looking at the comment from "Roadswwper1" it would suggest that there may be some sort of aircraft limit that exists in MSFS 2024, and adding the F28 may have just tipped you over that limit. Therefore, it may be worth trying to load the simulator with a Community folder with a few less aircraft to see if that solves the issue.

An easy way to test this will be to rename your Community folder to something like "Community.old", create a new community folder with just the F28 and maybe a few other products/mods installed, and then launch the simulator to test it. If the simulator loads with fewer products/mods in your Community folder, then that may point to the aircraft limit mentioned above.

Hope that helps.

Mark - Just Flight

Thanks for reporting this. This is something we have contacted Navigraph about several times since the RJ Professional release and unfortunately, we are still awaiting a response. I will check back with our team early next week to see if we received a response to our most recent message.

In the meantime, we would recommend reverting back to the default 2401 navdata that is included with the F28 Professional. This can be done by running the F28 Professional installer and selecting the "Repair" option.

Mark - Just Flight

I think it's also in the docs folder after installing to community. I couldn't find the UNS-1 online but I am probably blind :-)

Thanks for the tip. Everything is perfectly described. If you know what to look for😄🤷. Really successful airplane.

@Mark thanks Mark!

2020 UserCfg
}
}
InstalledPackagesPath "C:\Users\rbrin\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages"

2024 UserCfg
}
}
InstalledPackagesPath "C:\Users\rbrin\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages"

2020 Install works fine, 2024 not so well...

Yes I do use V2 (The one I tested was with the UNS-1)

I had to go into each variants Simobjects folder and change code = (L:EXT_Door_pax_2L, number) to code = (L:EXT_Door_pax_1R, number)

This is for MSFS2024

I wanna say Thank you, for this Update! It's a plesure to fly! Both, the F28 or the Bae!

Lighting in the F28 can be a bit like playing Twister! I'm sure it made total sense to some engineer who originally put the Dome and Storm light switches on the exterior lighting panel 😅

Mark - Just Flight

The file directories listed in the UNS-1 manual are intentionally pointing to the 146 file directories. The UNS-1 manual is intended to be a generic manual that can be used across multiple aircraft. The 146 file directories are used as examples, but the file directories will be the same structure for the 146 and F28, just with the "146" and "F28" names swapped out.

Mark - Just Flight

Believe it or not, I just had this same thing happen in the RJ, and it was something very simple. So even though there are a couple other reports of this on the forum now, I have to ask: was your speed brake extended? I had apparently bumped my speed brake lever at some point, and I didn't realize it until I noticed pitch oscillations at cruise of approximately +/- 500fpm, just like yours in the video. Retracted the speed brake, the problem went away.