F28 Professional

@JetNoise said in PILOT CALLOUTS Not available: @YISEN https://community.justflight.com/post/34921 Has been covered already.... Pls make use of the forum search ... OK,thank you

Happened again today, but this time I noticed that the APU main swith was in the ON position when landing. I must have forgotten to turn it off after starting the engines. (You are supposed to let the APU wind completely down before turning it off, so I tend to finish the before taxi flow first, making it easy to forget). I got the APU to start while taxiing in by turning the APU master off and waiting a bit, then trying again.

thank you for your response. i will try that and report back.

I ran into a similar problem today where I lost both engines. I couldn't figure out how to restart them with no bleed air. The procedures in the manual only work for one engine outage but not two. There is only one reference to a "windmilling option" in the manual, but it doesn't have many details and keeping above 200 knots does not provide any bleed air pressure. It does not seem possible to relight both engines mid air in this version. [image: e5cddaa8-f621-4627-b945-8c84b1685379.png]

On the Audio Selector Panel, the square buttons along the top of the panel are transmit buttons for the respective radios, and the circular buttons are receive buttons. Whilst looking into this, I have just spotted a potential bug in that logic though, which I've logged on our internal bug tracker. We'll get that investigated ahead of the next update. Mark - Just Flight

The "RUDDER STEERING AXIS" option on the EFB is used to toggle which controller axis are used for the nose wheel steering. With the option enabled the nose wheel steering will be linked to the RUDDER AXIS (the standard control method for most aircraft in flight sims). With the option disabled, the nose wheel steering is unlinked from the RUDDER AXIS and can be controlled independently using the NOSE WHEEL STEERING AXIS (a more accurate method that is used by the real aircraft). The blinking on the EFB is intentional as that indicates that the fields can be edited (usually when the engines are shutdown, and parking brakes or chocks are in place). Further info on all the EFB options and Boarding Simulation can be found in the F28 Professional EFB Manual: https://downloads.justflight.com/products/JFF003039/F28_Professional_MSFS_EFB_v2.pdf Mark - Just Flight

Thanks Mark, I just performed a Nav data update, to April 2025, from Navigraph, as per your instructions. Now my F28 has YSSY & YPPH and I assume other airports which were not available before.

You have to get it! It´s worth every penny Work great with the F28...

Great, Mark. Thanks so much.

Naturally, after posting it shows up. Nothing to see here. Please disperse.

After trying to figure this out for a little while, I found that the problem is that the flight plan is exporting to a PLN format and not RTE. In order to generate RTE I have to download the plan as a Just Flight 146 plan or in simbrief downloader select the Just Flight 146 and set a second export director to the ."..F28\work\FlightPlans" folder in order to get the RTE format.

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.

That's great! Thank you!

Many thanks !

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: 2a7df14f-9931-4beb-9de4-f830c08828c3.png]

@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!