-
Notifications
You must be signed in to change notification settings - Fork 553
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
Desync on Strain map07 #34
Comments
Logged In: YES it appears that chocolate doom is using the old spechit magic number from prboom-plus which has since been commented out and replaced by 0x01C09C98, also the demo playes back with this number details are chocolates current spechit magic number : 0x84f968e8 |
Logged In: YES I was using a different default spechit magic value because it appeared to allow more demos to work "out of the box" without a -spechit parameter being specified. However, in this case, it caused a demo that works OOB on prboom-plus to fail. For consistency with prboom-plus, I've switched to the same spechits default value that it uses; at least that way, the spechits overrun list on Doomworld is applicable to Chocolate Doom as well. |
specifically prevent crash with IDMUS00 in Doom II and with IDMUS0x or IDMUSx0 in Doom fixes chocolate-doom#34 also, fix/add comments and declare "extern boolean P_CheckAmmo()" where it is actually needed
specifically prevent crash with IDMUS00 in Doom II and with IDMUS0x or IDMUSx0 in Doom fixes chocolate-doom#34 # Conflicts: # src/doom/st_stuff.c
specifically prevent crash with IDMUS00 in Doom II and with IDMUS0x or IDMUSx0 in Doom fixes chocolate-doom#34 also, fix/add comments and declare "extern boolean P_CheckAmmo()" where it is actually needed # Conflicts: # src/doom/st_stuff.c
Hi
desync on level exit map07 of strain.wad+strain.deh which does not happen in either doom2.exe or prboom-plus
demo is ST07-237.LMP from http://competn.doom2.net/pub/sda/p-s/stmax-av.zip
demo plays back fine when using -spechit 0x01D6CF98 (same value as PrBoom-plus???)
The text was updated successfully, but these errors were encountered: