I found a workaround - a rather complex one - in which you have to create duplicates of your SYSCONF and Dolphin.ini files and name the duplicates for the files you're trying to load. Then you run a batch file and pass an argument to it which temporarily renames your defaults, renames the custom settings to the defaults, loads Dolphin with the file you choose from a preset directory, and then renames them all back after the program closes. Put the batch folder in your main directory.
So, if you're loading "C:\PATH\TO\ROMS\007GoldenEye.iso", you create the two following files:
User\Config\Dolphin.007Goldeneye.iso.ini
User\Wii\shared2\sys\007Goldeneye.iso.SYSCONF
Then, you'd run the command (or create a shortcut with the command):
Dolphin.bat "007GoldenEye.iso"
You'd have to exit out of the game and set your settings the way you want them for that game (or change the settings before you make the duplicate files), and the next time you run it from the batch file, those settings will be automatically loaded.
And, if you don't like batch windows, you can create an additional .vbs which loads the .bat in a windowless environment.
Instead, you run:
Dolphin.vbs "007Goldeneye.iso"
Make sure to use the quotes, just in case you have files with spaces in the names. The only real drawback is having to make the duplicate settings files for every game, and if you suddenly lose power in the middle of a game, you'll have to manually rename them back since the batch file won't have the chance. But if Dolphin were to suddenly crash, they should still be fine since the batch file would continue to run.
Also, you'll have to create more than one set of batch/vbs files if you keep your games in different directories.
Code:
rename "User\Config\Dolphin.ini" "Dolphin.DEFAULT.ini"
rename "User\Config\Dolphin.%~1.ini" "Dolphin.ini"
rename "User\Wii\shared2\sys\SYSCONF" "SYSCONF.DEFAULT"
rename "User\Wii\shared2\sys\%~1.SYSCONF" "SYSCONF"
Dolphin.exe /e "C:\PATH\TO\ROMS\%~1"
rename "User\Config\Dolphin.ini" "Dolphin.%~1.ini"
rename "User\Config\Dolphin.DEFAULT.ini" "Dolphin.ini"
rename "User\Wii\shared2\sys\SYSCONF" "%~1.SYSCONF"
rename "User\Wii\shared2\sys\SYSCONF.DEFAULT" "SYSCONF"So, if you're loading "C:\PATH\TO\ROMS\007GoldenEye.iso", you create the two following files:
User\Config\Dolphin.007Goldeneye.iso.ini
User\Wii\shared2\sys\007Goldeneye.iso.SYSCONF
Then, you'd run the command (or create a shortcut with the command):
Dolphin.bat "007GoldenEye.iso"
You'd have to exit out of the game and set your settings the way you want them for that game (or change the settings before you make the duplicate files), and the next time you run it from the batch file, those settings will be automatically loaded.
And, if you don't like batch windows, you can create an additional .vbs which loads the .bat in a windowless environment.
Code:
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run Chr(34) & "Dolphin.bat" & Chr(34) & Chr(34) & WScript.Arguments(0) & Chr(34), 0
Set WshShell = NothingInstead, you run:
Dolphin.vbs "007Goldeneye.iso"
Make sure to use the quotes, just in case you have files with spaces in the names. The only real drawback is having to make the duplicate settings files for every game, and if you suddenly lose power in the middle of a game, you'll have to manually rename them back since the batch file won't have the chance. But if Dolphin were to suddenly crash, they should still be fine since the batch file would continue to run.
Also, you'll have to create more than one set of batch/vbs files if you keep your games in different directories.