Mouse cursor detection issue in Proton

[RAMChYLD]

The mouse cursor is janky when playing on Linux via Proton. I have to offset the mouse cursor to be able to click on anything at all. Namely, I have to position the mouse cursor below the item I want to click instead of on the item I want to click at all to be able to get it to select.

[zirize]

I’m on an AMD GPU + AMD CPU setup running Ubuntu 24.04, and I’m using X11 instead of Wayland. Under this environment the game runs absolutely perfectly for me.
what’s different between your setup and mine?

[Boothy]

Are you on Ultrawide?

Not got the game (yet, I have the old version), but I've seen this same behaviour in other games when not using a standard widescreen resolution.

[Parciwel]

Originally posted by Boothy:

Are you on Ultrawide?

Not got the game (yet, I have the old version), but I've seen this same behaviour in other games when not using a standard widescreen resolution.

I am not on ultrawide and have the smae problem.

[Boothy]

Ah okay, so not that then (good to hear in a way, as I am on ultrawide!).

My next thought would be what Proton are people using? i.e. standard, experimental, GE Proton etc.

It's sometimes worth switching to experimental for a specific game just to try it out. (Game > Settings > Compatibility).

[zirize]

Originally posted by Boothy:

My next thought would be what Proton are people using?

I only game on Linux and I've played dozens of titles on Steam, but I've honestly never bothered checking which Proton version I'm using. I just stick with the default Steam assigns and everything usually runs fine.

[Boothy]

Originally posted by zirize:

I only game on Linux and I've played dozens of titles on Steam, but I've honestly never bothered checking which Proton version I'm using. I just stick with the default Steam assigns and everything usually runs fine.

Me too, only on Linux these days, still got Win 10 in dual boot, but haven't used it for ages now, and plan to wipe it at some point.

99% of the time you'll be fine on the default Proton these days. But it can be handy to switch to experimental sometimes, if the default Proton is having issues.

I switched to Linux about 2 years ago now, and in the early days quite a few new releases didn't always play nicely on initial release for me, and switching to experimental normally resolved the issue.

Although I had a couple that didn't work there either, so I started using GE Proton instead, which is a bit more cutting edge (which I now manage via ProtonUp so nice and easy).

All the updates from GE and experimental will get rolled into the default Steam Proton at some point anyway, although Valve seem to favour stability rather than cutting edge (which is a good thing).

If you look under Settings > Compatibility (global Steam, or Game specific), you'll see everything from Proton 3 through to Proton 10 (beta), plus experimental and others.

Note, if you've not switched Proton before, it's not a big thing if you do it for a specific game, so a quick test is easy if you have issues. You do Game > Settings > Compatibility: Tick 'Force the use...' select experimental (or whichever) in the drop down, close, and you can launch the game immediately. No reboots or Steam restarts needed. Just make sure the game isn't running when you do the change.

If you want to go back to default Proton, just go back into the game settings and untick the 'Force the use...'. Again no restarts or anything needed.

[zirize]

Originally posted by Boothy:

99% of the time you'll be fine on the default Proton these days. But it can be handy to switch to experimental sometimes, if the default Proton is having issues.

I'm the type who just googles for a fix whenever something breaks—I don’t really bother testing Proton versions myself. Funny enough, the games that do give me trouble are often the ones with native Linux builds. When that happens, I just force the Windows version and run it through Proton instead. That's basically the only time I ever touch the Compatibility options.

[Boothy]

Lol, I've also had the same issue with native Linux versions, and forced Proton instead, which fixed the issue.

One example being Civilization VI (haven't even bothered with VII), I had missing world leaders and other glitches with the Linux version, but everything just worked fine after forcing Proton.

Shame really, but I'd rather it work via Proton than not work properly under native Linux!

[zirize]

Originally posted by Boothy:

Shame really, but I'd rather it work via Proton than not work properly under native Linux!

Honestly, that’s not necessarily a bad thing. It means distro developers can build their systems however they want without worrying about staying compatible with every game’s native libraries. And long-term, there’s no guarantee we’ll even be on x86 CPUs forever. If we eventually end up running games through something like QEMU-Wine, the Windows x86 binaries might actually end up being the more future-proof option.

[Saito]

Noticed this as well, found out going into window mode and back into full screen fixes it, i think its got to do with how the game detects resolution.

[electro-duck]

Originally posted by Saito:

Noticed this as well, found out going into window mode and back into full screen fixes it, i think its got to do with how the game detects resolution.

THANKS ! A alt+enter 2 times solved the issue. (Shortcut for fullscreen/windowed)

[ArcaneGamer]

Best solution, if you're on Proton with windowing system Wayland, is this launch option.

PROTON_ENABLE_WAYLAND=1 %command%

Check in Ubuntu Gnome UI > Settings > System > About > System Details

Other specs of my sys:
- Ubuntu 24 LTS
- AMD RX
- Proton 9.0-4
- SMR 1.0.7

*Please Valve, add markdown support!*

[FVD]

no issue on my side

[ArcaneGamer]

Originally posted by FVD:

no issue on my side

I'm fairly confident that this is a Wayland incompatibility with some versions. Getting the version via command is windowing system specific.

echo $XDG_SESSION_TYPE

[FVD]

Originally posted by ArcaneGamer:

Originally posted by FVD:

no issue on my side

I'm fairly confident that this is a Wayland incompatibility with some versions. Getting the version via command is windowing system specific.

echo $XDG_SESSION_TYPE

I have downloaded to Steam OS and it has downloaded proton 10 for me. I can see you are using 9, maybe try updating it