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
- [Linux] Screen.SetResolution immediately applies windowed resolution when switching from Fullscreen to Windowed mode
- Lighting window allows non-cube map texture for Environment Reflections, throwing invalid texture type (2D) error
- Console warning “MismatchingRepositoryProjectMessage” when creating a new Unity Version Control workspace
- [Ubuntu] VFX Graph Enum Value menu stretches across screen when entered long Enum Value
- Unclear warning message in Rendering Debugger about the Play mode Debugger Overlay
Resolution Note:
Fixed with 2020.2.0a8, backported to 2020.1.0b2, 2019.3.6f1