Closed DVN196 closed 2 days ago
Were you able to resolve this? I am not seeing anything sticking out from the log, but if you got it resolved a comment on how you did it could help others in future :-)
If you still need help, feel free to re-open. You might also want to open an issue over on the Flathub repo. Flatpak SteamTinkerLaunch's packaging is maintained separately to this repo (dependencies, installation, etc), although the code that checks for and makes adjustments to work around Flatpak limitations is in the codebase here. So the Flatpak isn't a separate SteamTinkerLaunch project but does have so e quirks that may need to be raised over on the Flathub repo sometimes.
Sorry, after I submitted the issue. Suddenly it work, but now it doesn't work again.
I met these issues:
It seems I cannot re-open the issue
I cannot launch STL when I enabled Cloudflare Warp (I think it is network issue? Does STL fetch anything on startup?)
STL does try to download some things, but nothing that should prevent startup. Check the log file for more information on a failed run but some people using exotic network configurations have issues accessing GitHub via scripts in general including with SteamTinkerLaunch.
If you want to attach the log, please do so by attaching it as a file and not by pasting text.
Right now I cannot fork custom command (textractor.exe): Yesterday, it works, I just need to enable "Keep STL open".
It sounds like a Wine issue more than anything else. In the vast majority of cases, issues with custom commands are caused by Wine/Proton compatibility issues or configuration issues.
You can optionally try disabling using the Steam Linux Runtime with your Custom Command, or alternatively if you do not have the Steam Linux Runtime required by the Proton version you are using, you can install it. There is a button on the Main Menu that will send the download request for the relevant Steam Linux Runtime AppID. Due to Steam limitations this cannot be done silently, so after clicking the button on the Main Menu you will have to follow the prompt inside of Steam to install it.
Today, it is not very stable. When I open the game, sometimes it only shows the custom program and STL menu, sometimes it only shows STL menu and the game
It should never show SteamTinkerLaunch and the Custom Command or SteamTinkerLaunch and the game together. There is never a case where this should happen.
If you are having issues getting your game and the custom command to run together, you can try using Fork OR Inject, and adjusting the delay for each - You cannot use both together, but the delay will control when the game/custom command starts, as sometimes you need one to start before the other.
On SteamOS Valve are very restrictive about multiple processes running in the same prefix, but historically this has not applied to the Linux Desktop, and doesn't apply to the native Steam Client on Arch Linux as of a couple days ago (I have ran custom commands and games together with the fork option).
It seems I cannot re-open the issue
This is because the account you replied with is different from the account you opened the issue with. :slightly_smiling_face:
Given that things are playing up for you, this seems like a system issue. Some users have had bad installs of the Steam Flatpak (given that it is not maintained or supported by Valve) that have resulted in various issues with and without SteamTinkerLaunch.
I am more inclined to say this is a system issue / Wine issue more than a SteamTinkerLaunch issue because I don't see why things would be this flaky...
System Information
Issue Description
I am migrating from native steam to flatpak. I installed steam and add my existing games library. I installed STL flatpak. Opening games with STL, nothing appear (Only the notification for first time launch), Steam indicates that the game is running. Without STL, games run normally
Logs