protonscr

Add environment variable for 'Automatically capture the mouse in full-screen windows'

protonopen Feature Request
ValveSoftware/Proton#9127 · opened 2025-10-22 by NyxDaylight · updated 2025-11-01 · 3 comments · github
NNyxDaylight 2025-10-22 github

Feature Request

I confirm:

  • [x] that I haven't found another request for this feature.
  • [x] that I have checked whether there are updates for my system available that
    contain this feature already.

Description

An environment variable for proton that enables 'Automatically capture the mouse in full-screen windows' from winecfg without needing to use proton tricks

Justification

The current method of having to open winecfg in every game that has moues capture issues is clunky and would be useful to just pass a launch parameter for a game when needed.

Llamemantis 2025-10-26 github

This is badly needed for those of us using more than 1 screen.

Issues with mouse not staying within game application occurs with a number of games like the new Arc Raiders, The Finals, The Outlast Trials, Legacy:sword and sorcery, etc.

Symptoms:
This issue happens when 3 things happen.

  1. In a sweep motion, You move your mouse towards your second screen.

  2. While moving, you click once (or rapidly) and itll allow your mouse to escape the game application.
    The cursor appears rapidly blinking on the second screen. But still interacting with the game, although at this point your cursor will only allow you to turn in game until you reach the border of your second screen.

  3. click a second time and itll unfocus your game application as youve now clicked on your second screen.


Given that utilizing gamescope has not yielded any fixes, i can only hope that im not implementing the fixes correctly, which further clarifies the need for an accessible method to easily force cursors to stay in game application.


Issue with Cursor escaping the game application on dual monitor set up

Issue transferred from https://github.com/ValveSoftware/Proton/issues/9145.
@lamemantis posted on 2025-10-26T21:11:47:

Games with this issue: Almost any game that is First Person camera, The Finals, Arc Raiders, Peak, Mordhau, The Outlast Trials

Additional info: Fedora 42 Silverblue (happens on workstation as well), GNOME as shipped on Fedora.

Proton Versions: Proton 7.0-6, Proton 8.0-5, Proton 9.0-4, Proton Experimental(tried bleeding edge as well), Proton Hotfix

The issues persists the same exact way through these titles and have been tested with the proton versions I've listed.

Symptoms: The cursor escapes from the game application when moving and clicking your cursor towards the direction of your second monitor when playing a game in first person.

Recreate issue:

  1. Move your cursor in a sweep motion to the direction where your second monitor is at.
  2. start clicking as you move and cursor will escape the game application

Notes on issue:

  • If you dont move your cursor fast enough it wont escape the game application. Spam clicking will make it easier to replicate the issue.

  • Gamescope didnt help my situation. Perhaps i didnt do it right but it would be a good reason to add an accessible feature to force cursor to stay in game application. Perhaps in the form of a game launch command or a check box in steam properties. It can be very cumbersome for people who are still new and have trouble finding proper answers.

Llamemantis 2025-10-29 github

@kisak-valve
I only made a separate issue post to make sure people and most importantly the devs could find the issue posted itself as an issue to be prioritized instead of having to come across it inside a feature request post which may not come off as urgent as a bug/issue.

If you think this is still the right call then I respect it. I just wanted to clarify

A couple more things:

what is the likelihood that the issue will be simply noticed by the devs?

Is there a timeframe where the post is deemed as "old" and forgotten and can be reposted as a nudge to the devs that the issue still exists?

ZZeroIndex-x636A06 2025-11-01 github

I am also having trouble with this issue in any first person shooter games as well... I specifically have noticed it in The Finals and Just Cause 3 but it can be replicated in other games as well...

Proton versions

Upstream links