DualSense Edge Trigger Switch Support

[Loriborn]

The DualSense Edge includes two additional inputs with two inputs each for the "trigger" sliders used to increase or decrease travel of the associated trigger. While the firmware handles clamping the trigger range based on that value, it would be beneficial to extend the value of this input to the plugin as well, in order to allow for different behavior based on the state of the trigger travel switch.

The two inputs map as such:

The yellow highlighted values default to 09 when at their default value, the topmost mode with longest travel, with either corresponding to the left and right slider respectively (though inversely, the first byte is the right slider, and vice versa). These values are 00 if the slider is at any value except default.

The blue highlighted value corresponds to the value of the slider:

Left Paddle State : 00 -> 10 -> 20
Right Paddle State : 00 -> 40 -> 80

I may PR this myself but I must determine how best to handle the input value itself, as the state is exclusive but having an Input Action Mapping for the three states feels inappropriate. An 1D axis value (0, 0.5, 1) may be applicable here.

[rafaelvaloto]

@Loriborn

A good solution would be to configure a parameter that represents the state of the Edge control (slider/paddle), instead of using multiple Input Action Mappings. This parameter can represent the slider/paddle position as a 1D axis value, for example:

• for the leftmost position (Left: 00 | Right: 00) 0
• 0.5 for the middle position (Left: 10 | Right: 40)
• for the rightmost position (Left: 20 | Right: 80) 1

This makes the handling of slider input much more streamlined and manageable, and also aligns with common practices for analog inputs.
Additionally, I recommend adding a function in the DualsenseProxy class that sets this parameter in the DualsenseLibrary class, specifically for the Edge control. This way, the logic is centralized and easy to maintain.

This setPaddleState function in the DualsenseProxy class will also be exposed and available for configuration through both Blueprints and C++, just like the parameters for Gyroscope, Accelerometer, and Touchpad. This ensures easy access and flexibility for developers working in Unreal Engine, regardless of whether they prefer visual scripting or native C++ code.

Suggested function signature:

SetPaddleState(int32 ControllerId, EControllerHand Hand, float Value)

This function should update the corresponding value in the DualsenseLibrary. If the connected accessory/control is an Edge slider, this function should be called accordingly to update its state.
This approach will keep the implementation flexible and ready for future extensions.

[rafaelvaloto]

Hi @Loriborn ,

I added a separation of the DualSense and DualSense Edge devices, would that make this implementation easier? Or do you think it would be unnecessary?