Jump to content

Bug: MiG-29 autopilot unusable with FFB


Go to solution Solved by BIGNEWY,

Recommended Posts

Posted (edited)

I have a Sidewinder Force Feedback 2, and the MiG-29's autopilot is unusable. When I activate an autopilot mode and don't touch the stick, the trim center moves in the controls indicator, but the stick remains motionless. However, if I move the stick at all, the stick then moves to give extreme pitch and roll inputs, sending the aircraft out of control. If I grab the stick and try to level the aircraft, the autopilot fights me. I have no problems with my Logitech Extreme 3D Pro Joystick (no force feedback), and I haven't noticed any problems with any other autopilots, including the Su-27's, which I believe is similar and works beautifully.

This is a problem on all MiG-29 variants.

 

Here are a couple video demonstrations:

 

 

 

 

I've seen this mentioned tangentially in other threads (e.g. here and here and here), but I didn't find a dedicated thread about this issue, so I thought it would be a good idea to start one.

 

I'm attaching a track file, the DCS log, and my DxDiag info.

 

Would love if this issue could be sorted out soon! It really makes the MiG-29 frustrating to fly, since it's impossible to trim it perfectly so I'm always having to correct to maintain altitude and can never take my hands off the stick.

MiG-29S autopilot.trk

DCS log (MiG-29 autopilot).zip

DxDiag.txt

Edited by N22YF
  • 3 months later...
Posted

I just discovered that this issue seems to surface only if you take your hand off the stick while autopilot is engaged (which is typical, since you typically would need autopilot only when you want to take your hand off the stick). A workaround for the Sidewinder Force Feedback 2 is to just tape over the hand sensor (which is located under the trigger button).

  • 2 years later...
  • 7 months later...
Posted

The SWFFB2 was a stick for the Zero Fighter when MS released the CFS2 for the Pacific Theater, and the seemingly insignificant grip sensor indicates the high quality of the product.

I gave up on the method of blocking the sensor because if I was not careful, the stick would start up with a violent noise the moment Windows started up.

The level flight AP button, a standard feature on Russian fighter grips, is stable in high-altitude cruising.

OS:Windows 7 Ultimate

CPU:Core i7-2700K 4.8GHz

Mother Board:Asrock Z77Extreme6

Memory:G.SKILL DDR3-2133 16GB

Graphic Card:AMD HD7970 1125/1575MHz

Display:Eyefinity / Square x3

  • 6 months later...
  • 2 weeks later...
  • ED Team
  • Solution
Posted

please be sure you cover the hole on the stick with your hand on the sidewinder ffb2, let us know if it helps

IMG_20240912_131815.jpg

  • Like 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted
please be sure you cover the hole on the stick with your hand on the sidewinder ffb2, let us know if it helps
IMG_20240912_131815.thumb.jpg.d632228e988b1b7ecd472b49021cd9cc.jpg
Or even better. Just screw the grip apart and remove the sensor.

Sent from my SM-A536B using Tapatalk

  • Like 2
  • 3 months later...
Posted

I'm also having this issue. Blocking the sensor helps for sure, but over time, I get an "autopilot-induced oscillation" leading to some real violent maneuvers 😛 

A-10C, AV-8B, Ka-50, F-14B, F-16C, F-5E, F/A-18C, L-39, Mi-8, MiG-21, MiG-29, SA34, Spitfire, Su-27, Su-33, UH-1H

Posted
I'm also having this issue. Blocking the sensor helps for sure, but over time, I get an "autopilot-induced oscillation" leading to some real violent maneuvers  
Try to tape over the two sensor wholes, unless you take the sensor out of the grip.
It could be that the stick gets out of "sync" if you remove your hand and then later cover the sensor. I've never seen the behavior described in this thread, while I've always covered the sensor by tape or removed. I've never flown DCS with the sensor "working".

Sent from my SM-A536B using Tapatalk

Posted

Well like I said, I've allready blocked the sensor, so the stick moves while in autopilot when I'm not holding the stick. But that causes oscillation when the autopilot has been on for a while

A-10C, AV-8B, Ka-50, F-14B, F-16C, F-5E, F/A-18C, L-39, Mi-8, MiG-21, MiG-29, SA34, Spitfire, Su-27, Su-33, UH-1H

Posted
Well like I said, I've allready blocked the sensor, so the stick moves while in autopilot when I'm not holding the stick. But that causes oscillation when the autopilot has been on for a while
Ah, misunderstood! What happens if you press trim reset? I sometimes get some real strange trim behaviour when using the autopilot.

Sent from my SM-A536B using Tapatalk

Posted
2 hours ago, MAXsenna said:

Ah, misunderstood! What happens if you press trim reset? I sometimes get some real strange trim behaviour when using the autopilot.

Sent from my SM-A536B using Tapatalk
 

The autopilot works by using trim. So if you reset it the autopilot will just move it again 

Black Shark Den Squadron Member: We are open to new recruits, click here to check us out or apply to join! https://blacksharkden.com

E3FFFC01-584A-411C-8AFB-B02A23157EB6.jpeg

Posted
3 hours ago, MAXsenna said:

What happens if you press trim reset?

I tried that now, and it doesn't help.

A-10C, AV-8B, Ka-50, F-14B, F-16C, F-5E, F/A-18C, L-39, Mi-8, MiG-21, MiG-29, SA34, Spitfire, Su-27, Su-33, UH-1H

Posted
The autopilot works by using trim. So if you reset it the autopilot will just move it again 
I meant turning off the AP and then reset the trim.

Sent from my SM-A536B using Tapatalk

I tried that now, and it doesn't help.
Too bad. I'm not at my computer and can't test.

Sent from my SM-A536B using Tapatalk

  • Recently Browsing   0 members

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