You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Steam Deck installation instructions mention that ProtonUp-QT will add steamtinkerlaunch to PATH for you, but the instructions to install without ProtonUp-QT don't mention adding it to PATH. The instructions direct you to do something that will not work, because steamtinkerlaunch isn't in PATH.
From here, you can run ./steamtinkerlaunch. You can simply type ./steamt and press "Tab" to autocomplete (either with a physical keyboard or your on-screen keyboard)
Wait for the script to finish, and then run steamtinkerlaunch compat add to ensure SteamTinkerLaunch is added as a compatibility tool in Steam.
Without adding it to PATH after step 5, step 6 will fail as command not found.
The text was updated successfully, but these errors were encountered:
Steps 5 and 6 are intended to be ran from the directory of the SteamTinkerLaunch, as made obvious by the ./steamtinkerlaunch - ./steamtinkerlaunch will fail regardless of whether SteamTinkerLaunch is in your PATH or not with a file not found error because there's no script to execute with ./. Though Step 6 on the wiki forgets the ./, I will fix that after this post. In general, this will work.
The steps for a manual non-root install explain how to add SteamTinkerLaunch to PATH, so I will update the wiki to direct users to that.
Also, if you missed it, there is a dedicated issue for suggesting improvements to the wiki: #457.
The Steam Deck installation instructions mention that ProtonUp-QT will add steamtinkerlaunch to PATH for you, but the instructions to install without ProtonUp-QT don't mention adding it to PATH. The instructions direct you to do something that will not work, because steamtinkerlaunch isn't in PATH.
Without adding it to PATH after step 5, step 6 will fail as
command not found.
The text was updated successfully, but these errors were encountered: