Jump to content

Recommended Posts

Posted

Could someone please offer some input into this issue for me. But before I get it it I will preface it by saying that I have talked to others (it occasionally happens to them as well), I have searched the manual (but I may be missing something) and I have dissected my HOTAS profile looking for a conflict...

 

Why out of the blue does my Heading, Bank and Pitch AP buttons turn OFF for no apparent reason?? Everything will be going just fine then all the sudden I find myself fighting to keep fine control of my aircraft. I will look down and sure enough they are all turned off. Then in the mist of trying NOT to scrape my Schval camera into the dirt I will turn them all back on.

 

Is this a bug, or is there a button that releases them all at once I am unaware of?

 

It sucks.

[sIGPIC]http://i1138.photobucket.com/albums/n537/16th_Relic/16th-sig.jpg[/sIGPIC]

AMD 965BE, 8GB RAM, ATI5750, Track IR4,TM MFD's, CH FS,PT,PP

"You can take my CH setup when you pry it from my dead, cold hands..."

Posted

  1. Combat damage
  2. Power outage resulted by low RPM of rotors;
  3. Abrupt maneuvers
  4. Too much positive/negative Gs
  5. AP oscillations (I don't know if it is really modeled).

  • Like 1

Wir sehen uns in Walhalla.

Posted

  1. Combat damage
  2. Power outage resulted by low RPM of rotors;
  3. Abrupt maneuvers
  4. Too much positive/negative Gs
  5. AP oscillations (I don't know if it is really modeled).

 

Thanks for the reply. very helpful

 

 

  1. Combat damage -- Not this as it happens at times before I even take damage or engage in hostilities.
  2. Power outage resulted by low RPM of rotors -- Ill keep an eye on this, I am assuming I would get the low RPM warning correct?
  3. Abrupt maneuvers -- possible I suppose but has happened when I am not doing anything too awfully abrupt as well.
  4. Too much positive/negative Gs -- not sure as it happens when I might be in a hover scanning for enemy
  5. AP oscillations (I don't know if it is really modeled). -- I'll pretend I didn't read this as I have no idea what it is and would be sure to make a fool of myself

 

Thanks again for the reply. Rep inbound :thumbup:

[sIGPIC]http://i1138.photobucket.com/albums/n537/16th_Relic/16th-sig.jpg[/sIGPIC]

AMD 965BE, 8GB RAM, ATI5750, Track IR4,TM MFD's, CH FS,PT,PP

"You can take my CH setup when you pry it from my dead, cold hands..."

Posted
This thread might provide some insight:

http://forums.eagle.ru/showthread.php?t=38509&highlight=Autopilot

 

Also, since you asked. There is an "autopilot disengage" button on the cyclic of the real Ka-50 with the corresponding command of LALT + A in the game.

 

 

Thanks CyBerkut. I diables the disengage command hoping that might provide a fix. I did not unfortunately.

 

What they need is an EMERGENCY AUTOPILOT ENGAGE button. :cry:

[sIGPIC]http://i1138.photobucket.com/albums/n537/16th_Relic/16th-sig.jpg[/sIGPIC]

AMD 965BE, 8GB RAM, ATI5750, Track IR4,TM MFD's, CH FS,PT,PP

"You can take my CH setup when you pry it from my dead, cold hands..."

  • 2 months later...
Posted

Autopilot channels turning off below 4m

 

I would think the Emergency Autopilot Disengage is used when the helicopter's flight caracteristics are affected by damage, in which case, the pilot's brain might adapt better than the autopilot which is programmed for a non-damaged helicopter.

 

As far as your autopilot channels turning off, it must be related to the Auto Hover function: when the Auto Hover is engaged AND the radar altitude is less than 4 meters, the autopilot channels will disengage and the (blue) lights will blink for a while, then turn off.

This is by design - not a bug.

 

My advice: use Vertical Descent with caution as it will stop you at 4m (documented), but what if you collective is a bit on the low side and you go down to 3.99m? You then lose your damping channels at a very critical stage of flight, with no audio warning.

i7-7700K@4.8GHz, 16Gb-3200, GTX-1080Ti-Strix-11Gb, Maximus IX Hero, Oculus Rift, Thrustmaster Warthog+F/A-18C, Logitech G940 Pedals.

Posted

I encountered this situation a few times myself. It always occurred when I disengaged Auto Hover after being in a perfect hover.

[sIGPIC][/sIGPIC]

Posted

yes, I have also seen this behavior, and never been able to pin a specific set of circumstances to it (ie too low etc..), except that, as Advent has said, it seems to occur when disengaging the auto-hover...all of a sudden it's like you are riding a bucking bronco ;)...

easy enough to wrestle it under control and re-engage the AP channels ..still, would be nice to know, if it is a modelled feature, exactly what set of circumstances can cause it so to avoid.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...