Search Issue Tracker
Won't Fix
Votes
6
Found in
2017.2.2f1
Issue ID
1061672
Regression
No
Mouse axis is not returned when calling Input.GetAxis() and using Remote control
How to reproduce:
1. Open TeamViewer or another Remote Control program
2. Open same Remote Control program on another machine and get access to control the first machine
3. On controlling machine, open attached Unity project "GetAxis RDP Issue"
4. Load scene "InputGetAxisTest"
5. Enter the play mode
6. Move computer mouse around the Game view
Expected result: Sphere is following the mouse position.
Actual result: Sphere doesn't follow the mouse position when using Unity via Remote control.
Workaround: use Input.mousePosition instead of Input.GetAxis().
Reproduced with: 2018.3.0a5, 2018.2.0f2, 2018.1.8f1, 2017.4.7f1, 2017.2.3p2, 2017.1.4p2.
-
misun1191
Nov 23, 2019 21:07
Yes, this is a severe problem. The workaround would only work for custom script in the play mode, and the basic manipulation would still remain problematic on Unity Editor. For example, I can't move the objects or rotate the camera in the Scene view with mouse, and it is extremely frustrating.. (I don't know whether I can switch the mouse behaviour on Editor).
I had used Unity5.4 on Windows with Remote Desktop and it was fully functioning. Since I switched to Unity2018, 2019, I can no longer work remotely... I don't understand why Unity stopped supporting this.
-
unity_cma7iR9olN89VA
Oct 04, 2018 20:28
I am also experiencing the same problem. Mouse completely unresponsive in the Unity editor.
Running Windows Remote Desktop Client on a Mac. The windows PC is running windows 10.
This is a severe issue as it means Unity can not be used when using a remote desktop. Many developers use remote desktops but are therefore unable to use Unity.
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
All resources have been moved to the new Input System. It can be updated via Package Manager or directly here: https://github.com/Unity-Technologies/InputSystem