[c1bb7de23] BFG IWADs don't load if 1.9 IWAD is in $PROGDIR

[mjr4077au]

Sorry for the gumby title, the length limits in the subject are really annoying.

As compiled with MSVC 19.5, if I place a v1.9 doom.wad IWAD into the directory, but load the BFG doom.wad IWAD that's found from Steam, it won't load properly and errors when going to E1M1. The BFG IWAD works fine without the v1.9 IWAD being there, and the v1.9 IWAD works at all times.

EDIT: This also occurs under the same circumstances for the doom2.wad IWADs.

[Graf Zahl]

How am I supposed to reproduce this? Using the BFG IWAD in my IWAD search path does not cause this type of glitch.

[mjr4077au]

My situation here was the BFG IWAD was being found from Steam, but I had a 1.9 IWAD in my game directory. Having the 1.9 IWAD in my game directory caused the above to occur when trying to play the BFG IWAD.

The 1.9 IWAD played fine, and the BFG IWAD did as well when I removed the 1.9 IWAD from the game directory. Just having the BFG IWAD there won't cause the bug, it loads fine without the 1.9 IWAD.

[_mental_]

Please post a complete log. Lines after "W_Init: Init WADfiles." should help to figure out what's going on.

[Rachael]

Sorry for the gumby title, the length limits in the subject are really annoying.

Unfortunately the limit is set by phpBB, there's nothing I can do to change that.

Also, loading my copy of the BFG IWADs work fine. You should check your IWADs with one of these IWAD tools:

https://github.com/chungy/iwadverifier
https://github.com/Doom-Utils/iwad-patches

[mjr4077au]

I'm not at home to test until tomorrow but I have a strong feeling this commit would have fixed it: https://github.com/coelckers/gzdoom/com ... 207b0b9122

The WADs aren't corrupt, the BFG WADs play fine from my search path without the presence of 1.9 WADs in my GZDoom directory. You must test by having both 1.9 and BFG IWADs in your search path, not just one or the other.

[mjr4077au]

This is definitely still an issue for me. I think I'm just going to have to go through the commits myself and find where it goes wrong for me as it's too obscure of an issue.

[Graf Zahl]

Can't you just debug and check what goes wrong here?
Or as a first step post the entire startup log?

[mjr4077au]

Full log attached. This is opening up a doom.wad BFG Edition as found from my Steam directly, while containing a doom.wad 1.9 Edition in GZDoom's running directory. Log doesn't say too much.

Regarding debugging, because it's not fatally crashing how would I get a breakpoint to know where it's crashing?

EDIT: Just be 100% clear, it does this on a fresh config without any upscale packs etc. I can get a new log if you like?

[Graf Zahl]

To me this looks like it opens the correct WAD directory but reads the content from a different file. No idea how this can happen, this is the same file handle that gets used here.

[mjr4077au]

Yeah that makes 100% sense. I was hoping that the patch you did to fix the SW menus might have helped here, thinking maybe there was some kind of 'doom.bfgedition' magic in the pk3 file that was getting skipped but alas not.

I'm going to keep going through the commits to try and isolate the one where the problem originates as that's about all I can do within my abilities.

[mjr4077au]

c1bb7de23a is the straw that breaks the camel's back. Works fine at the commit beforehand.

Oh, and @Rachael if you happen to catch this, I wasn't pointing fingers at anyone regarding subject length limitations, more just having a rant. Understand that it's a product limitation

[Graf Zahl]

Ugh, that one was a huge commit that not only shuffled some code around but also renamed a few things globally.

[Graf Zahl]

Ok, I can reproduce it when having two doom.wad files in the selector, at least some progress.

[mjr4077au]

Yeah I saw the size of that monster and thought "shit he's going to hate this...". I wouldn't be surprised if it's a one-liner fix or something silly.

Glad it's been reproducable at least, I was starting to think that others might have thought I was on crack or something .