-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not function, game hangs on launching and then closes #1147
Comments
Before reading on, you're using a very outdated version of SteamTinkerLaunch (about 16 months behind). Please do not use SteamTinkerLaunch releases and instead use SteamTinkerLaunch from master. You can install this from ProtonUp-Qt in Advanced Mode, as per the wiki page. Yad works fine here but maybe there's a Yad issue on Debian? Have you only tried using SteamTinkerLaunch from Steam? Try running SteamTinkerLaunch from the commandline and seeing if there's any notable output. You can try You might also want to try running Steam from the commandline. One user reported an issue with one specific game in #357, and it seems like a Yad issue (returned code SteamTinkerLaunch is working fine over here on Arch Linux ( If you are trying to use SteamTinkerLaunch as a launch option (which, as noted on the Readme and Steam Launch Option wiki page, is only for native games), when installed via ProtonUp-Qt you must pass the full path because Steam does not see user-added PATH variables, as documented on the ProtonUp-Qt wiki page and this is also mentioned on both the linked Readme section and Steam Launch Option wiki page. Not sure if relevant, but it seems a while back there was an issue where Yad failed to compile on Debian 12 due to an outdated glibc version, unsure if this would affect running it though (I imagine not but linking anyway): v1cont/yad#269 |
Okay, I believe the issue was in fact Yad not working correctly, I installed pacstall and downloaded stl + yad from there and now it seems to be functioning correctly and the correct version of SteamTinkerLaunch, however it still doesn't seem to be opening with any games when set as a compatibility tool, it will show "running" for a couple seconds and then close. I can now also produce a log. |
Yeah, it does sound like the initial issue was related to Yad. Might be worth reporting upstream if Yad standalone did not work. The Yad AppImage that you can install from SteamTinkerLaunch with Although note that the Yad AppImage is unofficially built and is not supported by Yad upstream. Issues should only be reported if standalone Yad fails to work outside of SteamTinkerLaunch. Just to prevent any noise upstream :-) This issue now is probably because your Steam Library folder path contains Your Steam root library folder path contains a lowercase SteamTinkerLaunch does not attempt to start the game because it does not see a valid incoming start command, since the path does not include a known location like
The check for We can make this check case insensitive with a Note that symlinking will probably not work because Steam passes the resolved symlink path to compatibility tools, SteamTinkerLaunch never gets to see the symlinked path (see also #1132). So the only solution is to use a libraryfolder that doesn't have a capitalized Out of interest, are any other folder names in your |
Oh my god, hero, it was in fact the capitalization, I have absolutely no idea why steam created it with a capital, I recently formatted the drive for steam games exclusively and it is the only part of the directory that was capitalized, very strange, thanks a lot though! |
No problem! I will close this issue now that this is resolved :-) Out of interest, if you change the name of the directory to have a lowercase |
System Information
Issue Description
Pressing launch shows the game opening, and then instantly closes, does not produce any logs, reinstalled multiple times and cannot for the life of me figure it out, unless I'm just really stupid. All listed dependencies installed, possibly YAD issue? Currently 14.1 (GTK+ 3.24.38)
The text was updated successfully, but these errors were encountered: