Spitfire Rudder trim slow for Axis movement

[psjshep]

Maybe I am missing some configuration, but no matter what I do to tweak the rudder trim it always moves very slowly.

I have been using Authentikit's elevator & rudder controls, which use rotary encoders on a Leo Bodnar board to push 2 buttons (1 for each direction)

I have been able to use Joystick Gremlim to map to a vjoy joystick axis for both elevator trim & rudder trim (virtual X & Y axis).

The elevator trim can be tweaked in Joystick Gremlin such that the amount of X-axis (as I have bound it to) matches the rotation in-game - works VERY well.

When I try with the rudder trim, it doesn't matter what values I use, the rudder trim ALWAYS moves at the same slow motion... the physical movement I make with the rotary will eventually synchronise with the in-game movement... but takes about 10 seconds to reach the final point... slowly!

I have tried to alter the joystick .lua file & use values >1.0 for rudder trim, but it doesn't change the actual speed of the rotation - it almost seems like it isn't an analogue axis, but a button press....

Any idea anyone?

Phil

[LeCuvier]

Rotary encoders produce very short-duration contact closures and therefore produce very slow movement if you use them with commands intended for pushbuttons.

In some cases I have been able to change the response "speed" by increasing or decreasing the gain of the related object in "clickabledata.lua", but that did not work in this case because the command in "default.lua" uses a different button number, so there is no related object.

[psjshep]

Yeah... I know button press controls tend to be slower than axis only controls....

I used Joystick Gremlin & vjoy to create a virtual joystick movement in X - this was then bound to the Axis control section, not the button selection... but it moved at the same speed.

As a test, I used the throttle as a true axis movement - got the same result.

Which is the gain in clickabledata.lua ?

Thx for the feedback (as always)Phil

[Olliecast]

I’d love to get this reacting in the same speed as the elevator trim. 
 

I have a rotary controller that turns instantly when calibrating in usb devices but it’s really slow when reacting in dcs with the spit. 
 

@NineLineanything you’d recommend to increase the reaction for it? 

 

[LeCuvier]

This button is programmed to rotate at a fixed "speed", until its position matches the axis input value. There is nothing we can do about this behaviour.

On 11/3/2021 at 10:33 AM, psjshep said:

..Which is the gain in clickabledata.lua ?

...

In "clickabledata.lua" the clickable rudder trim wheel is represented by this line:

elements["RTRIM_WHEEL"] = default_axis_limited(_("Cockpit.SpitfireLFMkIX.trim_rudder"), devices.CONTROLS, device_commands.Button_44, 146, 0.0, 0.1, false, false, {-1.0, 1.0})

The 0.1 near the end of the line "... 0.0, 0.1, false, false, {-1.0, 1.0})" is the gain for the object type "default_axis_limited". It seems to have no effect for the rudder trim knob.
I created a new axis command bound to the cockpit button and increased the gain to 0.5, but the button still turns at the same slow rate.

[psjshep]

Thanks for looking & for the explanation... appreciated.

Phil