Hi,
Do a lot of zdoom/gzdoom users here use zdl? I want to set up multiple config files for pwads and megawads that have extra settings, so they don't conflict with each other when configuring them. I know i can copy gzdoom to every mod folder and load them separately, but that doesn't seem to be the most efficient way to do it. If i play a weapon mod that has extra configurable controls and then play a different weapon mod or just vanilla wads; all of the settings get written into the default ini file and makes things messy. Somewhere i've seen users using -config filepath\gzdoom-username.ini in the Extra command line argument of ZDL, but the results were confusing.
Loading gzdoom config file with zdl
Moderators: GZDoom Developers, UZDoom Developers
Forum rules
Please be as descriptive as possible in your posts (list your hardware and operating system, the version of the source port you are using, any mods you are running and how they're being loaded, etc.)
This will help others to give you a solution!
Please be as descriptive as possible in your posts (list your hardware and operating system, the version of the source port you are using, any mods you are running and how they're being loaded, etc.)
This will help others to give you a solution!
-
PurpleRhino83
- Posts: 15
- Joined: Sat Feb 03, 2018 8:26 am
- Location: Dhaka, Bangladesh
Loading gzdoom config file with zdl
Last edited by PurpleRhino83 on Wed Sep 12, 2018 5:37 am, edited 1 time in total.
-
Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49252
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: Loading gzdoom config file with zdl
What's confusing here? -config overrides the default config path for both reading and writing so it should be all you need.
-
PurpleRhino83
- Posts: 15
- Joined: Sat Feb 03, 2018 8:26 am
- Location: Dhaka, Bangladesh
Re: Loading gzdoom config file with zdl
Sorry for not clearing it up. I tried to load a custom ini file using -config that i had already configured with a text editor, but after starting the mod it looked like as if i've started gzdoom for the first time with default settings, which led me to believe that it wasn't loading the custom ini file i was telling it to load. I checked and it wasn't loading from the custom config file, instead it was writing the mod specific settings in the default ini file and it created another config file outside ZDL folder called "Mod" without any file extension.Graf Zahl wrote:What's confusing here? -config overrides the default config path for both reading and writing so it should be all you need.
-
Guest
Re: Loading gzdoom config file with zdl
I just had this issue myself, and was able to figure it out. This is 5 months late, I know, so as you've probably already resolved the issue, this is intended more for the edification of anyone else who Googles the problem and ends up here:
You may have spaces in one of the folder names in your filepath. Since you got "Mod", I'd imagine you were trying to set a filepath that looked like this: drive:\parentfolder\Mod WADs\wad\config-name.ini. The space between Mod and WADs is read as the end of the -config command, thus spitting out a blank extentionless file named Mod and using default settings.
What you need to do is wrap the config filepath in quotes, which will prevent the rogue space from ending the -config command. The example I gave above would thus be -config "drive:\parentfolder\Mod WADS\wad\config-name.ini", and should work just fine.
You may have spaces in one of the folder names in your filepath. Since you got "Mod", I'd imagine you were trying to set a filepath that looked like this: drive:\parentfolder\Mod WADs\wad\config-name.ini. The space between Mod and WADs is read as the end of the -config command, thus spitting out a blank extentionless file named Mod and using default settings.
What you need to do is wrap the config filepath in quotes, which will prevent the rogue space from ending the -config command. The example I gave above would thus be -config "drive:\parentfolder\Mod WADS\wad\config-name.ini", and should work just fine.