-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGIL don't start the right map when used with doom.wad #187
Comments
I can't reproduce it on Windows x86_64 with RetroArch and on armv7 with PicoArch. I use |
Strange, mine has this hash sha1 : 7742089b4468a736cadb659a7deca3320fe6dcbd The best is probably to always use utimate doom instead... Edit: I have tested 1.1 , 1.8 and 1.9 with the same problem of bad level loading. Curious to know your checksum @DrUm78 |
Ah maybe I misunderstood: mine is Ultimate Doom and is named btw sha1 is |
I read again and that seems obvious now, my bad. I thought also you were talking about the shareware, which works too btw. |
Ah yes, just saw your messages, so indeed you have doom ultimate, it seems to be a mandatory to have SIGIL working... |
Description:
SIGIL don't start the right map when used with doom.wad : it only start a map from doom 1
It's strange because
So 2 solutions : SIGIL is in reality only compatible with Doom Ultimate wad file or there is a bug on prboom when using SIGIL with classic Doom wad file (not ultimate).
Step to reproduce:
Install SIGIL wad file next to doom 1 doom.wad (and not doom ultimate doomu.wad) then start SIGIL : you will not be on the first level of SIGIL.
Wrong SIGIL level (with doom.wad):
Good SIGIL level (with doomu.wad):
Platform :
Any (reproduced on Windows x86 and ARM linux)
The text was updated successfully, but these errors were encountered: