Page 1 of 1

Annoying Hexen crash in v1.8.7 and v2.0.03

Posted: Wed Oct 08, 2014 13:02
by fr1dd
Got a Hexen crash problem that occurs in v1.8.7 and v2.0.03. The crash does not occur in v2.0.01, v2.0.02 or v1.8.6 and down (only tested down to v1.8.2). No crash with ZDoom v2.7.1 either.

The crash occurs in MAP27 (cheatcode ''visit13'') at the lower stairway located directly to the right in the main hall. There are some dragon stonewalls that can be activated (to spin around) in the courtyard by a stoneswitch behind two trees.

When you approach the two first stonewalls closest to the main hall while they are spinning the game crashes instantly. When they stand still for a short moment or not have been triggered it works fine. But as soon they start spinning the game crashes. So it´s impossible to access those areas without the noclip cheatcode.

The game is run fresh without any config done.

Re: Annoying Hexen crash in v1.8.7 and v2.0.03

Posted: Sat Oct 11, 2014 16:14
by Kappes Buur
Also happens with gzdoom-g2.1.pre-82-g5d032f3

After activating the switch, the polys start to turn.
Then, running up the corridor from the courtyard, GZDoom crashes when coming level with the second set of polys.

Image Image

Re: Annoying Hexen crash in v1.8.7 and v2.0.03

Posted: Sat Oct 11, 2014 20:04
by Graf Zahl
I already fixed that but haven't committed the fix yet because I need to make sure that the fix doesn't cause any other problems. This is caused by the polyobject BSP builder not initializing a few fields that GZDoom added to the segs.

Re: Annoying Hexen crash in v1.8.7 and v2.0.03

Posted: Sat Oct 11, 2014 21:30
by fr1dd
Graf Zahl wrote:I already fixed that but haven't committed the fix yet because I need to make sure that the fix doesn't cause any other problems. This is caused by the polyobject BSP builder not initializing a few fields that GZDoom added to the segs.
Nice to know that. Thumbs up :).