Doom source port config file being ignored/overwritten

[buvk]

I am using DoomRunner 1.8.0 and the latest version of Crispy Doom.

My final launch command looks like this:

"./crispy-doom.exe" -config "crispy-doom.cfg" -iwad "../IWAD/DOOM.WAD"

If I execute the above via command prompt, Crispy Doom launches and uses the config file as expected.

If I execute the above via DoomRunner, my config file is overwritten, and all my settings are lost. A new folder called "Crispy Doom" is created within my "D:\Games\Doom\Crispy Doom" folder.

I do not have this issue with DoomRunner 1.7.3.

[Youda008]

Overwritten? 😱 But the launcher doesn't write to the config files.

[Youda008]

Can i please see your options.json file?

[buvk]

Overwritten? 😱 But the launcher doesn't write to the config files.

Yeah, all settings would be back to default. I think it is creating and using a config file in "D:\Games\Doom\Crispy Doom\Crispy Doom" which for some reason makes the config file in "D:\Games\Doom\Crispy Doom" revert back to default settings.

[buvk]

Can i please see your options.json file?

options.zip

[Youda008]

Hmm, this is a peculiar problem, i don't understand where it's comming from. All the paths i'm passing to the engine are correct. And it's only Crispy Doom doing this, not any of the other engines, so i would suspect this to be rather a Crispy Doom bug that Doom Runner's. But i will try something.

[Youda008]

So apparently, Crispy Doom cannot handle being started from another directory using relative executable path (no idea what's going on there that this is a problem). Luckily, there seems to be a simple workaround. Can you please try this modified version? DoomRunner-Crispy-workaround.zip

[buvk]

This version fixes the issue.

[Youda008]

Awesome, i will release this fix officially soon together with some others.

[Youda008]

fixed