Reproduced 3/3 times, issue also occurs in //UE5/Release-5.0 - CL 20979098 Binary. Confirmed NOT a Regression.
Expected Results are based on the previous Input system.
Actual Result: For X axis (W/S), S is always prioritized (resulting in player moving backwards, showing as -1), and for Y axis (A&D), D is always prioritized (resulting in player moving right, showing as 1).
Expected Result: Player shouldn't move if opposite directions are inputted at the same time (based on old Input system)
How does TextureRenderTarget2D get TArray<uint8> type data?
Why does the REMOVE method of map container remove elements have memory leaks?
What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?
How do I set a material as a post-processing material?
How to delete some elements correctly when deleting an array loop?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-173678 in the post.
0 |
Component | UE - Gameplay - Input |
---|---|
Affects Versions | 5.1 |
Target Fix | 5.3 |
Created | Jan 9, 2023 |
---|---|
Resolved | May 24, 2023 |
Updated | May 24, 2023 |