Trimmer Crazy now...BS1, never had this issue before...

[Afterburn]

Edit: Solved - see my post #5 below.

 

I have the Steam version of BS1 v1.0.2 (haven't upgraded yet). I used to use the trimmer to a great extent. It allowed my deflection of my non-ffb stick to be minimal. Now the cyclic does not trim, but the rudder does. Also I have "central position trimmer mode" checked but the rudder instantly jumps without returning the rudder to center (as if that mode is not checked...I think...)

 

I've attached a track. You will see me first try to trim the cyclic to no avail, then trim the rudder (notice the jump immediately after the trim), then attempt to trim the cyclic again. :helpsmilie:

 

trimmer issues.trk

 

Also, I'm using Helios for some GP-Wiz controllers but not for any HOTAS commands (trimmer is on my HOTAS and assigned in game).

Edited November 25, 2011 by Afterburn

[PeterP]

What stick and axis are you using in DCS ?

 

Did you changed your profile lately - maybe your input file is messed up.

This normally doesn't appear in BS1.

[Afterburn]

I'm using an old Saitek X36 HOTAS (still works great after all these years) with X, Y, and RZ assigned to roll, pitch, & yaw. Slider 1 is collective, slider 2 is wheel brake, and RX is throttle.

 

I'm not sure of the time line but I've been adding more and more to my GP-Wiz40 controllers through Helios. I'm pretty sure I had Helios integration before this issue started, but I experimented with gauge output to a second monitor around the time this issue occurred. I used a second profile for the gauge output, and have since reverted back to my original profile within Helios. Reinstall? Anyway I'm in the US, so turkey calls...time to eat.

 

Thanks!

[PeterP]

To nail the culprit down - try to disable GP-Wiz40 next time and use only DCS to assign the commands like trim and the axis. Than see if this problem still exist.

So you know in which direction to search.

 

Enjoy your meal!

[Afterburn]

Solution: I recently plugged in a racing wheel. Best I can figure is it was supplying alternate inputs that DCS was interpreting in a funky way. Unplugging the controller solved the issue. I imagine deleting the assignments would be equally fruitful.:music_whistling:

 

Thanks PeterP for you rapid responses!