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
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
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