So my issues I have with the latest update is:
- Pilot missing in external view
- Aircraft tagged 2020 in the selection menu. Not sure if that makes a difference?
Just tried the Arrow III and turbo Arrow, running MSFS 2024 only (On PC) and on SU2 Beta.
Hadn’t installed the Arrows at all since installing 2024 and got them from the JustFlight store not in the marketplace.
Both planes I got Yoke full to left and no instruments or EFB working. Also no copilot showing and it is selected on the EFB.
Works OK with the alternative panel.cfg file so far for instruments, yoke and efb but no Pilot or copilot visible.
1 Like
My background info:
- MSFS 2024 SU2beta
- Had the na and turbo Arrows installed (directly from Just Flight) previously in 2020, copied over into 2024, then uninstalled when I learned that a new version was incoming
When installing the new version, I had the same issues as some others here - yoked full left,etc.
Happy to report that the updated panel.cfg linked to above fixed the issues for me in the turbo Arrow.
However, it looks like when using Navigraph charts or the map in the EFB, it will constantly blank out for half a second, then return. I left it alone for some time and the problem never went away. Almost like it’s constantly trying to reload and refesh?
Have you ever owned the Marketplace version? You shouldn’t be seeing the MSFS 2020 tag in the aircraft menu.
Martyn - Just Flight
All three PA-28’s don’t have the MSFS 2020 tag for me. Are you certain you ran the correct installer?
We’re working on a fix for the EFB map issue which occurs on all our MSFS 2024 aircraft at the moment due to a current sim limitation. We’re hoping to have a fix within the next week.
Martyn - Just Flight
4 Likes
Nope, never did.
Quick test with the Arrow III in FS2024. Everything seems to work fine, except the aircraft started rolling as soon as I clicked “Ready to fly”. This bird seems to load in with the parking brakes off. Only when I entered the aircraft it stopped rolling (and loaded a saved state).
Looking forward to the first flight in this new old bird tomorrow. 
1 Like
Yup, correct installer…the manifest is correct too…
Hi all,
The updated installers are now live (installer filenames end in ‘a’).
It looks like the interactive paper checklist issue might have been caused by the use of a custom tail number in the aircraft menu (identification tab), which is why only some users were affected, but we’ve disabled that feature until we’ve fixed it. That should happen on Monday.
Worked OK
WASM failed
Thanks for your patience,
Martyn - Just Flight
12 Likes
In the Arrow and the Turbo Arrows, the PMS GTN option is not available in the EFB. It does show up in the Warrior.
EDIT: This is in MSFS 2020.
Sadly I’m on Xbox, so have to wait a bit longer to get my Pipers back (cue violins).
But boy, you couldn’t ask for much better service than that shown from JF on here today!
7 Likes
Still no luck with TDS GTNXi with latest update (0.11a). Still blanks out after a few minutes.
The updated installers are aimed solely at addressing the WASM gauge issue caused by the paper checklist.
We’ve yet to reproduce the issue that you’ve reported with the GTN but are investigating.
Martyn - Just Flight
All good now, the panel.cfg swap worked! And yes, I had a custom tailnumber in the sim.
1 Like
Understood - thanks!
1 Like
All working correct with type ‘a’ installer.
Thanks for the fantastic effort in fixing this guys!
1 Like
However, my 1 gig internet is downloading the 6a versions at 5 Kb/sec – right KB’S! Measured in days to complete. What’s up with the server?
So, none of my GPS products are working in the latest bundle for FS24. I’ve downloaded the (a) EXE and installed into FS24 community folder. I am in Beta 1.4.18 and although the aircraft works well, none of the GPS configs work except for the GPS100. I have the GTN 750 payware and it’s not working (in the P28) either. The lights for the buttons are working but the screen(s) are blank. Is this a bug for many or am I the oddity? Oh ya, none of the EFB maps are working either (Navigraph or default).
Does this also happen when starting on the runway? Do you have the radio lights switch set to full brightness?