MSFS Products

Pssst... I can sneak you the money under the table and don't mind to fix this myself or ignore it complety because I will surely use your KLN-90B or no GPS at all, because I love your KNS-81 implementation.
I mean... the are so many avionics options, you could put a warning on the description that this is only working after SU15. 👉👈🥺

I am having major issues with the Arrow AP. I don't want its altitude hold feature active, I want to control the trim myself. I don't know if it's my logitech AP unit or what but the plane never seems to want to stop holding altitude. Because there is no switch just a clickspot, I can't tell whether altitude hold is supposed to be on or off, and my bindings for altitude and heading hold seem to do nothing in this plane. I'd like an option in the ipad to disable the clickspot and all the altitude features of the Arrows so they NEVER take control of trim, and the AP works as it would in real life, please. And ideally I'd like the "Heading Hold On" and "Heading Hold Off" bindings to work so I can use my switches instead of the mouse.

I think it might be my logitech AP unit interfering, so I will test with it unplugged, but it seems pot luck whether I can get the AP in the Arrow to release control of trim.

@Mark Thanks for your reply. From that I gleaned that the AP disconnect is not a feature of the aircraft so perhaps something might be wrong on my end.

I did a long testflight during which I unplugged my yoke and throttle quadrant and that seemed to cure the AP disconnect. After reconnecting the AP disconnected again after a while.

I checked the yoke sensivity setting in MSFS and noticed there was a "reactivity" setting I have never touched before. It showed 100 so I changed that to 98, on a hunch that this might filter out these spikes.

I did a long test flight with this setting and did not have a AP disconnect. The funny thing is, when I set it back to 100 I also did not have these AP disconnects anymore.

When I later checked for spikes using VKB Joytester I noticed that the yoke was indeed sending spikes once in a while, very short bursts but off the scale.
These did not lead to AP disconnects since I already touched the reactivity setting in MSFS.

Even after a very, very long flight the AP disconnect did not return except once when I changed GPS instruments on the tablet during a flight.

Perhaps the original value of the reactivity setting was not set properly in MSFS internally so setting it to 98 and then back to 100 reset something in MSFS.
Sorry for the long reply but hopefully someone else with a similar issue might benefit from this.

@trevor250

See this page - there is an email link to submit queries if you have bought products from elsewhere:

https://www.justflight.com/support

@jaspar11 I have just tested this and I am seeing the tail plan position indicator move between +5 and -3 by triggering the elevator trim assignments, so that sounds like there may be some other controller conflict that may be preventing the trim from working correctly for you.

If you could kindly contact Just Flight support via the following link, they will be able to run through some troubleshooting steps with you to get you up and running: https://www.justflight.com/support

Mark - Just Flight

I'm wondering if the autopilot glideslope following is going to be addressed. It is awful. It used to be fine, but something is very very wrong with it now. In my case, the AP captures it ok at first, but despite being fully configured and at Vref+5, the plane just won't follow the dot and it (the dot, not the plane) just keeps going further and further below the middle spot and the plane makes one or two ineffective tries to follow it down , but it just gets further behind, resulting in being too high as you get near to the threshold. Multiple posters have agreed on at least two different threads about this. All my other payware planes do just fine.
It is getting to the point where I just don't want to even fly this plane, which stinks, because it is by far my favorite plane for MSFS.

@TrailerSwift89 These codes are three-character IATA aircraft type codes as opposed to the four-character ICAO aircraft type codes that you have referenced. FS Traffic uses IATA codes as that is what is used in the databases.

Mark - Just Flight

I'm using the files Just Flight supplied for the GSX aircraft profiles. For some reason GSX does not detect that catering door is open to begin the catering animation. Is there some different variable that be used? This is what's included in the GSX profile provided by Just Flight:

[service1]
pos = 1.53 7.13 0.26 -1.50
code = (L:EXT_Door_pax_2L, bool)
name = FWD SERV
embeddedStair = 0

@NickW61 Thanks for letting us know. We've passed this info on to our support team so that they can quickly point users in the right direction if they run into this issue.

Mark - Just Flight

I can by clicking on it, I meant mapping it to a control. Do you have it mapped? and not with 3rd party software. I guess I should have been more specific, sorry.