| View previous topic :: View next topic |
| Author |
Message |
JustCauseWhyNot
Tux's lil' helper
Joined: 07 Dec 2021
Posts: 131
|
 Posted: Thu May 09, 2024 4:36 am Post subject: [Solved}Proton games don't work |
 |
|
I can launch proton games, but they then just chug at 1 frame every 10s. I don't get what the problem is. I've got a rtx 4070 super, and 7800x3d that run native games perfectly fine. It's just when using proton that it doesn't work. I've tried proton-ge-9.2/9.4, and normal proton-9.0-1/8.0-5. Here's my steam runtime, and steam-236390.log. I've tested more than just warthunder. I've also tested hell let loose, and squad. They both have the same issues. And yes my nvidia drivers are built with abi_x86_32.
Any help would be very much appreciate, thank you.
Solved: This issue was what I was suffering from.
Last edited by JustCauseWhyNot on Thu May 16, 2024 4:27 pm; edited 1 time in total |
|
| Back to top |
|
 |
rab0171610
Guru
Joined: 24 Dec 2022
Posts: 307
|
| Posted: Thu May 09, 2024 5:14 am Post subject: |
|
|
Could you please post your and
| Code: | | equery h abi_x86_32 |
|
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2727
|
| Posted: Thu May 09, 2024 12:30 pm Post subject: |
|
|
| Code: | | 37938.451:0060:006c:trace:... |
Any idea how you got tracing enabled? This makes wine extremely slow, or did you only enable it for the sake of logs?
WINEDEBUG=all would cause that for one, just unset it to use defaults.
If was only for logs and it's still slow without, have you ruled out whether this is 32bit or 64bit specific? (I'm not sure what these games are using, can run file(1) on the executable to figure it out though)
If 32bit, may want to try to emerge mesa-progs and vulkan-tools[cube] with USE=abi_x86_32, gives you some simple 32bit test applications and may help debugging. Also is this nvidia-only or intel/amd+nvidia? If the latter, may need USE=abi_x86_32 on mesa too and not just nvidia-drivers. |
|
| Back to top |
|
|
keet
Guru
Joined: 09 Sep 2008
Posts: 571
|
| Posted: Thu May 09, 2024 1:14 pm Post subject: Re: Proton games don't work |
|
|
Squad ran horribly on my 2070S, no matter what I tried (though other games generally worked well). Just to rule out my distribution and configuration, I also tried Arch and Manjaro and had the same problem.
Since I switched to a Radeon card, it's worked great. |
|
| Back to top |
|
|
JustCauseWhyNot
Tux's lil' helper
Joined: 07 Dec 2021
Posts: 131
|
| Posted: Thu May 09, 2024 3:34 pm Post subject: |
|
|
| Quote: | Could you please post your and | Code: | | equery h abi_x86_32 |
|
Here's my emerge --info, and equery h abi_x86_32
| Quote: | | Any idea how you got tracing enabled? |
Not a clue. I've gotten it disabled, and it's still very slow. It's possibly a tiny bit better, but it's hard to tell. Here's the an updated steam-236390.log | Quote: | | have you ruled out whether this is 32bit or 64bit specific? |
No I've not. Each exe that I've ran on has given this output | Code: | | .local/share/Steam/steamapps/common/Counter-Strike Global Offensive/game/bin/win64/cs2.exe: PE32+ executable (GUI) x86-64, for MS Windows, 7 sections |
The only difference between the exe's have been the number of sections. Such as warthunder being | Code: | | .local/share/Steam/steamapps/common/War Thunder/win64/aces.exe: PE32+ executable (GUI) x86-64, for MS Windows, 11 sections |
and the rest being 7 like cs2. The native linux bins have been 64 bit versus PE32+. I also wanna note that while playing cs2 just now through proton it actually ran fairly well in game. But initial loading was a bit slow like the other titles, and when I made a graphics setting change it caused cs2 to shit out like the rest. Here's it's steam-730.log
| Quote: | | Also is this nvidia-only |
Yes it is. |
|
| Back to top |
|
|
JustCauseWhyNot
Tux's lil' helper
Joined: 07 Dec 2021
Posts: 131
|
| Posted: Sun May 12, 2024 2:17 am Post subject: |
|
|
I've done a lot of system updating, but everything's still broken. Here's my steam-236390.log, and steam-runtime. I'm also using these launch options | Code: | | PROTON_LOG=1 ENABLE_VKBASALT=0 WINEDEBUG=-all %command% |
.
Any ideas, or help is very much appreciated. |
|
| Back to top |
|
|
JustCauseWhyNot
Tux's lil' helper
Joined: 07 Dec 2021
Posts: 131
|
| Posted: Tue May 14, 2024 8:58 pm Post subject: |
|
|
| I found it's not a wine issue. I emerged wine-proton, and it ran what I wanted without issue. I know now it's either a steam, or proton issue. |
|
| Back to top |
|
|
Ralphred
Guru
Joined: 31 Dec 2013
Posts: 506
|
| Posted: Wed May 15, 2024 11:21 am Post subject: |
|
|
| JustCauseWhyNot wrote: | | I know now it's either a steam, or proton issue. |
There has been quite a bit of "nvidia related noise" on protondb.com regarding launch settings; I'd check out a few newer games and see what launch settings people are using - some of these settings are a "proton thing" and not a "game thing" too, so it's also worth having a few older versions of GE-Proton around too, 7.37 and 8.21 are a couple of my go to versions. |
|
| Back to top |
|
|
JustCauseWhyNot
Tux's lil' helper
Joined: 07 Dec 2021
Posts: 131
|
| Posted: Thu May 16, 2024 3:59 pm Post subject: |
|
|
| Quote: | | it's also worth having a few older versions of GE-Proton around too, 7.37 and 8.21 are a couple of my go to versions. |
Is there a particular reason as to why these specific ones? Idk how you're managing your proton instances, but I like installing with portage, and there aren't any public 7.37 proton-ge ebuilds. |
|
| Back to top |
|
|
|
Gamers & Players
