Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.0-preview.5
Issue ID
1224897
Regression
No
Mouse movement isn't recognized in Editor Play mode and Build when it is accessed using Remote Desktop
How to reproduce:
1. Open the attached project ("Input system Remote connection.zip") in machine accessed by Remote Desktop
2. Open "Input System Test" scene
3. Enter Play mode
4. In-Game view press spacebar to switch between New Input/Built-in Input systems
Expected result: Sphere moves together with mouse
Actual result: Sphere isn't moving
Reproducible with: 2019.3.3f1, 2020.2.0a2
Could not test with: Versions before 2019.1 are not supported by New Input System
Note:
- Attached video on how to reproduce it using EnvIronman on windows
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed with 2020.2.0a8, backported to 2020.1.0b2, 2019.3.6f1