Unreal Engine Issues

Started event of EnhancedInput continues to be triggered when a key is pressed and held down from before the level transition.

When a key is held down after a level transition, the "Started" event of the Enhanced Input is triggered continuously.  ...

Enhanced Input Axis Actions repeatedly firing the last input value when entering a Common UI menu

When using an axis mapped input action such as looking around with a gamepad joystick, then opening a Common UI menu, the last input axis value will keep firing irrespective of the current joystick ...

Common UI/Enhanced Input UI action binding issue

They've nailed it down to the following logic FUIActionBinding::TryCreate which doesn't check for the InputAction specified.// Make sure there is no existing binding for the same action associated w ...

Raw Input plugin fails to process some negative values

Came from a UDN: [Link Removed] Proposed fix is to change `FRawInputWindows::ParseInputData` to use this logic instead: ``` ... USHORT BitSize = ValueCapsBuffer[iValue].BitSize; LONG SizeMask ...

EnhancedInput Chorded Actions do not work on higher priority mappings

Reported from Prismatic: It appears that the Add Mapping Context function currently prioritizes low numbers over high numbers, which seems inconsistent with the function description and some parts ...

bIgnoreAllPressedKeysUntilRelease behaves differently for triggers in EnhancedInputAction and triggers in InputMappingContext

For actions that are triggered on the Input mapping context, simply adding or removing an InputMappingContext with no related key override with the bIgnoreAllPressedKeysUntilRelease option will caus ...

Chorded Trigger evaluation can be evaluated to unexpected results in some specific cases

Slate widget may incorrectly consume key up events causing some UI to get stuck

This is a bug reported from a UDN customer with a sample project and video attached that goes over the input consumption states and how they are incorrectly being set when changing UI modes ...

Logging out and then logging in as a new user results in slate creating multiple Slate User IDs

I believe this is happening because when you change your logged in user, the Slate Application will automatically create a new second slate user with an ID of 2. This is bad because the Slate App is ...

Cannot bind lambda functions to Enhanced Input component