At the end of E1L3, it's pretty easy to get killed actors endlessly gibbing. Seems like some kind of portal issue?
[refactoring5]: Duke: Endless gibbing at end of E1L3
Moderator: Raze Developers
Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
-
mjr4077au
- Posts: 830
- Joined: Sun Jun 16, 2019 9:17 pm
- Graphics Processor: nVidia with Vulkan support
- Location: Gosford NSW, Australia
-
Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49204
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: [refactoring5]: Duke: Endless gibbing at end of E1L3
Next time, instead of posting a video, please attach a savegame. I haven't been able to reproduce this yet and this would have been dead easy to test when loaded from a save. 
-
mjr4077au
- Posts: 830
- Joined: Sun Jun 16, 2019 9:17 pm
- Graphics Processor: nVidia with Vulkan support
- Location: Gosford NSW, Australia
Re: [refactoring5]: Duke: Endless gibbing at end of E1L3
Save game in this state is available here: https://drive.google.com/file/d/1j8qoBx ... sp=sharing
-
Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49204
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: [refactoring5]: Duke: Endless gibbing at end of E1L3
This one was actually an original Duke bug. You must just have hit the sweet spot to trigger it.
What was missing that an above water <-> underwater transition never checked the actor's vertical movement, but only the distance, so a slowly diving actor would just be teleported back up which in this case would let it end up at the top of the sector because the case was never considered.
EDuke32 had this fixed, too, btw - I checked after adding the fix.
What was missing that an above water <-> underwater transition never checked the actor's vertical movement, but only the distance, so a slowly diving actor would just be teleported back up which in this case would let it end up at the top of the sector because the case was never considered.
EDuke32 had this fixed, too, btw - I checked after adding the fix.