Turbo Arrow IV - snap roll to the right
-
Hi have the same erratic behavior as mentioned above.
In my situation, a work around is to activate the yoke as rudder “in the assistance menu”. During take off I still use the pedals to keep the centerline. No need to for yoke input. I use Elite pro pedals controlled by an Elite fa2020 driver and fsuipc. Hopefully this might help by users affected with that issue -
@Martyn i have this issue when I have HSI activated. I put the heading bug to my actual heading, then press Heading button and then Engage autopilot, it snaps violently to the right.
Autopilot off and the ingame yoke immediately snaps to neutral again.When I put the other option in the EFB (so not HSI but the abbreviation eludes me now) and I follow the same procedure, all is fine.
-
@Skyhigh747 That's interesting because you are describing my normal takeoff procedure for flying runway heading. I changed yokes and the problem went away but maybe I wasn't using AP to track the runway heading. (I've been out of town for a few days and haven't tested further). That's useful info.
-
FWIW, I wasn't able to fly the turbo Arrow much before I left home on a trip. When I came back, I first installed the patch and have made numerous flights in the plane. It might be unrelated to the patch, but I have not had the problem again and I have been using the original yoke that I originally had the problem with.
-
@Skyhigh747 said in Turbo Arrow IV - snap roll to the right:
I put the heading bug to my actual heading, then press Heading button and then Engage autopilot, it snaps violently to the right.
Interesting... Try it the other way around. Engage the autopilot and then press the heading button. I have a hunch...
-
I have had the issue of the arrow (all versions) trying to kill me when engaging autopilot with a hard roll that eventually inverts the airplane.
Both my Keyboard camera was mapped to left right arrows (which also corresponds to the 4 and 6 key on the number pad as well as aileron right and left roll. It is not an actual conflict because this is only activated with the num lock key that switches back and forth between the keypad controlling the ailerons or the camera.
However, If you accidently hit the num lock key you switch from camera mode over to aileron mode and instead of moving your view left or right, you are directly entering aileron input without realizing it. But the autopilot remembers and when it is engaged it will then snap roll.
I completely removed the keybindings for the keyboard for aileron left, right, up and elevator up and down from my keyboard since I have a Thrustmaster.
This seems to be a tremendous improvement. I feel this is more of a work around than a solution.
One other tip. If you are on the ground and activate heading and autpilot and the wheel snaps to the left or the right, try the following. Make sure autopilot is engaged and put the heading bug directly on your current heading...and then ...wait. Just wait. Internally the guidance is going around 360 degrees. If you wait (it could be as long as 45 seconds), the heading will come back around and the wheel will straighten out. You are then calibrated and can shut off the autopilot and heading and you will be set for when you are in the air. At least that worked for me several times in experiments on the ground.
-
Yup this has been plauging me as well, turn on the auto pilot and it rolls hard right (very rarely hard left)
But not all the time! It may happen once every couple of gaming sessionsFor me it feels like it's an autopilot command problem
On my bravo I just mash between the the Hdg Nav App and Rev buttons and it will eventually start to behave itself.I've tried to systematically to work out the comnination of buttons to press to correct it but it doesn't seem consistant :(
But mashing those buttons does work after a few rotations
-
@Cristi-Neagu said in Turbo Arrow IV - snap roll to the right:
Interesting... Try it the other way around. Engage the autopilot and then press the heading button. I have a hunch...
Turning the autopilot ON first, then turning on HEADING mode, after the heading bug has been set to the desired heading, seems to work well for me all of the time...
