No rocker switch support for the Thrustmaster T-flight Hotas X

[Dean]

Hi Gary

Under VA's options for setting up the joystick inputs, I find there is no way to set up a key press for the Thrustmaster's two-way 'rocker' button. I use this rocker (aka paddle or 'rudder') button on the throttle a lot, as this gives me 2 extra much needed key presses, which are most useful considering that this HOTAS setup has very limited buttons anyway.

The throttle 'rocker' button can be set-up for either analogue or digital input. The inputs values for digital read as:

+ joy u-axis (for right key press)

- joy u-axis  (for left key press)

Or if used as analogue:

  joy u-axis (used for yaw control)

I've attached an image of the rocker switch and also an image of the controller inputs shown in the device's settings. The rocker button input is seen as the 'z-rotation' when analogue input is used, or as the 'slider' when digital input is used. The digital input (slider) is the one that adds the 2 extra key presses when the rocker button is pushed left or right. 

Can support for this kind of rocker switch be included into your joystick settings in the near future? It would be greatly appreciated if this could be done.

Look forward to hearing from you, 

Kind regards,

Dean

[Luca D]

If i understand correctly the problems comes from the fact that, even when in digital input mode, the stick still consider the rocker as an axis, instead of a button
Even if it only register the two values "-100" and "+100" without the full analog progression, the fact that Windows shows it as "slider" in the frame above, instead of two buttons in the frame below, means that the driver still reports it as an axis to the other applications

At the moment VA can bind a command only to "true" digital input, that is only buttons/POV hat direction... does that stick come with a profile software? if it does, it should be easy then to map the rocker as two keyboard combinations, and then link those to your VA command.

[Dean Robbins]

I used the default Win 7 driver installation for my HOTAS, but even with Thrustmaster's own driver installation there's still no difference in the controller settings, they're more-or-less identical in operation. Also there's no profiler software for customising the rocker button - or any of the buttons. 

As you've mentioned already, it uses the axis +/- state to switch between the keys

I play the game Elite: Dangerous, and within its menu options under the key bindings the rocker switch is recognised for both analogue and digital inputs. I have lateral thrusters assigned to the rocker in analogue mode, but also have the rocker bound to 2 other keys in its digital mode, so I have 4 functions on the rocker altogether. Nice :) That is very useful to have in-game, but it's of no use in VA when trying to assign the rocker button to various macro-conditions/commands to in-game functions, as that call must be made by the joystick within VA itself.

I'll watch this space and see what Gary has to say about this.

Dean

--

---
You received this message because you are subscribed to a topic in the Google Groups "VoiceAttack" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/voiceattack/pMfazgUitl0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to voiceattack...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dean]

*Bump*

Still waiting for some dev feedback on this request,

Regards

[Xen Xennon]

I also have this controller and having these 2 extra buttons recognized would be very handy - I use them (used to) to toggle from the left <> right panes in the UI panels in ED, but because VA can't detect them means I can't *monitor* when the UI changes state and thus remember where it was when I last brought it up and to correctly always go to the pane I want it to.  I ended up using button 6 for left pane and 7 for right pane which VA does pick up.

... but i would still love to see these buttons picked up by VA - can always use more buttons.

[Gary]

If the stick reports its devices as buttons or POV, VoiceAttack will pick it up.  I did not write any code to handle the analog devices for a stick.  That *may* come way down the road, but it's not in there at this time.  It would require another, 'when I do this' for every command.  Probably, 'when stick is in range: a - b'.  When we start getting this specific is when the user interface becomes too bloated, and will require a lot of review and thought.

Sorry about that!

Gary

[Dean Robbins]

I wasn't sure if this was an easy thing to do or not, but thanks for the reply, Gary. 

--