Disable Altitude Hold
-
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.
-
I would have thought JustFlight would have addressed this by now. I too have had this issue.
JustFlight wrecked their perfectly acceptable Piper Autocontrol roll control unit by adding a cheap, and unnecessary, implementation of vertical speed and altitude hold. I can no longer enable heading control without altitude control being switched on too. No way to separate the two.
This used to be an excellent representation of the Arrow which is now marred by this dog's dinner of an autopilot. Can I ask you to implement an option on the EFB to revert it back to the original heading only control mechanism?
In my VA we planned to use the Arrow on a SEIR course. We planned limited use of heading control when flying IMC in order that the student was eased into procedural turns, holds, etc. using VORs and NDBs. Now, this option is no longer available.
Please give us a way of disabling this dreadful AP implementation.
I am more than happy to raise a ticket but I must first ask if you have any intention of resolving this issue?
Respectfully
Rick
-
@Tensim The altitude hold click spot you refer to has been implemented in the Arrow since its original release in 2021, and therefore, we can confidently say that its implementation has not affected the autopilot behaviour in any way. The hidden vertical speed click spot was added in a post-release update based on feedback we received from the community and uses a similar logic to the altitude hold click spot. These clickspots use very basic logic and simply trigger the default MSFS autopilot modes when clicked, so any issues experienced with these features are likely related to controller conflicts with one of the default MSFS autopilot modes being triggered by external hardware.
One thing that has changed significantly since the Arrow's original release is the updates to the GPS units. Each of the GPS units that can be selected in the Arrow has received significant updates by their respective developers since the Arrow's original release, and in some cases, this has resulted in effectively entirely new GPS units with enhanced simulation. Each of these GPS units does attempt to overrule the Arrow autopilot code with their own custom autopilot code which can cause autopilot quirks depending on which GPS is selected.
If you would like to experience the Arrow with our autopilot code, please select the NO GPS option on the EFB, otherwise, the autopilot will be controlled by a mixture of our code and the selected GPSs code.
As Derek has said above, if you are having any issues please open a support ticket with Just Flight support we will be able to assist with troubleshooting this further: https://www.justflight.com/support
Mark - Just Flight
-
This post is deleted!
