Heading/altitude hold don't work even with AFCS in BOTH
I have version 1.1.1 from Orbx. I'm just looking for heading/altitude hold, not a true autopilot. I set up Spad to turn the Chinook AFCS to "both" and press the correct heading hold/ baro altitude hold buttons and you can see them move in the cockpit, but the two buttons move and don't light up. Not sure AP is ready for prime time yet. Just updated it via Orbx the other day.
Pretty much the same result using the msfs control bindings. Heading "seems" to hold but not altitude.
**Function -----------------------------------MSFS Axis Bindings**
Toggle AFCS Mode HDG HOLD* ------------TOGGLE AUTOPILOT HEADING HOLD
Toggle AFCS Mode BARO ALT HOLD* ---TOGGLE AUTOPILOT ALTITUDE HOLD
Toggle AFCS Mode RAD ALT HOLD*------ TOGGLE AUTOPILOT RADIO ALTITUDE HOLD
*Beware that AFCS Mode will not engage unless the AFCS System Selector is correctly configured
System must be ON in the 1/2/Both position)
Miltech Simulations @MiltechSimulationsCan you please try the AP without using SPAD and confirm if it works fine for you?
The Heading/Alt hold and their corresponding buttons very much work just fine on 1.1.1. With the system selector knob on BOTH, you should be able to engage the systems and the corresponding lights will light up, indicating mode is engaged.
If this is something you are unable to replicate, it may be the case that SPAD is not correctly setup. That's beyond what I'm able to assist you with.
- B@Burnhaven
Tried it without Spad today
I keep experimenting with the autopilot. Right now I turn the AFCS to Both with the mouse, toggle the heading hold on and also the radar altitmeter hold on with a single key binding and set cyclic trim on manual. It hunts around briefly and settles about 5 degrees off from where the heading bug is set, then hunts more before settling on an altitude. Useful for a brief period to check maps or post a screenshot, but maybe not much more.
Miltech Simulations @MiltechSimulations-
Make sure you have sufficient deadzone on your cyclic and pedal axis. Otherwise the AP may conflict with inputs from both, and result in inaccurate heading tracking. It should consistently work and follow the selected heading.
-
Make sure to move your collective hardware axis to idle/minimums. Otherwise the collective will conflict with Alt Hold modes. Also, make sure you are engaging the Alt Hold modes only when V/S is near zero, that way you avoid overcorrections done by the AFCS system. The system will increase/decrease collective to keep altitude constant, and will react to changes in pitch.
Take a look at this demo video: https://www.youtube.com/watch?v=APRfJ_Yc4fo&ab_channel=CaptainKenobi
Beware the system is experimental, and due to lack of support of native helicopter autopilot systems, it may conflict with any hardware input as explained above.
- B@Burnhaven
Thanks I'll try those suggestions. I really only need 20 seconds of "stay alive" time from this system. I'm using keyboard, mouse and a logitech 3D joystick with twist stick for rudder and the single axis control for collective. On a positive note I'm having pretty good luck at landings for a helicopter newbie. Love the Chinook and it's sounds. In multiplayer events it appears as a twin-engine airliner to others, but that motivates them to buy the Chinook so it looks correct :-)
-