Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.4.4
1.5.0
Issue ID
ISXB-387
Regression
No
Play Mode Input Behavior does not function when Update Mode is set to Process Events Manually
How to reproduce:
1. Open the attached “repro-project.zip“
2. In the Edit → Project Settings → Input System Package change “Update Mode” to “Process Events Manually”
3. Plug in a controller and enter Play Mode
4. Move the cursor in the Game View and the Cube should follow the cursor
5. Click on the Inspector and then move the cursor back to the Game View
Expected result: The Cube does not follow the cursor until the click action is performed on the Game View.
Actual result: The Cube follows the cursor when moved across the Game View.
Reproducible with: 1.4.4 (2020.3.43f1, 2021.3.16f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a24)
Reproducible on: macOS 11.6.5, Win 10
Workaround: The “Play Mode Input Behavior” functions as intended when “Update Mode” is set to “Process Events in Dynamic Update: or “Process Events in Fixed Update”.
Note: The issue is not reproducible on a built project.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sprite Masks affect Sprite Renderers outside their range when a Light2D is present with specific Target Sorting Layers selected
- URP Lens Flare is rendered in the wrong position when Render Graph Compatibility Mode is enabled and Render Scaling is not 0
- Editor crashes on DrvPresentBuffers when loading RenderDoc while using OpenGLES 3.0 or OpenGLES 2.0 Graphics API
- [Test Runner] Incorrect name under Window > Panel after project restart
- [iOS] Crash when using fallback fonts created at runtime
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.