search

Youda008 / DoomRunner

Preset-oriented graphical launcher of various ported Doom engines (an alternative to ZDL)
GNU General Public License v3.0
241 stars 18 forks source link

[BUG] IPK3's are not handled properly. #176

Closed yum13241 closed 3 months ago

yum13241 commented 3 months ago

If you load a regular WAD file alongside them, that WAD file gets loaded as the IWAD, making mods like Doom CE inconvenient to use.

Youda008 commented 3 months ago

Hi. Thanks for reporting. Can you give me an example? What files/mods are you trying to load, what command it produces, and what should be the correct one?

yum13241 commented 3 months ago

What?! The bug fixes itself after a reboot?

Anyways, what was happening was I was trying to load DOOM64.CE.IPK3 with vanilla.ini set as the chosen config. This (correct) cmd-line would result: gzdoom -config "/home/USER/.config/gzdoom/vanilla.ini" -iwad "/path/to/DOOM64.CE.ipk3"

When I added any .wad file imaginable, this incorrect cmd-line would result: gzdoom -config "/home/USER/.config/gzdoom/vanilla.ini" -iwad "/path/to/Doom_PSX_64_SoundBulb.wad". This would result in DOOM64.CE.IPK3 not loading.

But when I restarted, DoomRunner stopped drinking, it used the correct cmd-line, which would be gzdoom -config "/home/USER/.config/gzdoom/vanilla.ini" -iwad "/path/to/DOOM64.CE.ipk3" -file "/path/to/Doom_PSX_64_SoundBulb.wad"

By the way, I have absolute paths ON and I am on Linux. DoomRunner is version 1.8.2 and I had to rebuild it with Qt5, because of issue #167.

Youda008 commented 3 months ago

Hm, that's weird. IWADs and WADs are completely separate parts of the command that have their own separate handling so i cannot imagine how this could get mixed together. Anyway if it happens again, let me know.

yum13241 commented 3 months ago

I'll close the issue and reopen it with a comment if it happens again.