The root cause appears to be an order of operations change made for [Link Removed] (CL 18309493 in UE5/Main). On EnhancedPlayerInput.cpp:238, the TriggerStateTracker is combined with state evaluated ...
From the user: > Up until 5.3.1 those input modifiers were identical apart from the instanced data. If you upgrade to 5.3.1, not taking the new IMC files, the sensitivity settings will never get a ...
The haptic feedback stuff is meant for VR devices, and has never worked with DualSense or any other console (afaik) that isn't a VR device. We technically could support this, but it would just be ...
This is happening because UEnhancedPlayerInput::UEnhancedPlayerInput is attempting to load the IMC asset, but if your triggers are defined outside the engine module then it would trigger a load of t ...
When a key is held down after a level transition, the "Started" event of the Enhanced Input is triggered continuously. Suspected similar root cause as [Link Removed]. ...
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 ...
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 ...
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 ...