Whenever we use ReShade Deployer it symlinks the reshade dlls and hard copies/creates the default ReShade files.
I was thinking that instead of copying/creating the files, have said files inside a folder of ReShade Deployer (p.e. "Presets") and then symlink then to the game. This way we have all presets on a single location and our games a little cleaner. It's also easier to backup our carefully made presets.
The only problem would be on creating said folders, what name does the program pick. Creating the folder from the exe name seems logical, but what happens when two games use the same .exe name?
I think adding an adding an extra optional step, a checkmark and title below "Add-on Support", with a text field below it should do it, I think.
sorry for the very crude mockup, I'm using W11s snipping tool
(also, as a small nitpick, I think the "to" in the "Deploy to Game" button shouldn't be capitalized but that's just me)
Whenever we use ReShade Deployer it symlinks the reshade dlls and hard copies/creates the default ReShade files.
I was thinking that instead of copying/creating the files, have said files inside a folder of ReShade Deployer (p.e. "Presets") and then symlink then to the game. This way we have all presets on a single location and our games a little cleaner. It's also easier to backup our carefully made presets.
The only problem would be on creating said folders, what name does the program pick. Creating the folder from the exe name seems logical, but what happens when two games use the same .exe name?
I think adding an adding an extra optional step, a checkmark and title below "Add-on Support", with a text field below it should do it, I think.
sorry for the very crude mockup, I'm using W11s snipping tool
(also, as a small nitpick, I think the "to" in the "Deploy to Game" button shouldn't be capitalized but that's just me)