Rudder pedals not working

[GoldenBoy]

These are old analog pedals, Thrustmaster Rudder Control System.  I'm using the quality and highly lauded Necroware Gameport to USB converter.  They show up in JOY.CPL under Windows 10, and Windows XP and calibrate perfectly. I have used the pedals to replace the keystrokes in Plane Controls: YAW configuration, using joy1_axis_y.  However, the rudder pedals produce no effect on the actual rudders on the planes.  They don't move.

Checking the rudder pedals on the Fine Tune screen, I show the pointer swinging wildly many times per second!!!  Sensitivity, Dead Zone, and Edges settings have no effect on the pointer.

I have edited the CURRENT.ACTIONS, and the CURRENT.MAP files as these did not show that the rudders were recorded as being set up.

DEVICES.TXT show that the Necroware Arduino Micro HAS been recorded in the file as Joy1.

Now, again this converter has successfully passed the JOY.CPL applet, and shows virtually rock-solid on the horizontal Z-axis WITHIN Joy.cpl.

Why aren't the rudder pedals working with the rudder on the plane?  Why is the Fine Tuning on the rudder pedals swinging wildly, and don't respond to the Sensitivity, Dead Zone, and Edge adjustments?

Also, why doesn't IL2 offer support for their product?

[Gutholz]

9 hours ago, GoldenBoy said:

YAW configuration, using joy1_axis_y.  

...

horizontal Z-axis WITHIN Joy.cpl.

Different axis, is that on purpose? 

Could it be that the pedals maybe have more than one axis (brakes?)

Or maybe the converter has multiple axis that report (usually unused) nonsense values?

 

 

[GoldenBoy]

Yes.  The game wants to use joy1_axis_y, but it swings wildly and doesn't respond to the pedals at all.  Whereas AXIS_Z does respond to the pedals in JOY.CPL.  When using Vjoy and Joystick Gremlin, AXIS_Y is jittering like craxy and doesn't respond to the pedals, but AXIS_Z is calm and responds to the pedals.  Now, I'm an absolute noob with Vjoy and Joystick Gremlin.  But, my testing doesn't seem to be getting anywhere.

However useful AXIS_Z may be, IL2 doesn't recognize it.  Vjoy and Joystick Gremlin don't show up in Input Devices.  I can't get Key Mapping to accept Joy1_axis_Z, even though I've hard-coded it within Carrier.map and Carrier.actions.  Puzzling.

CORRECTION:  CURRENT.ACTIONS and CURRENT.MAP.  NOT CARRIER...

[JollyJack]

Do you have an TM xbox with Thrustmapper X installed by any chance? That destroys USB input behavior with IL2 and DCS.

[GoldenBoy]

Interesting about the TM xbox.  I'm afraid not. Strictly PC.  And run my tests on-line and offline.  Still looking for answers.

[Gutholz]

So the problem is that you can not assign the working AXIS_Z in IL2 because it always uses the broken AXIS_Y?

When IL2 asks you to move the desired axis back & forth, it always assigns the randomly jittering AXIS_Y? Like wanting to assign buttons on a keyboard but a cat is walking around on the keyboard.

So you must try to edit the config file. I think current.actions is maybe the wrong file, try global.actions or create a custom profile and use that.

[GoldenBoy]

This problem was resolved by re-flowing solder on each of the kit contacts on the PCB.  This caused the pointer within the game to stabilize.  I must've had some cold contacts on the board.  

Thanks for your ideas!