Forum Discussion

minty-tiff's avatar
minty-tiff
3 years ago

Mouse sensitivity completely incorrect on Arch Rolling

Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number RX 480
Enter RAM memory size in GB 8
What is your gamertag/PSN ID/EA Account name? Minty.tiff
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Are you using any software with an overlay? Yes
If yes, can you list them here? Steam
If you disable this software, does that have any effect? No
Which Legend were you playing (if applicable)?
Which Legends were your squad mates using (if applicable)?
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Not applicable
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Aiming
Did your squad mates also experience the issue? I don't know
How many matches had you played in a row before the issue occurred? 0
When did this happen? (dd.mm.yy hh:mm) 02.05.2023 23:00 CET
How often does the bug occur? Every time (100%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? Mouse sensitivity is completely off since the last update. In Linux, I am used to Source requiring exactly 2.0x the sensitivity that it does in Windows (with Raw Input enabled). I'm not sure where this specific issue lies, but it's not a big deal. I play at 0.30 on Windows, and 0.15 on Linux (through autoexec.cfg in Apex, since it doesn't allow for hundredths adjustments through UI). However, since the most recent update, Apex is completely off; the sensitivity scalar does not match *any* of my games (Overwatch, which is at 1/3 of Source's; regular Windows, which would be twice the usual; or anything else). If set to the same sensitity used in CSS/CSGO, it is *way* too insensitive. This issue was not present last time (a week or two ago) I played.
What should be happening instead? Correct source-to-source sensitivity mapping
Steps: How can we find the bug ourselves? 1. Ensure that you are running on latest Arch Rolling. 2. Enable Steam Play for all titles. 3. Run Apex with the automatically recommended Proton version (sorry, I can't seem to check the exact version Steam is enforcing; I will try running it with Proton-GE 7.54 and 8.1, to see if the issue persists). 4. Compare camera movement to any other Source powered game.

‌

 No additional info provided; the ticket should be plenty. If not, please provide a template for the additional info required.

Kind regards,

2 Replies

Replies have been turned off for this discussion
  • minty-tiff's avatar
    minty-tiff
    3 years ago

    P.S.: I can confirm that it seems to correctly map to Windows sensitivity (that being 0.30, instead of the 2x increase -0.15- that I usually use in Source games on Linux), using Proton-GE 7.54. Perhaps it is an issue specific to Proton 8?

    Though the fix (?) is appreciated, since this fix does not propagate to most other Source branches, perhaps it is better to keep the old "broken" sensitivity (requiring 2x that of Windows's) until each branch has a patch ready.

    EDIT: If taken into consideration, please also allow players to adjust sensitivity by hundredths, and perhaps even thousandths, through UI. Though it may seem silly, it would help to partially prevent weird issues like this. (e.g. I previously had to have a separate mouse profile for Apex at 6000 DPI x 0.2 Sensitivity, to hit an "effective 1200 Source"-sensitivity).

  • FAT9L's avatar
    FAT9L
    3 years ago

    I've never experienced anything like this, across multiple different Linux systems and various Source games. Am currently on Arch as well, using Proton Experimental, and have been playing Apex on it for around a year with no specific issues.

    Are you using libinput (Wayland), xinput (X11), or something else (ie gnome-tweaks) to manage your mouse? Here's an Arch wiki page about mouse acceleration that may be relevant. What you're describing is definitely not normal behavior, and it makes me think that your dpi settings may be different between operating systems, or that your prefix has something configured weirdly. An issue may need to be raised with the Proton team, if not.

About Apex Legends Bug Reports - Archive

23,008 PostsLatest Activity: 5 years ago