Using the enhanced input system
- IA_Lookup (all on default)
- IMC_Default mapping IA_Lookup to three things: A keyboard-key (let’s assume “L”), the “Square” on the PS5 controller, the “Digipad-Up”.
- Using UE5.7 from source, with GameInput SDK + runtime installed.
- Plugins “Game Input Base” and “Game Input (Windows)” enabled, disabled “XInput”.
- EnhancedInputAction IA_Lookup placed in the player blueprint, reacting to “Started” (instruct character to look up) and “Completed” (instruct character look forward).
InputSettings.ini
[GameInputPlatformSettings_Windows GameInputPlatformSettings]
bProcessController=True[/Script/GameInputBase.GameInputDeveloperSettings]
+DeviceConfigurations=(DeviceIdentifier=(VendorId=1356,ProductId=3302),Description=“PS5 DualSense controller”,bOverrideHardwareDeviceIdString=True,OverriddenHardwareDeviceId=“DualSense”,bProcessControllerButtons=True,bProcessControllerSwitchState=True,bProcessControllerAxis=True,ControllerButtonMappingData=((1, “Gamepad_FaceButton_Left”),(2, “Gamepad_FaceButton_Bottom”),(4, “Gamepad_FaceButton_Right”),(8, “Gamepad_FaceButton_Top”),(16, “Gamepad_LeftShoulder”),(32, “Gamepad_RightShoulder”),(64, “Gamepad_LeftTrigger”),(128, “Gamepad_RightTrigger”),(256, “Gamepad_Special_Left”),(512, “Gamepad_Special_Right”),(1024, “Gamepad_LeftThumbstick”),(2048, “Gamepad_RightThumbstick”),(8192, “Gamepad_Special_Left”)),ControllerAxisMappingData=((0, (KeyName=“Gamepad_LeftX”,DeadZone=0.239532,bIsPackedPositveAndNegative=True)),(1, (KeyName=“Gamepad_LeftY”,Scalar=-1.000000,bIsPackedPositveAndNegative=True)),(2, (KeyName=“Gamepad_RightX”,bIsPackedPositveAndNegative=True)),(3, (KeyName=“Gamepad_LeftTriggerAxis”)),(4, (KeyName=“Gamepad_RightTriggerAxis”,DeadZone=0.239532)),(5, (KeyName=“Gamepad_RightY”,Scalar=-1.000000,bIsPackedPositveAndNegative=True))))
When clicking on the “mapping” icon in the IMC, and pressing a button on the controller, it does correctly map it (so GameInput is working).
Nor running the game, I observing the following:
When pressing :
- the key, my characters looks up, as long as the key is pressed (correct).
- the “Square” on the gamepad, the character looks up as long as pressed.
- the “Digipad-up” on the gamepad, the first time pressing the character looks up (as long as pressed) and on releasing the character looks back forward. So far perfect. However when now pressing the Digipad-up again, the character rapidly toggles between looking up and forward- because there is a rapid flow of “Started” and “Completed” events firing.
Why is it so specific to the digipad buttons?
Any ideas where to look?
Update: Created a new FirstPerson shooter template with 5.6, updated to locally built 5.7, enabled the two gameinput plugins, disabled xinput, enabled processing of the gamecontroller in the plugin gameinput settings, mapped an IA to process the dpad-up, changed the bp_firstpersoncharacter to just do print strings on started and completed. Press & hold the first time, 1x “started”, releasing the button “completed”. Now press & hold again - it keeps rapidly printing the debug-strings,. toggling between them (expected: printing “started” exactly once, until released).
Noticed the option “Process Controller Switch State”, which specifically mentions you might want to disable it, if the dpad is processed as buttons already. Disabled it - pressing it in the game, no reaction anymore.
Also, Game Input for Windows - Experimental Release Notes | Tutorial has a definition for the ps5 controller with (256, “Gamepad_Special_Left”) and also (8192, “Gamepad_Special_Left”) which is a bit suspicious.
This sounds different, but is similar in them mentioning that the first time it works.
Update2:
Just noticed that each time after a focus switch (ALT+TAB) out and back into the window, the button will behave correct 1 time - and after that will repeat again even if being held.
)