Passing "Others" parameters with spaces about twad HOT 1 CLOSED

Hey, first off sorry for the very delayed answer :)

In case you are still interested I've looked into the issue and this is indeed a good catch. I think I've fixed this with this commit:
bb5b329

Basically I did not consider "others" being used that extensively and only thought about engine parameters which don't contain spaces. I took the naive route and just split by space which obviously does not work for your use case. I now treat the "other" parameters as one-record-csv where the field separator is a space. That means you can now quote your string with double quotes if it contains spaces and that should work.

Regarding the issue, that you need to provide the absolute path: I cannot reproduce that one. Check out the two attached screenshots where I tried to replicate the issue. The configuration for Scythe II works like that, with the relative path to DOOMWADDIR.
Though, I am testing that now that the first issue is fixed so that might have been the reason. Please give it a shot :)

Edit:
Now that I thought about it... DOOMAWADDIR is not the CWD as you phrase it. It really is just set as environment variable. All the source ports look for the variable and if it is set, wads (and pk3 and so on) are searched there. Seems like ports don't look for configs or other file types in DOOMWADDIR. So that is port behaviour.
It might be possible to add an option to use DOOMWADDIR as working dir, though not sure what unwanted effects that might have.

from twad.