Potential binding situation needs help

[smooreace]

Also posted in Spectrum
https://robertsspaceindustries.com/spectrum/community/SC/forum/51473/thread/scjmapper-news-and-updates/3730209

Is it somehow possible to do conditional key-binds?

An example would be a 3 position toggle. Up is a button (27), down is a button (28), and the center is nothing.
Next to it is a pushbutton (26)...
27 and 26 equate to an action
28 and 26 equate to an action
26 alone equates to a 3rd action

Looking at the AutoPilot section at the lower right of a Warthog throttle specifically

And

Also, is there some kind of voodoo available to add a deadzone to a throttle? There are 2 potential ways I see to set this up, all using the right slider as actual throttle and the left slider as speed limiter slider

1 - Right slider manages forward and reverse thrust with center being zero. Desperately needs a dead zone!
2 - Right throttle runs full 0 to 100%. Left slider, when back beyond detent, engages reverse thrust that is again managed by the right slider.

Neither of these options seems to be able to be accomplished

Thanks for your work.. AMAZING!

[bm98]

From Spectrum:
I don't think that the engine supports this - the engine only maps single game device events to single actions but does not apply logic to it and has no elements to do so. You can do more than one action from a single event e.g. pressing a button may cause break, power zero and more but it starts from a single event.

• you would need an intermediate software either from the manufacturer of the device or Joystick Gremlin or UCR (https://github.com/Snoothy/UCR) where you could define such rules and then also define what the outgoing Joystick action should be. From there you may map it either in the game or with SCJM.
  Such software gets between the device and the software that uses the device and you can do all sorts of 'crazy' things with it.

And about the voodoo...
it would be something like:

	<deviceoptions name="X65F Flight Controller">
		<option input="roty" deadzone="0.030" />
	</deviceoptions>

I have to check if the game supports dead zones for sliders, it does it for axes - I use it with a Thumb-Knob (Rot Y axis) and assigned it to v_strafe_longitudinal (aka Throttle forward/back action) and it worked to have a decent gap between fore and back.
My throttle Saitek X-65F has the left part driving the z-axis, the right part driving slider1 but one would need to see in the game if a deadzone for the slider is possible as it not implies two directions...

[bm98]

Just checked in the game and it supports deadzone on slider1 - actually on all controls of the device it seems:
I have to update the program to support it as well then. For now you would need to add it manually to the XML or in the game.

See last item in the image below - I did not run and see if it really works .... sometimes it shows only the good intention ;-)

[smooreace]

After thinking about it, that makes perfect sense, about the multiple button combination thing.

And I'm one of those dumbasses that never thought to click the bottom right corner and cycle through input devices to get tuning sliders for ALL of my input devices. Stupid mistake!

Thank you