Skip to content
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

hr2final.wad MAP32 crashes with some screen sizes #52

Closed
Tracked by #34
deat322 opened this issue Sep 18, 2021 · 1 comment
Closed
Tracked by #34

hr2final.wad MAP32 crashes with some screen sizes #52

deat322 opened this issue Sep 18, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@deat322
Copy link
Contributor

deat322 commented Sep 18, 2021

Hello,

I've been using hr2final.wad MAP32 as a benchmark for testing various FastDoom v0.8.7 EXEs with the TAS UV-Max demo that is at dsdarchive.com, h232x423.lmp - I have converted this into a WAD to bypass FastDoom's demo compatibility check, and it plays to completion successfully. I've attached the WAD:

h232x423.zip

I have a BAT file that I use for easy checking:

%1 -nosound -file hr2final.wad h232x423.wad -timedemo demo1

I've noticed when playing back the demo that it will crash when certain screen sizes/modes are used:

Potato quality with screenblocks <= 8
Low quality with screenblocks <= 4
High quality with screenblocks <= 2 (via editing fdoom.cfg)
FDOOMT1
FDOOMT12

Using the demo WAD with vanilla doom2.exe has no issues, even when setting to low quality and screenblocks to 1. The key difference between vanilla and FastDoom that I can see is that FastDoom does not have a sprite rendering limit, though I can not say if that will have any influence on why FastDoom crashes.

It is easy enough to reproduce without the demo WAD by warping to MAP32 on hr2final.wad with potato quality and screenblocks set to <= 3, it will crash before you can leave the starting sector.

I have tested this on a Super Socket 7 and a Socket 370 motherboard with various CPUs and video cards with no other expansion cards or anything else plugged in except the keyboard, and the results are consistent.

@viti95 viti95 added the bug Something isn't working label Sep 20, 2021
@viti95 viti95 mentioned this issue Aug 24, 2022
4 tasks
@viti95
Copy link
Owner

viti95 commented Aug 24, 2022

Moved to #34

@viti95 viti95 closed this as completed Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants