Search Issue Tracker
By Design
Votes
1
Found in [Package]
1.0.0-preview.6
Issue ID
1227077
Regression
No
[New input system] Gamepad input affects standalone builds which are unfocused
How to reproduce:
1. Open attached project "InputBugRepro.zip"
2. Make sure a gamepad is connected
3. In Editor, Build&Run
4. Open two builds
5. Touch gamepad's analog stick
Expected result: only the cube on focus standalone build moves
Actual result: both builds are effected by the gamepad input
Reproducible with: 2019.3.6f1, 2020.1.0b2, 2020.2.0a3 (1.0.0-preview.1, 1.0.0-preview.6)
Could not test with: 2017.4, 2018.4 (new input system was not yet implemented)
Notes:
Does not reproduce with multiple Unity Editors
Reproduces when one Editor is opened/focused and one build is opened
Reproduces with multiple Windows desktops
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
As far as the input system is concerned, this works as designed. When "Run In Background" is off in the player, there's no input being received when not focused.
However, there is some part in Unity (most likely PlayerConnection) that *overrides* "Run In Background" and *forces* it to true in development players -- but not in non-development players. This makes it appear as if the feature isn't working as intended.
After 1.0, we'll have another look at this and se