Hello @demanuPL, please add PROTON_LOG=1 %command% to some affected game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.
I don't think this is limited to AMD GPUs. I'm finding the same problem on Nvidia. I get a bunch of log output, the game's process shows that it's running when I run ps -ef , but nothing ever happens.
@kisak-valve, here's my log: https://pastebin.com/HFN8b9RU
I also want to point out:
All Proton 7 versions launch games
I've tried every Windows game I have, none of them launch with Proton 8.X. Tried GE, Experimental (both non-beta and bleeding edge), Proton GE, and Proton TKG.
..Is this not being monitored at all?
I've tried multiple kernels, system updates, driver versions (although it's obviously not the drivers since the issue appears on AMD as well).
I can at least add that up until about 4-5 days ago, Proton 8 versions DID launch games, the only for sure bug I found was that Proton versions 8 and later disable DLSS in ALL games, and DLSS works in almost all games for Proton versions up through and including 7.X. I was going to report that bug, but then Proton 8.X stopped even working at all.
@demanuPL @gardotd426 Please try disabling/removing any custom programs/add-ons, especially gamemode and mangohud.
Sorry, that gist was indeed with launch options but I have tried without.
That said, I will get a gist of a Proton log WITHOUT any launch options
because I know that will help anyone looking at the logs.
I will say though, MangoHud/gamemode/gamescope/etc all work fine with
Proton 7.X and Wine 7.X/8.X in Lutris games (as does Proton 8.X). But I
still need to get you that gist, I'll have it for you when I get home
On Wed, May 17, 2023, 11:44 AM alasky17 @.***> wrote:
@demanuPL https://github.com/demanuPL @gardotd426
https://github.com/gardotd426 Please try disabling/removing any custom
programs/add-ons, especially gamemode and mangohud.—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/6763#issuecomment-1551637599,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y337ZEECA6AGDQXCP3ADXGTW7TANCNFSM6AAAAAAX5I64XU
.
You are receiving this because you were mentioned.Message ID:
@.***>
When you run proton through Steam, it is using the Sniper runtime library, which has known problems with both mangohud and gamemode.
That would be a huge relief at least knowing what the problem is, although I'm confused as to why it would have worked a week or two ago with those. But yeah when I get home shortly I'll check and post a gist or if it works I'll post my results.
What's weird is the fact that the games don't crash, they just never actually launch even though the processes are running
@alasky17 So, MangoHud is the problem as far as games not launching at all goes. Do you know if the bug is in the Sniper runtime or in MangoHu? Or could you point me toward the bug report so I could see about investigating it some more?
Turns out gamemode is what was causing the Doom Eternal problems, I'll go report there.
Proton 8.X still has a pretty huge bug in it, but it's a separate issue - all DLSS is disabled in any Proton version (official and non-official) from 8.0 onward. DLSS works in all games except Dying Light 2 on Proton 7.X
When you run proton through Steam, it is using the Sniper runtime library, which has known problems with both mangohud and gamemode.
I've identified another program that's causing issues with proton 8, SteamVR Beta [#6782 (comment)](https://github.com/ValveSoftware/Proton/issues/6782#issuecomment-1559035800)
@gardotd426 Replying here instead of the DOOM Eternal thread because that is getting pretty off topic for the actual game.
As I understand it, gamemode tries to "be smart" and set different things for different games. So breaking only one title makes sense.
There was a bug when Proton 8 released that caused Sniper to not always install when Proton 8 was first launched on a system. So likely you ran into that bug, and eventually a couple of Steam Client reboots fixed the issue, at which point Sniper got correctly downloaded and you started hitting the incompatibility with MangoHud.
I saw your comment here and on the other thread about DLSS - this hasn't been broadly reported as far as I know so it could be another problem with your system, but I have it on a list to look into.
I saw your comment here and on the other thread about DLSS - this hasn't been broadly reported as far as I know so it could be another problem with your system, but I have it on a list to look into.
I'm not sure what could be wrong with my system, since:
PROTON_ENABLE_NVAPI= PROTON_HIDE_NVIDIA_GPU=0 %command%`This definitely seems like a Sniper Runtime issue, since that's the only variable changing between working DLSS and breaking DLSS. But anyway, I'll see if I can get some logs from a couple Steam games with PROTON_LOG=1 and DXVK_NVAPI_LOG_LEVEL=info to see if DXVK_NVAPI is even being loaded in DX12 games, even though the bug appears in all titles, Vulkan or DX12.
You're right though, I'm off-topic with this issue, so I'll post a separate one with the logs and all information I can grab when I can get it all together. Oh, and I do indeed have a separate Manjaro install and a Pop OS install on separate partitions in addition to my daily driver vanilla Arch install, with their own ~/.config partitions, the only thing they share is $HOME and game library partitions, which will show if the issue is in Steam or not, so I'll update those installs and get everything as apples-to-apples as I can and see if the issue persists. I wouldn't be surprised if people aren't reporting this because they don't even notice, because MangoHud doesn't work, so unless they enable the fps counter in the steam overlay they won't even know they're getting lower fps in a game they already had installed, and most people don't go into their settings every time they launch a game.
DLSS is fixed, that one actually was a weird configuration issue that only
actually affected DLSS working in SOME games and no others (which is why I
didn't think it could be a config issue). It works in Dead Space Remake and
Dying Light 2 and everything else now.
On Tue, May 23, 2023 at 9:50 AM alasky17 @.***> wrote:
@gardotd426 https://github.com/gardotd426 Replying here instead of the
DOOM Eternal thread because that is getting pretty off topic for the actual
game.
As I understand it, gamemode tries to "be smart" and set different things
for different games. So breaking only one title makes sense.There was a bug when Proton 8 released that caused Sniper to not always
install when Proton 8 was first launched on a system. So likely you ran
into that bug, and eventually a couple of Steam Client reboots fixed the
issue, at which point Sniper got correctly downloaded and you started
hitting the incompatibility with MangoHud.I saw your comment here and on the other thread about DLSS - this hasn't
been broadly reported as far as I know so it could be another problem with
your system, but I have it on a list to look into.—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/6763#issuecomment-1559416913,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33YHMXE3TU756NJ7MJ3XHS6AVANCNFSM6AAAAAAX5I64XU
.
You are receiving this because you were mentioned.Message ID:
@.***>
Actually everything is fixed, the performance issue in Doom Eternal too, the only problem is that the solution makes zero sense. I've already explained that in the Doom Eternal thread, though, so I won't post it again here so I'm not spamming up the threads.
But @demanuPL the MangoHud folks are looking into their part in the Sniper Runtime issue right now, you said you're on AMD, can you confirm whether MANGOHUD=1 %command% was your problem or whether it is something else?
proton experimentalx1 2023-05MANGOHUD=1x1 2023-06DXVK_NVAPIx1 2023-05DXVK_NVAPI_LOG_LEVEL=info`x1 2023-05PROTON_ENABLE_NVAPI=`x1 2023-05PROTON_HIDE_NVIDIA_GPU=0x1 2023-05PROTON_LOG=1`x1 2023-05PROTON_LOG=1x1 2023-05MANGOHUD=1 %command%x1 2023-06PROTON_ENABLE_NVAPI=` PROTON_HIDE_NVIDIA_GPU=0 %command%x1 2023-05
After installing proton 8 none of games are working, also proton experimental doesnt work. I've tried all of my games and none on them even started. Problem is with AMD gpus with latest mesa. Works fine on all versions of 7 and below.
I've found this in logs:
2858.735:0210:0214:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FEB0 gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory pid 14988 != 14987, skipping destruction (fork without exec?)But I didnt add game mode to launch options