Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.3f1
Issue ID
785927
Regression
No
[WIN] Input is not processed when Game View is not focused
How to reproduce:
1. Open attached project
2. Open scene InputTest.unity
- Make sure you have a controller attached
3. Play the scene
4. Wiggle the left joystick of the controller
- Note it prints the x and y axes
5. Click Clear in the console
- This defocuses the game view and focuses on the console window instead
6. Wiggle the left joystick again
- Note how nothing is printed in the console now
- This does not happen on OSX; the controller is always detected there
- Reproduced in Version 5.3.3f1 (910d71450a97)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
With the deprecation of the old input system and the introduction of the new input system package, this bug has been moved over to the new input system can be found here
https://github.com/Unity-Technologies/InputSystem/issues/430
also
https://github.com/Unity-Technologies/InputSystem/issues/376
There are parts of this issue in the new input system that are both a bug and enhancement and needs some design around the gamestick controlling the UI.