So, Unity3D based games don't work correctly for you? Well it happens to me too and a helpful email from a GOL fan got it sorted, read on for how.
Unity3D is the tool used to make games like Rust and Rochard for example. Unlike Rust though Rochard isn't first person so it doesn't suffer the issue. It seems to happen mainly on first person games.
For a little bit of background, see this bug here. For some reason when a Unity game is built for Linux it can completely screw up your mouse axis under Linux.
If you also suffer from the issues please comment and vote there to get the point across to Unity.
The trick is to try a different window manager like Openbox. I run Manjaro KDE, but it also happened on Cinnamon too.
So, to fix it and try this at your own risk, install Openbox on your distribution and when you want to play a Unity3D-based game run this .sh script:
That will replace your current window manager with Openbox.
To get back to your original window manager on KDE for example it's as simple as this:
Or if you use Compiz then it's this:
Just replace the name with your current window manager.
That's all there is to it, and it worked perfectly for me. It's quite annoying having to go through hoops like this, but it makes the situation a bit more bareable for now.
If you have any other tips, let us know in the comments. Article taken from GamingOnLinux.com.
Unity3D is the tool used to make games like Rust and Rochard for example. Unlike Rust though Rochard isn't first person so it doesn't suffer the issue. It seems to happen mainly on first person games.
For a little bit of background, see this bug here. For some reason when a Unity game is built for Linux it can completely screw up your mouse axis under Linux.
If you also suffer from the issues please comment and vote there to get the point across to Unity.
The trick is to try a different window manager like Openbox. I run Manjaro KDE, but it also happened on Cinnamon too.
So, to fix it and try this at your own risk, install Openbox on your distribution and when you want to play a Unity3D-based game run this .sh script:
#!/bin/bash
openbox --replace &That will replace your current window manager with Openbox.
To get back to your original window manager on KDE for example it's as simple as this:
#!/bin/bash
kwin --replace &Or if you use Compiz then it's this:
#!/bin/bash
compiz --replaceJust replace the name with your current window manager.
That's all there is to it, and it worked perfectly for me. It's quite annoying having to go through hoops like this, but it makes the situation a bit more bareable for now.
If you have any other tips, let us know in the comments. Article taken from GamingOnLinux.com.
0 Likes
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
I completed rochard in Linux and works ok
0 Likes
Yeah, he should of mentioned that the mouse problem is for games like first person shooters that use the mouse to look around, like Rust, Verdun, Zigfrak ect.
This fix also makes vsync work in Unity engine games. When the engine detects that you are using a compositing window manager, it forces vsync off. So for me in KDE, every game using this engine (except bit-trip runner 2) has horrible screen tearing. Bit-trip was made in a earlier version of the engine that didn't have this problem.
The developers intentionally coded it this way, because games were running like crap when people had compositing running. Specifically Unity on ubuntu with compiz, back when you couldn't use the "unredirect fullscreen windows" option in compiz to stop games from getting composited because of some bug which got fixed shortly after. They didn't even give us a way to disable the behaviour in a config file or something, this is pretty sad.
Hopefully this stuff gets sorted in the new version that's coming.
This fix also makes vsync work in Unity engine games. When the engine detects that you are using a compositing window manager, it forces vsync off. So for me in KDE, every game using this engine (except bit-trip runner 2) has horrible screen tearing. Bit-trip was made in a earlier version of the engine that didn't have this problem.
The developers intentionally coded it this way, because games were running like crap when people had compositing running. Specifically Unity on ubuntu with compiz, back when you couldn't use the "unredirect fullscreen windows" option in compiz to stop games from getting composited because of some bug which got fixed shortly after. They didn't even give us a way to disable the behaviour in a config file or something, this is pretty sad.
Hopefully this stuff gets sorted in the new version that's coming.
0 Likes
I have had this issue in every DE except XFCE and unity. In both these DE’s all my games run flawlessly.
0 Likes
I have always played Unity3D games from Xfce. I guess that is why I have never had problems.:|
0 Likes
I use openbox, but I still get mouse jumps in Rust. :c
Yes, the mouse jumps in rust. But that is yet another problem lol. In particular this Fix stop the issue that people have with the character getting stuck looking at the sky and having to alt-tab to get the game to respond again. The problem only occurs on some window managers, generally the compositing ones.
0 Likes
Like Hamish, I use XFCE and have never seen mouse problems in Unity
0 Likes
I don't have the issue, but if you're using Steam, you could probably set the required commands in the launch options for each of the problem games. That would handle changing the WM back and forth automatically for you. I did something similar with AntiMicro to load and unload kb/mouse to gamepad mappings for certain games.
0 Likes
I've never had issues, though I use LXDE.
0 Likes
It does look like it's mainly affecting compositing then which is why you most likely don't see it on XFCE.
0 Likes
nope.. it happens for me with marco and and with xfwm as well.
without compositing.
it seems to be issue with 1920x1080 native monitor resolution, anything lower than that doesnt cause the issue.
also with xfwm i can start game in windowed mode and then when in menus i alt+space and switch to fullscreen. no issues with mouse then.. cant do that with marco however.
without compositing.
it seems to be issue with 1920x1080 native monitor resolution, anything lower than that doesnt cause the issue.
also with xfwm i can start game in windowed mode and then when in menus i alt+space and switch to fullscreen. no issues with mouse then.. cant do that with marco however.
0 Likes
it seems to be issue with 1920x1080 native monitor resolution, anything lower than that doesnt cause the issue.
What about higher? I'm running ratpoision, no compositing and 1920x1200 on my main monitor with no common issues on Unity games.
0 Likes
it seems to be issue with 1920x1080 native monitor resolution, anything lower than that doesnt cause the issue.What about higher? I'm running ratpoision, no compositing and 1920x1200 on my main monitor with no common issues on Unity games.
i dont know anyone with higher resolutions that have issues with it
just 1920x1080
0 Likes
it seems to be issue with 1920x1080 native monitor resolution, anything lower than that doesnt cause the issue.
also with xfwm i can start game in windowed mode and then when in menus i alt+space and switch to fullscreen. no issues with mouse then.. cant do that with marco however.
In KDE it doesn't matter if you use a resolution smaller, it's still broken without changing wm.
I can start windowed and then tell kwin to make it fullscreen, and it does work around the mouse issue. But vsync is still broken then and get worse performance.
0 Likes
Indeed I tried windowed on KDE which used to solve it on Cinnamon, no dice on KDE I have to switch WM to Openbox.
0 Likes
it seems to be issue with 1920x1080 native monitor resolution
No issues with e16 on Gentoo with 1920x1080.
0 Likes
To be honest I no longer buy games using Unity. It's kinda ironic with this particular engine with cross platform being the prime argument, but I've never experienced as many problems in any other engine as I have with Unity games.
0 Likes
For the record I run no DE with Compiz 0.8 as WM (Arch 64) and have no issues with Unity games. Not that I have many though. Screen res 1680x1050.
0 Likes
Patreon
PayPal
See more from me