Proton
Proton copied to clipboard
ValveSoftware
Games not launching on primary monitor with Proton 9.0-1 on multiple monitors.
Hello,
Currently, If I launch any game using Proton 9.0-1 it will launch on my secondary monitor which is on the left. When launched with Proton 8.0-5 the game will launch on my primary monitor which is on the right. Which is how it's always worked before.
For some reason proton 9.0-1 does not seems to be launching on the monitor that is set as the primary one but whichever one is the left most one.
My setup is a bit odd though so not sure if that has anything to do with it, I have two GPUs in my system like so:
GT 710: Using the Nouveau driver. Connected to my Secondary monitor on the left. RX 6500 XT: Connected to my Primary monitor on the right.
Is anyone else with multiple monitors having this issue?
Distro: Arch Linux. DE: Gnome 46.1 on X11.
Hi
I have the same Issue. Seems to be the same with all games when using Proton 9.0.1 and Proton Experimental. Have to revert to 8.0.5. This is using the Nvidia Proprietary Driver 550 on X11.
Using : NVIDIA GeForce RTX 4060 Laptop GPU/PCIe/SSE2
Distro: Tuxedo OS (Ubuntu based) DE: KDE Plasma 5.27.10
Hi,
I have the same issue, it seems Proton 9.x needs to have the primary monitor on the left of the multi-monitor setup. If you do that as a workaround then after the downside would be that some games (not sure if all) will take as max resolution reference the primary monitor. To me it happens for MS FS2020 and my left monitor is a 1080p laptop while my former primary monitor is a 2k external monitor, not ideal at all. GE version has the same issue, so far.
Using: NVIDIA 2070 Archlinux i3wm
Hi,
I have the same issue, it seems Proton 9.x needs to have the primary monitor on the left of the multi-monitor setup. If you do that as a workaround then after the downside would be that some games (not sure if all) will take as max resolution reference the primary monitor. To me it happens for MS FS2020 and my left monitor is a 1080p laptop while my former primary monitor is a 2k external monitor, not ideal at all. GE version has the same issue, so far.
Using: NVIDIA 2070 Archlinux i3wm
there is going to be a fix? i want to use proton 9 but this problem prevent me from doing that, i need also to keep the main monitor on right side
Bump, this is a huge issue, i have 3 monitors, one center 4k and two 1200p, one of them vertical one horizontal and any game opened with proton will always, without fail, no matter what i set in the launch options or in lutris, launch on the vertical leftmost monitor. even going as far as to disable all but my main monitor still messes up the resolution of most games
Bump! The same issue. In the Overwatch 2 there are 2 display options, but both of them are "Display 1".
Using: NVIDIA 3080 drivers: 550 Pop_OS (Ubuntu based) X11+Gnome
Same issue here. Any game I run with Proton 9, any minor version, will launch on one of my secondary monitors, and if I move the game window to any of the other windows I can't interact with the game.
Using: Nvidia 2080ti + Nvidia GT1030 (3 monitors to the 2080ti and 1 monitor to the 1030) PopOS X11 Gnome
Bump. Friend of mine with Linux Mint x11 cinnamon, amdgpu/radeonsi. Proton games start on the leftmost screen regardless of which one is primary
+1, it seems to work fine if my primary monitor is on the left ([0, 0] coordinates, I believe), but fails if it's on the right
This has been a problem since proton 9s beta released and it still persists. Ive just been using the latest protonge 8 version for my games.
Recently tried Valves new Deadlock playtest and the exact issue of not registering mouse inputs after moving it to the primary monitor (right) appears. Deadlock crashes on proton 8 versions so Valve is seemingly creating its compatibility around proton 9 so a fix or workaround would be appreciated.
I can confirm this is still a problem with Proton 9.0-202.
Long story short... did a new install of Fedora 40, installed Steam, installed latest versioned Proton (9.0)... much trial and error with no success, searched, found this issue, installed Proton 8 and now the games start on the external monitor (right side). There are still some issues I haven't figured out - basically the games freeze almost immediately or soon after. I don't know if that's related to Proton or Nvidia or something else.
I've done more testing, but pretty much the same results. I'm using the same laptop (same hardware), but 2 different versions of Fedora (37, 40), so different versions of the kernel, X11, nvidia, etc. I have 2 bootable partitions - one contains Fedora 37, the other Fedora 40.
On Fedora 37, using Proton 8 I don't have any problems... all the games I've tried startup on whichever monitor is defined as the Primary and all the games work fine.
On Fedora 37 using Proton 9 the monitor the games start on depends on the position rather than what's listed as Primary. If the external monitor is configured as LEFT of the internal or ABOVE the internal, then the games will start on the external monitor. If the external monitor is configured as RIGHT of the internal or BELOW the internal, then games will start on the internal monitor. So, it SEEMS like Proton 9 is always using 0,0 as the position to start and doesn't consider which monitor is configured as Primary. Whichever monitor the games start on they do run fine (on Fedora 37).
On Fedora 40, the monitor the game starts on is the same as Fedora 37, but if the game is started on the external monitor regardless of the Proton version it will freeze after a short period of time. Sometimes the game freezes while starting up, sometimes while loading a save, sometimes after the save is loaded. In the case of Witcher 3 (which seems to be the most consistent and forgiving), it loads fine and in fact I can sometimes play without problems until I bring up the map, then it will freeze soon after. The other 2 games I mainly tested with (Skyrim and Fallout 4) both tend to freeze at some point during the loading screens.
Hi folks - I'm pretty baffled here. I always have my primary monitor on the right for testing because I know that there are often more issues with the primary monitor on the right (since Linux WMs typically have it on the left by default). We haven't been able to reproduce the failure that is reported here with several different multimonitor setups. In order to attempt to figure out what is going on here, could folks who are experiencing this bug please post:
- The output of "xrandr --listmonitors" from your impacted setup
- Copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report.
- List an couple of titles of games you've personally seen this issue with as example titles.
- Get a log with PROTON_LOG=+event,+x11drv,+x11settings,+win,+system,+fshack,+msg %command% of launching a title where it goes to the wrong monitor, ideally with Proton Experimental.
~$ xrandr --listmonitors
Monitors: 3
0: +XWAYLAND0 3840/700x2160/390+1500+240 XWAYLAND0
1: +XWAYLAND1 2400/520x1500/320+5340+900 XWAYLAND1
2: +XWAYLAND2 1500/520x2400/320+0+0 XWAYLAND2
Computer Information:
Manufacturer: ASRock
Model: Z370 Killer SLI
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
CPU Family: 0x6
CPU Model: 0x9e
CPU Stepping: 0xc
CPU Type: 0x0
Speed: 4900 MHz
8 logical processors
8 physical processors
Hyper-threading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Debian GNU/Linux 12 (bookworm) (64 bit)
Kernel Name: Linux
Kernel Version: 6.1.0-23-amd64
X Server Vendor: The X.Org Foundation
X Server Release: 12201009
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20240806.97925
Video Card:
Driver: AMD AMD Radeon RX 6750 XT (navi22, LLVM 15.0.6, DRM 3.49, 6.1.0-23-amd64)
Driver Version: 4.6 (Compatibility Profile) Mesa 22.3.6
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x73df
Revision Not Detected
Number of Monitors: 3
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 7740 x 2400
Primary Display Size: 27.56" x 15.35" (31.54" diag), 70.0cm x 39.0cm (80.1cm diag)
Primary VRAM: 12288 MB
Sound card:
Audio device: USB Mixer
Memory:
RAM: 32028 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: de_DE.UTF-8
Total Hard Disk Space Available: 1874720 MB
Largest Free Hard Disk Block: 1620927 MB
Storage:
Number of SSDs: 3
SSD sizes: 2000G,0B,0B
Number of HDDs: 0
Number of removable drives: 0
List of Titles:
Every single one where proton 9.0_2 is involved, ive yet to see a single one where this didnt happen. the game always seems to be displayed over the edge of the rightmost monitor, as if it assumes a bigger resolution than the monitor has, or launch windowed no matter what
Examples:
- Xenonauts, Detects monitor resolution of 1440x900 in launcher, launches on wrong monitor windowed no matter what you tell it(no im not using the built in wine wrapper, i am using proton through lutris, though going through steam has the same issue)
- Trackmania Nations Forever
- Starcom Unknown space
-Skyrim all versions/Fallout 3,NV,4 All with Script extender and without, modded or not. Launcher Again Detects the 1440x900 resolution
-Flyout
-The Long Drive
-Hell even libre office does this when run through proton
-D-Info 1995 (phone book software from 1995) also does this
-Saints Row 3
As for logs, Ive been messing around with it for about two hours now and i cant get it to give me a log, or at least to tell me where its supposed to be. I know it gave me logs in the past, as there is logs in my home folder from when proton decided to take 15 minutes to launch a game, which turned out to be steam cloud doing.... things. Is there a option to tell it that i want the log file here und exactly here?
giving it PROTON_LOG=+event,+xPROTON_LOG=+event,+x11drv,+x11settings,+win,+system,+fshack,+msg PROTON_LOG_FILE=/home/martin/Desktop/logfile.log %command% as an argument in lutris doesnt seem to phase it.
@MartinKurtz I'm not 100% sure if Lutris is moving things around somehow. You can also go into your Proton folder in ~/.steam/steam/steamapps/common/Proton - Experimental (by default) and rename/cp user_settings.sample.py to "user_settings.py" and then edit the PROTON_LOG : 1 line -- just replace "1" with "+event,+x11drv,+x11settings,+win,+system,+fshack,+msg". The default location is ~/steam-[appid].log.
@alasky17 Well... I was just about to test and give you the info you're looking for and then I noticed there's a new version of the Steam Client. I figured it would be prudent to update the client before testing.... bad idea.
Now, when I start steam all I get is the black steam window with the spinning gear icon in the middle. Nothing else in the window, no way to close it other than to kill the process. Any idea how to fix this or downgrade back to the previous client version?
I can give you at least the 1st and 3rd items you wanted:
xrandr --listmonitors Monitors: 2 0: +*HDMI-1-0 1920/527x1080/296+1920+0 HDMI-1-0 1: +eDP-1 1920/344x1080/194+0+0 eDP-1
Games I've tried: Skyrim, Fallout 4, Witcher 3, Outer Wilds, I'm sure there's a few others, but those are the ones I've mainly been testing with.
If I can get the steam client working again, I'll be happy to post the other info you're looking for.
@alasky17
The output of xrandr --listmonitors:
Monitors: 2
0: +*HDMI-A-1 1920/527x1080/296+1920+0 HDMI-A-1
1: +DVI-D-1-1 1920/477x1080/268+0+0 DVI-D-1-1
Steam System Information:
https://gist.github.com/apemax/25579d072e6380c5b9cfc7b4d4f6ee5c
Steam Runtime Diagnostics:
https://gist.github.com/apemax/ff450f9ed870ff10b606eb829d794e6b
Proton log files from LEGO Star Wars: The Skywalker Saga:
And Battlestar Galatica: Deadlock:
Both run using Proton Experimental on X11.
I am unable to reproduce this on Wayland.
I will also mention for me at least this also happens with Native Linux games run using Steam Linux Runtime. The one I have noticed this with is War Thunder, Running it through Steam Linux Runtime it will launch on my left monitor, If I launch it directly outside of Steam it will launch on my right primary monitor.
If you need any more information just ask. :)
@alasky17
I was able to get my steam client working again. So now I can give you the logs. You asked us to test with Proton Experimental, but I seem to be having a separate problem with it.... all it does is "Processing Vulkan Shaders"... then when it gets almost done quits or aborts... the game itself never starts.
So, I used Proton 9 (Beta), which actually appears to be newer than Experimental:
Proton Experimental => 9.0-202 Proton 9 (Beta) => 9.0-203
$ xrandr --listmonitors
Monitors: 2
0: +*HDMI-1-0 1920/527x1080/296+1920+0 HDMI-1-0
1: +eDP-1 1920/344x1080/194+0+0 eDP-1
I also see the same issue with Fallout 4 and Witcher 3 on both Fedora 37 and Fedora 40. I've seen it with other games as well, but only briefly checked them: Outer Wilds, Witcher 1, Halo and I'm sure a few others.
I'd be happy to further test specific games if you like.
The issue with the game never actually starting is something i had too, thats what i narrowed down to steam cloud, so i started using lutris and that worked well to circumvent that
@MartinKurtz @zelburg (and anyone else) Could you try keeping your monitors in the same position (primary on right, etc) but making them "top aligned" so that they are +x+0, and then check if you still see the issue? I suspect you might, just trying to reduce a variable :) Thank you for all the details, logs, etc! I'm hoping that between all the info provided, something will stick out as the common variable that is causing y'all to all see this behavior on 9.0 vs 8.0 specifically...
@MartinKurtz @zelburg (and anyone else) Could you try keeping your monitors in the same position (primary on right, etc) but making them "top aligned" so that they are +x+0, and then check if you still see the issue? I suspect you might, just trying to reduce a variable :) Thank you for all the details, logs, etc! I'm hoping that between all the info provided, something will stick out as the common variable that is causing y'all to all see this behavior on 9.0 vs 8.0 specifically...
How does one check to see if your monitors are top aligned and change how they are aligned? I know with Nvidia I believe you can change it in nvidia-settings but I don't know how with a AMD GPU.
Also, As I can't reproduce this on Wayland I checked the output of xrandr --listmonitors:
Monitors: 2
0: +*HDMI-2 1920/530x1080/300+1920+0 HDMI-2
1: +DVI-D-1 1920/480x1080/270+0+0 DVI-D-1
Some of the numbers are different to the output from X11, Don't know if that helps.
xrandr
$ xrandr --listmonitors
Monitors: 2
0: +*DP-2 2560/598x1440/336+1920+0 DP-2
1: +eDP-2-1 1920/344x1080/194+0+250 eDP-2-1
System Information
https://gist.github.com/padthaitofuhot/d944f1995783e6bc0c92f13b875fda26#file-steam_system_information-txt
System Diagnostics
https://gist.github.com/padthaitofuhot/d944f1995783e6bc0c92f13b875fda26#file-steam_system_diagnostics-txt
Titles
- Literally anything running on Proton 9
- Mechwarrior Online
- Baldur's Gate 3
- Fantasy Grounds
- Ostriv
- Per Aspera
- Valheim
- Mechwarrior 5
Log from normal monitor position for game Ostriv
Log from "top aligned" monitor position for game Ostriv
@MartinKurtz @zelburg (and anyone else) Could you try keeping your monitors in the same position (primary on right, etc) but making them "top aligned" so that they are +x+0, and then check if you still see the issue?
@alasky17 , I'm more than happy to test some different settings, but also not quite sure how to check if the monitors are "top aligned" or how to change them if they're not?
I use Xfce Settings -> Display, to change the size/position of my monitors. I'm not opposed to using xrandr or some other method to tweak the settings, I'm simply not very familiar with it.
You mention "... so that they are +x+0", but if I look at my xrandr --listmonitors output:
$ xrandr --listmonitors
Monitors: 2
0: +*HDMI-1-0 1920/527x1080/296+1920+0 HDMI-1-0
1: +eDP-1 1920/344x1080/194+0+0 eDP-1
Specifically, the section for monitor "0", which is the external (right side) monitor set as Primary, it shows "... +1920+0", which appears to be what I think you mean by "top aligned". In other words, +1920 in the X direction (ie 1920 to the right), and +0 in the Y direction (ie. 0 from the top or "aligned" with the top of the left monitor). Yes? No? Maybe?
PS. As a side note, or maybe it's related. The /XXX values for the size of each monitor I assume refer to the physical size? I think it's little easier seen with this output:
$ xrandr | grep ' connected'
eDP-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
HDMI-1-0 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 527mm x 296mm
The "physical" size values for the internal monitor (eDP-1) seem to be correct. 344mm x 194mm, is approx 13.5" x 7.6", which appears to match the physical size of my internal monitor if I measure it with a measuring tape. But the physical size values for the external monitor (HDMI-1-0) seem to be off. 527mm x 296mm, is approx 20.7" x 11.6", but if I measure my external monitor it's closer to: 23.5" x 13.5" (or 597mm x 343mm). I have no idea if that's important or irrelevant.
My external monitor is a Sceptre E275W-19203RD 27" LED. My internal monitor is part of a MSI GS66 Stealth 10UH254 laptop, and the monitor itself according to "inxi -xxx -G" is a Sharp LQ156M1JW23.
Complete inxi -xxx -G output in case that's of value:
$ inxi -xxx -G
Graphics:
Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Micro-Star MSI
driver: i915 v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: none
bus-ID: 00:02.0 chip-ID: 8086:9bc4 class-ID: 0300
Device-2: NVIDIA GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB]
vendor: Micro-Star MSI driver: nvidia v: 550.90.07 arch: Ampere pcie:
speed: 2.5 GT/s lanes: 16 ports: active: none off: HDMI-A-1
empty: DP-1,DP-2,eDP-2 bus-ID: 01:00.0 chip-ID: 10de:249c class-ID: 0300
Device-3: Bison HD Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 1-11:3 chip-ID: 5986:2127 class-ID: 0e02
serial: 01.00.00
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 24.1.2
compositor: xfwm4 v: 4.18.0 driver: X: loaded: modesetting,nvidia
unloaded: fbdev,nouveau,vesa alternate: nv dri: iris
gpu: i915,nvidia,nvidia-nvswitch display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.00x11.26")
s-diag: 1055mm (41.55")
Monitor-1: HDMI-A-1 mapped: HDMI-1-0 note: disabled pos: primary,right
model: Sceptre F27 res: 1920x1080 dpi: 93 size: 527x296mm (20.75x11.65")
diag: 666mm (26.2") modes: max: 1920x1080 min: 640x480
Monitor-2: eDP-1 pos: left model: Sharp LQ156M1JW23 res: 1920x1080 hz: 300
dpi: 142 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") modes: 1920x1080
API: OpenGL v: 4.6 vendor: intel mesa v: 24.1.7 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: Mesa Intel UHD Graphics (CML GT2)
device-ID: 8086:9bc4
API: Vulkan v: 1.3.290 layers: 7 surfaces: xcb,xlib device: 0
type: integrated-gpu driver: N/A device-ID: 8086:9bc4 device: 1
type: discrete-gpu driver: N/A device-ID: 10de:249c device: 2 type: cpu
driver: N/A device-ID: 10005:0000
API: EGL Message: EGL data requires eglinfo. Check --recommends.
@alasky17 top aligned and primary the leftmost monitor works fine, as it does when the primary is the leftmost without top align, but top aligned with a monitor left of the primary , the game will always launch on the leftmost monitor, often in the wrong resolution
Hi folks - looks like the "top-aligned" theory has been disproven. Thank you for testing and for all the info/feedback! We will keep searching for the answer :)
I thought it was a user error; happening like this for every game.
I did seem to fix it with the 0 top aligned, I have a vertical and its above my main on the left, set at so top is aligned and everything went back to main. Will keep testing other games. Arma3 is working.
Hello, I have the exact same problem with Bloons TD 6
xrandr --listmonitors
Monitors: 2
0: +*HDMI-0 1366/160x768/90+1366+0 HDMI-0
1: +HDMI-1-1 1366/522x768/293+0+0 HDMI-1-1
GTX 1060 3GB (HDMI-0) AMD ATI Radeon Vega Series / Radeon Vega Mobile Series (HDMI-1-1) AMD Ryzen 7 5700G with Radeon Graphics (16) @ 4.673GHz (so the secondary display on which the game is launcher on newer proton versions is connected to the motherboard not the graphics card) DE: I3-WM X11 Arch Linux I think it's a unity game so I figured an older proton version wouldn't affect the game so I set it to use Proton 7.0-6 and now it does launch in the primary display. When I switch the game from one display to another on Proton 9 (or whatever was steam launching it with as I hadn't configured it) it seems fine but the game no longer responds to clicks although it does capture the cursor since it renders the custom cursor from the game. But on proton 7.0-6 it works as expected, launches in the correct display and changing displays has no effect on it. LMK if I can be any help, if you require any further information.
Proton 9 Displaying on the leftmost monitor is a legacy issue with x11. If your Linux Distro and your Desktop Environment support it, (you'll have to look it up) download and install the wayland package(its not called wayland, its different for every desktop env), then reboot your PC and switch to it in your Login Screen.
@apemax (and anyone else who this applies to) ... it looks like you have multiple AMD drivers installed -- "AMD open-source driver", "driver-version" : "2024.Q3.2 (LLPC)" and "AMD proprietary driver", "driver-version" : "(AMD proprietary shader compiler)". Just to confirm -- you only have 1 GPU, right?
Could you try temporarily uninstalling the proprietary AMD driver and keeping only the open-source mesa driver installed, and seeing if that fixes the issue? If this does fix the issue-- did you do any special configuration etc when installing/setting up your drivers? I was not able to reproduce this issue by merely installing the amdvlk (or amdvlk-pro) packages, but the "AMD proprietary driver" was also not showing up in Steam Runtime Diagnostics, which indicates to me that I wasn't fully mimicking your setup.