Visual Error on E2M2 Demo/Screen Melt Transition about fastdoom HOT 9 CLOSED

Good idea on checking the hash first. The only issue that a 386 is slow, so I'll add a check for WAD size and modify the readme, I guess that should be enough. Thanks for testing.

from fastdoom.

Can you share FastDoom version and executable used? Also, can you check what Doom WAD version do you have?

from fastdoom.

FastDoom Latest 0.9.9e
I don't think I've loaded anything but FDSETUP.EXE, which I assume loads FDOOM.EXE?

MD5: c4fe9fd920207691a9f493668e0a2083
WAD File: The Ultimate DOOM (v1.9)

from fastdoom.

I checked this WAD in DosBox X and it crashes Vanilla Doom after E2M2 with the error

W_GetNumForName: HELP2 not found!

I am guessing this link is relevant. Is FastDoom looking for HELP2 and creates this error?

from fastdoom.

This visual error happens with this same WAD in DOSBox-X as well, so not a MiSTer FPGA issue.

from fastdoom.

Question, is the WAD file named DOOM.WAD or DOOMU.WAD ?

from fastdoom.

Simply "doom.wad"

from fastdoom.

Oook I think that is what is causing issues. The Ultimate Doom WAD should be named doomu.wad in order to work properly.

from fastdoom.

All versions I just checked, including the commercially available version from GOG, have it labeled as DOOM.WAD despite being Ultimate Doom. I think most people's Ultimate Doom Wads are going to be named with that convention.

I think it would be useful to update the Readme for users to rename their ultimate doom wads as DOOMU.WAD and/or check their hashes first.

Most source ports these days seem let users treat Doom 1 Wads sort of interchangeably, but I can understand your commitment to keeping FastDoom so vanilla.

I can confirm that changing it to DOOMU.WAD does indeed load the first slide again, fixes this particular issue.

from fastdoom.