> @kodatarule > It's okay I tried that one as well as per protondb.com > It must be an amd thing... > Oh well I'll wait for protondb.com to show someone with an d card running it Can you generate a log ? PROTON_LOG=1 %co...
@kodatarule It's okay I tried that one as well as per protondb.com It must be an amd thing... Oh well I'll wait for protondb.com to show someone with an d card running it
> @kodatarule ty for the reply... > i tried > PROTON_NO_ESYNC=1 %command% > and it didnt work > apparently i am doing something wrong because i cant get it to run > im running vanilla manjaro kde with 5.11 kernal and amd...
@kodatarule ty for the reply... i tried PROTON_NO_ESYNC=1 %command% and it didnt work apparently i am doing something wrong because i cant get it to run im running vanilla manjaro kde with 5.11 kernal and amd card it see...
@Cytomax55 You need kernel compatible with futex2 and then just use proton-experimental, if you don't know how to do that try running with esync. So in your case PROTON_NO_ESYNC=1 %command% to the launch options.
@kodatarule I am running manjaro with latest kernel 5.11.2-1 How did you enable futex2 to get 30xx working? I am also running AMD 5700XT with mesa drivers Thanks in Advance
UPDATE2: Sorry for the triple post. The game seems to be working just fine with futex2, but fsync1 seems to cause it to crash to desktop once you click play. Using proton-experimental and kernel with futex2.
UPDATE: Thanks to a recommendation from user ZereoX to disable fsync( PROTON_NO_FSYNC=1 %command% ) the game works just fine. So there is only issue with fsync.