dburne Posted November 19, 2015 Posted November 19, 2015 Hey gang, So I was flying the convoy single mission this afternoon, and during combat I kept noticing the helicopter starting to fly crazy , like it was in a mind of it's own. After a short time I would look down and notice the three autopilot channels would be off ( bank, pitch, heading). I would quickly engage them again, but it happened another time or two. Not sure why this happened or what might be going on, I have been adding a few more controls to my HOTAS but do not show any conflicts, and I don't see any command that would disengage those three autopilot channels simultaneously... I have been flying this mission a few times this week, and today was really the first time it has happened like that. And no, Flight Director was not engaged. I did recently add the altitude channel to a button on my joystick, but don't see how that could be causing all three channels to disengage like that. I am flying in 1.5 , so may be just something going on there.. Any ideas? Thanks, Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
BaD CrC Posted November 19, 2015 Posted November 19, 2015 It happens when you are pulling a bit too hard on the cyclic or do some too crazy stunts like trying to dodge a missile. Sas is giving up and disconnects. https://www.blacksharkden.com http://discord.gg/blacksharkden
ED Team Raptor9 Posted November 19, 2015 ED Team Posted November 19, 2015 (edited) The three most common causes for those channels to disengage are: 1) The Doppler system hasn't warmed up yet after startup and the player tries engaging auto-hover. If you don't see your digital ground speed readout in the top left corner of your HUD, means the Doppler hasn't warmed up yet. The auto-hover function needs Doppler to maintain position. (Shouldn't be an issue on missions where the Ka-50 is already running) 2) The player engages the auto-hover a few meters above the ground, or is already in auto-hover and descends to within an few meters of the ground. SAS doesn't like this and the channels will disengage. 3) The "Autopilot Emergency Disengage" command is mapped to a stick or keyboard command and the player inadvertently pushes it, killing all SAS channels. Battle damage to the main hydraulic system will also cause one or all of the SAS channels to disengage due to the fact the SAS needs hydraulics to affect the flight control servos, but the channels will flash if this happens, not simply turn off. Edited November 22, 2015 by Raptor9 Grammer error like a knucklehead 1 Afterburners are for wussies...hang around the battlefield and dodge tracers like a man. DCS Rotor-Head
dburne Posted November 20, 2015 Author Posted November 20, 2015 Ah thanks guys, that probably explains it then. I think I was pretty low, and also was probably yanking the chopper around pretty good as I was in some heavy combat. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Recommended Posts