Cyclic stick freezes after ca. 15 min of flight under 1.0.1

[VS461]

Hey all,

I have an interesting problem after installing patch 1.0.1. During various single player flights (both own created and built-in missions), the cyclic and the pedal freeze at ca. 15 min flight time. This occurs after a trim button press (in various maneuvers, so I think it ain't a factor). The collective remains operative, but pedals and cyclic freeze. I can "release" them on the keyboard (quick push on an arrow key) but it repeats after an other trim button press.

 

This repeatedly happens after ca. 15 mins flight time, during hover, en-route, weapons employment, aerobatics etc. And, if I shake my joy like :joystick:, the cyclic is sometimes back online again, until the next trim press...

 

The rig:

ASUS P5Q Pro

Intel C2D E8400 3 GHz & Scythe Ninja 2

GeIL DDR2 800 MHz Black Dragon 2x2 GB & Scythe Kama Wing

Sapphire Radeon HD4850 512 MB @ 625/1800 MHz & Scythe Musashi

200 GB SATA2 for OS in AHCI mode

LG Super Multi DVD+-RW LightScribe/SecurDisk

Saitek X52+Rudder Pedals+Cyborg 3D Rumble grip hack for collective

 

CPU and GPU temperatures are below 55 °C during flights, ca. 45 °C at idle in these Summer times.

 

The software:

Windows 7 Ultimate RC b.7100 64 bit, with auto updates on

ASUS EPU-6 engine (controls clock speed and voltage automatically)

ATI 8.632.0.0 display driver, Catalyst 9.7

Realtek HD Audio 6.00.0001.5898

DCS:BS with patch 1.0.1 downloaded English version

Saitek 6.0.4.1 drivers, SD6 64 bit (Cyborg 3D not programmable in SD6)

DirectX 11

20/10 Mbit broadband internet connection

 

 

I didn't attach a track file cause I think the problem can't be seen on it (my useless "cyclicing" isn't on screen). But if anyone thinks it's important, I can make one.

 

I think that's all, I hope someone knows the solution.

Cheers!

[JG14_Smil]

I saw this problem for the first time today.. it is a stuck CTRL key. While you tap the CTRl key to end the problem, it is not the keyboard itself causing it, but rather a controller is missing a CTRl release and rendering controls inoperable. CTRL keys can be very unreliable when used as modifiers.

 

 

oh, RCTL ENTER will enable the joystick controller output and you would see the controls not respond.

Edited August 13, 2009 by JG14_Smil

[159th_Viper]

See This Post:

 

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

 

I have mine currently set to 0.1 and have not encountered any issues. A vast improvement from the default 0.05 :)

[JG14_Smil]

thanks Viper,

 

I had another episode where the CTRL key did not save me (must have been a fluke!) :)

 

No more loss of controls for me... went back to the original trim method, which I really like with the added clicks.

[VS461]

See This Post:

 

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

 

I have mine currently set to 0.1 and have not encountered any issues. A vast improvement from the default 0.05 :)

 

I set them to 0.1 and try it. Gonna report if it is good or not.

Thanks guys!!

[VS461]

Hi all,

I tried to increase and decrease the values in the .lua mentioned below with small steps, but no improvements. After every trimming I realized a heavily nose-trimmed state (in a hover, in acceleration, in aerobatics), both Flight Dir on and off (I mainly use FD) and the cyclic freezing went on as well and it begun at the take-off. I resumed to the original values (0.05x2, 0.1) but nothing happened, it was worse than before.

 

My X52 has no deadzone in the Control Panel and no deadzone in the game as well. Maybe there is some interference between the trimmer method and the worn-out X52's physical deadzone (it ain't a new one). The interesting thing is that the new method worked during the first missions and in the first minutes and without any changes in the .lua or other settings.

 

So I am back with the old trimming method and it is okay now. Maybe I'll try again with a new stick.

Thanks guys for your help.

Cheers!

[Marder]

Hi all,

I tried to increase and decrease the values in the .lua mentioned below with small steps, but no improvements. After every trimming I realized a heavily nose-trimmed state (in a hover, in acceleration, in aerobatics), both Flight Dir on and off (I mainly use FD) and the cyclic freezing went on as well and it begun at the take-off. I resumed to the original values (0.05x2, 0.1) but nothing happened, it was worse than before.

 

My X52 has no deadzone in the Control Panel and no deadzone in the game as well. Maybe there is some interference between the trimmer method and the worn-out X52's physical deadzone (it ain't a new one). The interesting thing is that the new method worked during the first missions and in the first minutes and without any changes in the .lua or other settings.

 

So I am back with the old trimming method and it is okay now. Maybe I'll try again with a new stick.

Thanks guys for your help.

Cheers!

 

had the same problem with my x52 yesterday :(

what do you mean with: "So I am back with the old trimming method and it is okay now."?

Edited August 18, 2009 by Marder

[159th_Viper]

what do you mean with: "So I am back with the old trimming method and it is okay now."?

 

You can choose your method of Trim in the 'Options' menu. New Trimmer method ticked by default. Untick to revert to Pre-Patch Trimmer implementation.