F28 Professional

Am I the only one who has this problem? If the pilot has to be fixed, could it be in the forward position, please? It is a bit strange to have a copilot having the seat moved backwards during flight.

There's been no intentional changes on our side with regards to the APU logic in the recent F28 Professional updates.

It'll be worth double checking that you have the GEN 3 and APU AIR switches both set to OFF before starting the APU (the latter will prevent the APU starter from triggering if left in the ON position). Note that the APU MAIN switch should also be left in the ON position for 10 seconds before pressing the START button, as that allows the APU intake door to open.

Hope that helps.

Mark - Just Flight

OK, thank you for your answer, I’ll pass it on that they should work, at least for a finite period of time as I may not be porting them over.
Much will depend on whether the Fokker F70/100 will be fitted with a WXR layer in the ND…

That's great! Thank you!

I contacted Navigraph and they said " their nav data has these airports" and that it's an issue with the add-on, which in this case is the UNS-1 in the F28. They included limited technical information to back up their story. Something to do with the UNS-1 not reading data due to a file size issue. Basically the navigraph guy was saying, talk to Justflight.

Thank you,

I will check if they have a trial version, looks promising if it works!

Many thanks !

In addition to ensuring that you're tuned into a VORDME (not just a VOR), there are also two switches on the VHF NAV panel that control the respective DME transmitter/receiver. These must be set to DME in order to receive a DME frequency.

Screenshot (476).jpg

Also, if the GNS430 GPS or UNS-1 FMS are fitted the DME readout on the HSI will indicate the distance to the active waypoint instead of the distance to the VHF NAV 1 navaid. If the GNS430 is fitted, toggling the CDI button from GPS>VLOC will allow for the distance to the VHF NAV 1 navaid to display, and if the UNS-1 is fitted toggling the NAV/GPS selector from GPS>NAV will have the same effect.

Hope that helps.

Mark - Just Flight

Yes, there's been no change to the Nav lights on our end in v0.2.1 apart from slightly reducing the Nav light intensity in MSFS 2024.

The Nav lights popping in/out of view is a behavior we see in all of our aircraft in MSFS 2024, and we believe is something being forced by the core simulator. We'll take another look once the F28 gets its native MSFS 2024 update in the near future.

Mark - Just Flight

I had this issue too. After reading this thread, I updated my TDS750 and it solved my Course/NAV 1 issue.

I tested this earlier today to get a screenshot, because I thought I had seen it before. I loaded into a remote clearing in northern Norway, time set to about midnight, cold & dark. I hid the EFB and looked around the cockpit with cabin lights off. I tried with the cabin door both open and closed. To my surprise, there was no light whatsoever, other than a couple pin-pricks of stars that didn't cast any light into the cockpit. No light around the door, no light in the cabin, no light in the cockpit. The only kind of odd thing is that all the gauges appeared kind of frosted while the rest of the cockpit was super dark.

I don't mind working ported versions. I'm not really the biggest fan of the preflight walk arounds.

You can't delete the registration in the settings but what I have done is just put a single space there instead and then the correct reg is then used in the cockpit.

So a space in Tail Number. I also do same in Flight Number.

image.png

@Aymerix Yes, that should be the correct file directory for the MSFS 2024 Steam version. I have updated my previous comment to reflect that, and the following FAQ will also have the correct file directories listed: https://support.justflight.com/en/support/solutions/articles/17000145452-uns-1-how-can-i-import-a-flight-plan-from-simbrief-

Apologies for the inconvenience.

Mark - Just Flight

@Mark said in Weather radar intermittent INOP:

Unfortunately, it's proven to be a tricky bug to track down and find reliable steps to reproduce.

I'll see if I can find a pattern. Thanks for replying!