MantisBT - Zandronum
View Issue Details
0002346Zandronum[All Projects] Bugpublic2015-07-12 18:462018-09-30 22:14
Hypnotoad 
 
normalcrashalways
closedopen 
MicrosoftWindowsXP/Vista/7
2.1 
3.03.0 
0002346: Software 3d floors crash in jumpmaze map
Map RJECT06 of Jumpmaze 2 will crash any software user. Edward-san debugged it and believes it is related to the 3D floors code.

I have attached a crash report.
Command line: zandronum -iwad DOOM2.WAD -file skulltag_actors_1-1-1.pk3 skulltag_data_126.pk3 jumpmaze2_v8a.pk3 +map rject06

then in console: 'warp -464 -32' will go boom.
No tags attached.
zip CrashReportRJECT06.zip (26,563) 2015-07-12 18:46
/tracker/file_download.php?file_id=1581&type=bug
Issue History
2015-07-12 18:46HypnotoadNew Issue
2015-07-12 18:46HypnotoadFile Added: CrashReportRJECT06.zip
2015-07-12 18:50Edward-sanNote Added: 0012908
2015-07-12 18:55Edward-sanSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=7621#r7621
2015-07-12 18:59Edward-sanSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=7622#r7622
2015-07-12 19:07Edward-sanNote Edited: 0012908bug_revision_view_page.php?bugnote_id=12908#r7624
2015-07-12 19:08Edward-sanNote Edited: 0012908bug_revision_view_page.php?bugnote_id=12908#r7625
2015-07-12 19:08Edward-sanPriorityurgent => normal
2015-12-13 03:07DuskNote Added: 0013977
2015-12-13 03:07DuskStatusnew => feedback
2015-12-13 03:08DuskStatusfeedback => resolved
2015-12-13 03:08DuskFixed in Version => 3.0
2015-12-13 03:08DuskTarget Version => 3.0
2015-12-13 03:08DuskNote Edited: 0013977bug_revision_view_page.php?bugnote_id=13977#r8321
2018-09-30 22:14Blzut3Statusresolved => closed

Notes
(0012908)
Edward-san   
2015-07-12 18:50   
(edited on: 2015-07-12 19:08)
There's a simpler way to reproduce: when you load the map offline, strafe to the right.

Also, it doesn't happen in 2.0. No, it happens also there, with the mentioned steps. I did not manage to reproduce in 2.0 because I was running randomingly around...

(0013977)
Dusk   
2015-12-13 03:07   
(edited on: 2015-12-13 03:08)
Appears to have fixed itself in 3.0.