A widespread problem with Unity games built for Linux is that Screen.lockCursor causes Input.GetAxis to return unusable mouse deltas. It can even cause the game to hang and crash after a few seconds of trying!
The known workaround has been to not lock the cursor, which is simply unacceptable.
If anyone has experience working around this issue, please use this thread to chime in.
I’ve filed a repro case with Unity (585517) and hope they will take this issue seriously. If you’re experiencing this problem, please use the bug reporter and reference this case. This needs to be fixed, like a year ago.
My game (The Novelist) is also suffering from this issue. Most Linux players have said the game runs perfectly (it’s built on Unity 4.3.4), but two players have run into it in Ubuntu 13.10 (which is bizarre, since other players on Ubuntu 13.10 can run the game with no issues).
Are there any workarounds other than not locking the cursor? That’s not an option for my game.
Is there anything that players can do to avoid this issue? Are there driver settings they can change?
If it helps, here are the system specs from one of the players for whom this makes the game unplayable:
UBUNTU 13.10 64bits (up-to-date)
GNU bash, version 4.2.45(1)-release (x86_64-pc-linux-gnu)
Linux Version 3.11.0-17-generic
Compiled #31-Ubuntu SMP Mon Feb 3 21:52:43 UTC 2014
Eight 2,2GHz Intel i7 Processors, 6GB RAM
Window manager:
Unity : unity 7.1.2
Graphic hardware and driver version:
GeForce GT 540M/PCIe/SSE2 using GeForce GT 540M/PCIe/SSE2 (standard version)
This is a serious problem for the game I’m making. Linux build seems to be OK, mouse responds and works fine for GUI elements on Intro scene, but game is unplayable after this due to this issue. I am testing on Ubuntu 12.04.
