Steam Collections

Steam Collections

simply enable different features by simply dragging the game into the corresponding Steam Collection

steamtinkerlaunch parses the Steam collections of the started game and examines if a associated steamtinkerlaunch configuration file exists under the same name (case-sensitive, but written uppercase in Steam !)

If a configuration file is found it is initialized as additional config file.

This makes it easy to create "Configuration collections" by

• simply creating a Steam Collection
• creating a collections configfile under the same name and defining settings in it
• adding a game to the collection to use those settings automatically

Collection Configuration Files are searched in the User Configurations STLCOLLECTIONDIR (STLCFGDIR/collections) or in the system-wide dir GLOBALCOLLECTIONDIR (SYSTEMSTLCFGDIR/collections)

where some collection files are already preconfigured (list might not always be up to date):

• Backup the SteamUser files are automatically stored in the Backup
• BlockInternet game is started with access to the internet blocked [Block Internet](https://github.com/frostworx/steamtinkerlaunch/wiki/Block Internet)
• Conty Conty container is used to start a 32bit game
• DLSS DLSS enable all required options required for DLSS
• DelCompat delete compatdata before game launch
• Dependencies game is automatically started with the debugging tool Dependencies-Program
• DOSBox game is started automatically with linux native dosbox provided by Boxtron
• FSR the game is started with enabled FidelityFX SuperResolution ([FSR](Wine FSR)) support
• FWS the game is started automatically with FlawlessWidescreen support
• GDB game is started automatically with the debugger Gdb
• Geo11 the game is automatically started using Geo11
• Geo11-VR the game is automatically started in Side by Side VR using Geo11
• Luxtorpeda game is started automatically with linux native binary provided by Luxtorpeda
• MangoHud enable MangoHud for the game
• MangoHudCfg enable MangoHud for the game and use the steamtinkerlaunch internal MangoHud config
• MangoApp enable MangoApp for the game
• MO2 start Mod-Organizer 2 before starting the (supported) game
• OpenVR-FSR enable automatically OpenVR-FSR for the game. (apparently without effect, if the game doesn't use openvr)
• PEV use all supported PEV - PE32 file analysis tools on the game exe
• Raytracing enable automatically all options required for Raytracing
• Regedit the Registry can be edited on game start easily
• ReShade game is started automatically using ReShade
• ReShadeVR game is started automatically in SBS-VR mode using ReShade
• SBS-VR game is started automatically in SBS-VR mode without Shader (for games with built-in Stereoscopic3D support)
• ScummVM game is started automatically with linux native scummvm provided by Roberta
• SortGameArgs unlock Game-Command-Line-Arguments
• SpecialK game is started automatically using SpecialK if available/downloadable
• Vortex game is started automatically with the Vortex Mod Manager
• Wine game is started using Wine instead of Proton
• Wineconsole a Wineconsole is opened instead of the game
• x64dbg game is started automatically with the debugger X64dbg
• Zink OpenGL game is started automatically using Zink Zink

Multiple Collection Configuration Files are possible, they are loaded one after another, with the last one overriding settings also found in the previous files. All settings which are also configured in $STLGAMECFG are overridden (but not overwritten).

The function can be diabled per game with the option CHECKCOLLECTIONS in the Game Menu

The same function also checks if a script with the same name (".sh" suffix expected) as the Steam collection is in the global GLOBALTWEAKCMDDIR and in the user TWEAKCMDDIR. When found it is executed before the game with the following 3 commandline parameters

1. SteamAppID
2. Game directory
3. Game Wineprefix

(of course the script should not block the actual game start, and it is up to the user what is actually executed in the script)