Closed jimmon89 closed 1 year ago
It looks like the game isn't being launched via proton. The launcher parses the args that steam provides in order to determine how to launch proton.
I noticed a couple things about your config:
soldier
path in your arguments which is the container steam uses for proton starting at version 5.13. Have you disabled that? Normally, there'd be a few extra args, one of which being /home/<user>/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/_v2-entry-point
/usr/share/steam/compatibilitytools.d/proton-ge-custom/proton
. The launcher is currently case-sensitive when it checks for not running via soldier. I think it would work if your path were /usr/share/Steam/compatibilitytools.d/Proton-ge-custom/proton
instead. I'll add case-insensitivity to my todo list.It looks like the game isn't being launched via proton. The launcher parses the args that steam provides in order to determine how to launch proton.
I noticed a couple things about your config:
- There's no
soldier
path in your arguments which is the container steam uses for proton starting at version 5.13. Have you disabled that? Normally, there'd be a few extra args, one of which being/home/<user>/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/_v2-entry-point
- You're using a non-standard path name for proton
/usr/share/steam/compatibilitytools.d/proton-ge-custom/proton
. The launcher is currently case-sensitive when it checks for not running via soldier. I think it would work if your path were/usr/share/Steam/compatibilitytools.d/Proton-ge-custom/proton
instead. I'll add case-insensitivity to my todo list.
To test, i renamed /usr/share/steam/compatibilitytools.d/proton-ge-custom/
to /usr/share/Steam/compatibilitytools.d/Proton-ge-custom/
as you suggested, but nothing changed.
so i manually downloaded the non-AUR archive from glorious eggrolls github and extracted it to /home/<snip user>/.local/share/Steam/compatibilitytools.d
and it worked, complete with loading SteamLinuxRuntime_soldier as you mentioned
i tried copying /usr/share/Steam/compatibilitytools.d/Proton-ge-custom/
to /home/<snip user>/.local/share/Steam/compatibilitytools.d/Proton-ge-custom/
and when i copied the AUR package to my user directories compatibilitytools.d folder it had the same issue as it did in the /usr/share/ compatibilitytools.d directory
so i downloaded the actual AUR proton-ge-custom-bin package instead of the Chaotic-AUR package to see if there is a difference and the actual AUR package works, meaning the problem is with the chaotic-aur package
It was caused by the chaotic-aur version of proton-ge-custom-bin Use the actual AUR version, it works as expected. it's not an issue with min-ed-launcher
Describe the bug/error On Arch Linux, When i try to launch the game using min-ed-launcher it opens a fairly small window compared to my native 1080p that closes on its own a few seconds. the game as a whole never actually starts unless i use the one from the actual game the window is completely black and is named
Elite - Dangerous (Client)
Steam Version of Odyssey Proton Version: (GE-Proton7-49) Launch Options:Also tried with Konsole to the same effect
Debug log
settings.json
Log journal from black screen indecent
Log journal from vanilla launcher went to main menu then exited manually