 |
gzdoom-Spie812.ini (43,986 bytes) |
|
|
Works in deathmatch, not coop |
|
|
Using 2.4.0 the crash is present but I can't reproduce it with the latest devbuild. Could you please download the recent version from here and give it a try? |
|
|
using gzdoom-2.5pre-273-gb1e1f25, the most recent version right now, I was still able to reproduce the crash. Crash: https://www.youtube.com/watch?v=o6-jJkPDFRE |
|
|
That looks like a stack overflow caused by some infinite recursion. |
|
|
Yes, it's something with obituary messages. It happened only on maint2.4 branch for me but apparently the issue is still there. I'll check it again on master a bit later. |
|
|
An infinite recursion was introduced in this commit. To fix the recursion itself this part can be rewritten as Although I have some problems with matching old and new code. Old version of ClientObituary() did more things which were partly moved to Actor.GetObituary() function. Probably I'm just missing something. |
|
|
That would pretty much break the entire intent here, i.e. allowing to override GetObituary. The actual condition that causes the recursion needs to be identified and properly handled. |
|
|
attacker and inflictor are the same object in ClientObituary() function on C++ side. This is the real cause of infinite recursion. I have no clear vision how resolve it. Is it enough just to compare them for inequality? |
- Anonymous
