[Solved]Proton games don't work

[JustCauseWhyNot]

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.

[rab0171610]

Could you please post your

Code: Select all

emerge --info

and

Code: Select all

equery h abi_x86_32

[Ionen]

Code: Select all

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.

[keet]

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.

[JustCauseWhyNot]

Could you please post your

Code: Select all

emerge --info

and

Code: Select all

equery h abi_x86_32

Here's my emerge --info, and equery h abi_x86_32

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

have you ruled out whether this is 32bit or 64bit specific?

No I've not. Each exe that I've ran

Code: Select all

file

on has given this output

Code: Select all

.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: Select all

.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

Also is this nvidia-only

Yes it is.

[JustCauseWhyNot]

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: Select all

PROTON_LOG=1 ENABLE_VKBASALT=0 WINEDEBUG=-all %command%

.

Any ideas, or help is very much appreciated.

[JustCauseWhyNot]

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.

[Ralphred]

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.

[JustCauseWhyNot]

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.

[ritzmax72]

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.

I have 2070s as well and hate to switch to Windows just to play Squad. Squad recently started running well on Windows. I guess the team did some optimizations but it fails on Linux. So disappointing.

[JustCauseWhyNot]

Squads not running on linux atm any ways due to eac issues with updated glibc. Also did you try squad in dx12 through proton? For some reason it runs much better in my experience.

[papu]

I recenly get and eac update from a game and it works , glibc has an option for eac
https://i.imgur.com/NdoYi4d.jpg

[JustCauseWhyNot]

It was a squad issue at the time that required them to update their eac iirc. It was fixed a couple days or like a week later after my post.

[papu]

It was a squad issue at the time that required them to update their eac iirc. It was fixed a couple days or like a week later after my post.

ok, I have some questions:

do you have hash-sysv-compat active on glibc? how many of your games withe eac are working with gentoo and proton?

thanks

[JustCauseWhyNot]

I do have that flag. And recenctly I've not been playing multiplayer, and those that I have been playing have worked. Such as native warthunder. It uses eac, but I'm not sure how much the native version does use eac as there is little evidence of it running.

[papu]

I do have that flag. And recenctly I've not been playing multiplayer, and those that I have been playing have worked. Such as native warthunder. It uses eac, but I'm not sure how much the native version does use eac as there is little evidence of it running.

ok, thanks