You are not logged in.
Pages: 1
I have been browsing forums and wiki for a week but nothing helped me, the native games are smooth af but the proton games get stuck at preparing to launch and it stays like that. Although after i reinstalled everything (literally), the games crash but the native games still work fine.
i have tried mirror's edge catalyst and warframe
here is what i have tried...
1. using dmesg
2. deleting steam and its cache and everything
3. downloading vulkan
4. whatever i found on reddit and forum
here is dmesg: http://ix.io/3AzZ
here is steam log for warframe (http://ix.io/3AGD)
i have noticed that the game isn't downloading its vulkan shader package (not sure what the official name is)
before it used to download it but it doesn't work
and also i am using the lts kernel
i uninstalled steam, removed all the cache and reinstalled it and i found something in dmesg that might be something......
http://ix.io/3AF7
in the last few lines there were few errors i saw after the game crashed
[ 5090.042039] ACPI Error: Thread 1012620736 cannot release Mutex [ECMX] acquired by thread 1040997824 (20200925/exmutex-378)
[ 5090.042057] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200925/psparse-529)
[ 8128.400585] ACPI Error: Thread 2184675328 cannot release Mutex [ECMX] acquired by thread 2661801408 (20200925/exmutex-378)
[ 8128.400597] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_AML_NOT_OWNER) (20200925/psparse-529)
[11246.468202] fossilize_repla[5973]: segfault at 56240d0da240 ip 00007fa64aded569 sp 00007ffea2715180 error 4 in libGLX_nvidia.so.470.74[7fa64ada0000+b2000]
SOLUTION: today after i restarted my lappy and updated the system, warframe started working (with proton version 6.3 and experimental too) smooth as usual, its weird but started working so, thank you everyone for the help
Last edited by kashishme (2021-10-05 04:08:39)
Offline
Steam being proprietary software, you would be better served at the source
https://github.com/ValveSoftware/steam-for-linux/issues
It's probably not a Proton issue, because you're not even getting to the point where it gets invoked at all. So it's probably not a steam-runtime issue either.
Of course, if I'm wrong, they'll just transfer your issue to the correct repo, so no harm done.
Offline
Steam being proprietary software, you would be better served at the source
https://github.com/ValveSoftware/steam-for-linux/issues
It's probably not a Proton issue, because you're not even getting to the point where it gets invoked at all. So it's probably not a steam-runtime issue either.
Of course, if I'm wrong, they'll just transfer your issue to the correct repo, so no harm done.
and also, how do i fix the curl command so i could upload it on official steam page? is it that the log file is too big?(because it is huge tbh)
Offline
If the games are on an NTFS drive, try to remount it a few times (... easiest done with
systemctl restart $mountpoint$.mount
) see https://github.com/ValveSoftware/Proton/issues/5068 for some discussion around this.
As for getting the curl command to work, which command are you trying to use exactly and what's the error message you get? In general I'd assume these suggestions are based on bash so could just run that command through bash instead if it's some keyword/logic issue
Last edited by V1del (2021-10-02 16:22:55)
Offline
If the games are on an NTFS drive, try to remount it a few times (... easiest done with
systemctl restart $mountpoint$.mount
) see https://github.com/ValveSoftware/Proton/issues/5068 for some discussion around this.
As for getting the curl command to work, which command are you trying to use exactly and what's the error message you get? In general I'd assume these suggestions are based on bash so could just run that command through bash instead if it's some keyword/logic issue
i am using ext4 partition
and as for the command i think its because of the big size of the log so i will try copying things here
Last edited by kashishme (2021-10-03 04:21:49)
Offline
What exactly are you trying to upload? For basic debugging the log you get in your $HOME when adding
PROTON_LOG=1 %command%
to the game's launch options should contain everything of relevance and shouldn't be that big
Offline
What exactly are you trying to upload? For basic debugging the log you get in your $HOME when adding
PROTON_LOG=1 %command%
to the game's launch options should contain everything of relevance and shouldn't be that big
i tried to get the log again, and this time it worked for some reason, i don't really see anything for some reason but here is the log, last time it was too big
http://ix.io/3AGD
Offline
That's just the generic header line and no actual log information. Only suggestion I have based on this try other games and potentially proton 6.3 rather than the experimental branch
Offline
That's just the generic header line and no actual log information. Only suggestion I have based on this try other games and potentially proton 6.3 rather than the experimental branch
i changed the proton version to 6.3 and something did show up (http://ix.io/3AH4)
btw a note that it did not crash but neither did it launch, but steam shows its still running
Last edited by kashishme (2021-10-03 14:46:49)
Offline
Try moving compatdata folder elsewhere and let it re-generate the prefix? It's saying c:\windows within the prefix is not found. It doesn't really make sense because it's looking for "c:" when the folder name is usually meant to be "drive_c", which is probably why it's not finding it? Different path, disregard. That should be a symlink to drive_c. Doesn't explain why that path is not found, though. Does the symlink correctly point to ../drive_c?
Although, the error could be happening at any point within that path, so it's not necessarily an issue with the prefix. Fucky stuff can happen sometimes when you try to reuse the same prefix across different Proton versions though, especially if downgrading from a newer version back to an older version. When in doubt move your prefixes and let it generate new ones. You can move config files and save data and stuff from the old prefixes back to the new prefixes afterwards.
Last edited by Ammako (2021-10-05 00:25:53)
Offline
Try moving compatdata folder elsewhere and let it re-generate the prefix? It's saying c:\windows within the prefix is not found. It doesn't really make sense because it's looking for "c:" when the folder name is usually meant to be "drive_c", which is probably why it's not finding it? Different path, disregard. That should be a symlink to drive_c. Doesn't explain why that path is not found, though. Does the symlink correctly point to ../drive_c?
Although, the error could be happening at any point within that path, so it's not necessarily an issue with the prefix. Fucky stuff can happen sometimes when you try to reuse the same prefix across different Proton versions though, especially if downgrading from a newer version back to an older version. When in doubt move your prefixes and let it generate new ones. You can move config files and save data and stuff from the old prefixes back to the new prefixes afterwards.
I kinda understand it, but how do i do it, changing the prefixes?
Offline
Steam put the prefixes for games in a folder with name compatdata. The default path for this folder is ~/.steam/steam/steamapps/compatdata. In this folder there are other folders, each for every game and have as name the id of the game(which is a number). In every of those folders(depends of the games you have that use proton). there is a pfx folder. This folder is the prefix. If you delete a game id folder, then steam will recreate the prefix when you run the game.
Offline
So... What was the solution kashishme?
Offline
Pages: 1