Jump to content

Recommended Posts

Posted

Hi all,

 

I got distracted by another sim and just started playing DCS again after v1.01. I like the new trim logic but I've run into an occasional problem that I'm guessing others have already figured out. (a brief search of "controls" yielded nothing...sorry if I missed it). Sometimes after trimming, my stick and rudder "die". I've tried retrimming, holding trim, engaging FD, disengaging FD, and letting go in hope that the trim logic will see that I've returned to neutral. "Something" has worked twice but I wasn't able to duplicate the success. Anyone figure out how to get control back before smacking terra firma?

 

Smokin' Hole

Smokin' Hole

 

My DCS wish list: Su25, Su30, Mi24, AH1, F/A-18C, Afghanistan ...and frankly, the flight sim world should stop at 1995.

Posted

That has been a somewhat common thing since the patch apparently, especially with newer folks such as myself.

Check this post out:

http://forums.eagle.ru/showpost.php?p=731504&postcount=8

 

Keep in mind, if you make any alterations to the .lua file , use notepad++ to make the changes, not standard notepad or word editor, to keep from corrupting any files.

 

Also, if you find yourself in this situation, if you wiggle the stick in a small circle rapidly, and the pedals a small movement rapidly, you will regain control again - just hope your not too low when this happens...

 

I got Black Shark last week, immediately patched, and really battled with this issue off and on in the first few hours. I changed my pitch, roll, and rudder to .2 for all, and this - combined with my awareness and being smooth on the stick and quick to release after releasing trim, seems to have helped me greatly.

 

Hope this helps.

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|

Posted

Yep, that was my problem. However I don't like using wide deadzone on a perfectly good stick. I've decided to return to the old trim logic. Thanks for the help.

Smokin' Hole

 

My DCS wish list: Su25, Su30, Mi24, AH1, F/A-18C, Afghanistan ...and frankly, the flight sim world should stop at 1995.

Posted

Ahhhh, my old trim back. Funny what you get used to.

Smokin' Hole

 

My DCS wish list: Su25, Su30, Mi24, AH1, F/A-18C, Afghanistan ...and frankly, the flight sim world should stop at 1995.

Posted

LOL.

 

Good to see you got it solved somehow.

 

I have a CH Fighterstick and CH rudder pedals and the things have zero noise. In my case the controls were locking up because I was inadvertently pushing the right rudder pedal a tiny bit all the time. It seems like my right foot is heavier than the left one.

 

 

Cheers,

  • 3 weeks later...
Posted

I had the same experience with my Saitek ST-290's roll and rudder occasionally ceasing to function. I found that if I unplug and reconnect its USB plug the controls recenter and operate correctly and reliably again.

I suspect a marginal contact in the USB plug or connector that occasionally goes open. When that happens the Saitek software shows that the roll and rudder centering have shifted off center.

At any rate, it's any easy fix and can be done by pausing the sim.

Posted (edited)

ericinexile,

there is no need to modify your controller's deadzone. All that you need to do is modify the FMOptions file under the Eagle Dynamics/KA-50/Scripts/Aircrafts/_Common folder. This DOES NOT CHANGE YOUR STICK'S DEADZONE. The way that trim works is that it locks out your stick input until you return the stick to the neutral (center) position. What the FMOptions file does is determine HOW CLOSE to the neutral position you have to return the stick to in order to regain control of the aircraft. My settings are 0.20, 0.20, and 0.4. (pitch, roll, rudder respectively). I have not had controller lockout ONCE since I made these changes, and before, I had it all the time. Some people might say that my settings of 0.2, 0.2, and 0.4 might be too large, and make my aircraft do sudden violent manuvers when trimming, possibly causing a crash- this also DOES NOT happen to me, so I like my settings the way they are.

Edited by Speed_2

arrogant, realism-obsessed Falcon 4 junkie

Posted
ericinexile,

there is no need to modify your controller's deadzone. All that you need to do is modify the FMOptions file under the Eagle Dynamics/KA-50/Scripts/Aircrafts/_Common folder. This DOES NOT CHANGE YOUR STICK'S DEADZONE. The way that trim works is that it locks out your stick input until you return the stick to the neutral (center) position. What the FMOptions file does is determine HOW CLOSE to the neutral position you have to return the stick to in order to regain control of the aircraft. My settings are 0.20, 0.20, and 0.4. (pitch, roll, rudder respectively). I have not had controller lockout ONCE since I made these changes, and before, I had it all the time. Some people might say that my settings of 0.2, 0.2, and 0.4 might be too large, and make my aircraft do sudden violent manuvers when trimming, possibly causing a crash- this also DOES NOT happen to me, so I like my settings the way they are.

 

I changed my settings to the same as Speed and I have had no problems. I haven't noticed any sudden jerks when trimming either. Pretty smooth (at least for me) flying. :thumbup:

[sIGPIC][/sIGPIC]

i7 10700K OC 5.1GHZ / 500GB SSD & 1TB M:2 & 4TB HDD / MSI Gaming MB / GTX 1080 / 32GB RAM / Win 10 / TrackIR 4 Pro / CH Pedals / TM Warthog

  • Recently Browsing   0 members

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