MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003621Zandronum[All Projects] Bugpublic2019-03-11 02:132019-03-23 14:13
ReporterJanosch 
Assigned To 
PriorityhighSeveritycrashReproducibilityalways
StatusclosedResolutionno change required 
PlatformMicrosoftOSWindowsOS Version10
Product Version3.0 
Target VersionFixed in Version 
Summary0003621: Zandronum Has Issues With Death And Decay 2.4 Softcore
DescriptionHow to explain this... I thought this was an issue with the mod itself, but I was told this was a Zandronum problem, so I was told to make a bug report here by the mod developer on discord. So basically what happens is during gameplay, certain monsters seem to freeze/crash the Zandronum client. Specifically in Death And Decay version 2.4, the Mephisto monster's Gatling Gun attack on the top of his head hangs the client, as well as the Legionnaire's kick attack. Sometimes this just hangs the client for around 5-10 seconds, I'd say about 25% of the time while it hangs it will decide to just close itself out of the client back to the desktop (Which I'm assuming is a crash) After this happens once and recovers from it with no crash, It'll not do this again until you re-open Zandronum again and re-encounter one of these monsters when they do said attack. I've had every single player on my server report this issue. There's one last monster that does this but this one fatally crashes it instantly with no hang-ups, and that's the Diabloist monster. For some reason playing Zandronum offline this doesn't happen, only online. I hosted DnD 2.4 on TSPG's Painkiller node for about 2 weeks and was highly confused on why it kept crashing the server. Mifu told me to use the debug version, so I did, and everytime the server closed itself out it gave me a "[19-03-09 13:18:21] zandronum-server: /home/sean/zabuild/src/src/p_sight.cpp:660: bool P_CheckSight(const AActor*, const AActor*, int): Assertion `t2 != NULL' failed." on RCON. So I was debating if this was an issue with TSPG's servers, with the mod, or the client itself. I asked everyone, and the DnD mod developer said it was a Zandronum issue and to report it here. I have several links of videos testing all of these issues: Here's one with Mephisto's gatling gun hanging the client:'https://youtu.be/xVnLGmIiz8U [^]' Legionnaire's kick hanging the client:'https://youtu.be/4AJCYrnaVNM [^]' and finally the Diabloist crashing the TSPG Painkiller server with the RCON error:'https://youtu.be/N4UbhZr7VGc. [^]' I don't know what's causing this. The mod developer wanted me to report this as well to figure out what's causing the issue because he doesn't know, either.
Steps To ReproduceFor Mephisto and Legionnaire's bug:

Mephisto:

1. Open up the Zandronum client (version 3.0) with the wad order as follows:

dndv2.4-152-gd3332858.pk7
dnd_monstersv2.4-152-gd3332858.pk7
dnd_onlyammov2.8.wad

(Map packs don't really matter here as long as they don't replace or cause incompatibilities with DnD's monsters)

2. In-game on console: "summon Mephisto", wake him up, watch him hang the client when he starts spinning his gatling gun attack. Observe that his plasma arms don't do it.

Legionnaire:

1. Open up the Zandronum client (version 3.0) with the wad order as follows:

dndv2.4-152-gd3332858.pk7
dnd_monstersv2.4-152-gd3332858.pk7
dnd_onlyammov2.8.wad

(Map packs don't really matter here as long as they don't replace or cause incompatibilities with DnD's monsters)

2. In-game on console: "summon Legionnaire", wake him up, notice how his laser beam rifle attack doesn't do anything but when you get close to him his melee kick attack will hang the client for a bit.

For Diabloist:

1. Use a database and save/load your character, etc. high enough through normal gameplay in order to get Diabloist to show up (level 20ish?) OR summon him using sv_cheats, but I can't do this since I don't have authority since it's TSPG's servers.

2. Host a server under TSPG Painkiller (DMFLAGS etc, don't really seem to necessarily matter.)

Use the wads as follows:

vilchal.wad (good testing wad with a single map with archvile at start, increasing chances of the random monster spawner to spawn Diabloist within normal gameplay)
dndv2.4-152-gd3332858.pk7
dnd_monstersv2.4-152-gd3332858.pk7
dnd_onlyammov2.8.wad

3. In-game, use "send_password" with your rcon password to gain rcon access. In console: "rcon setsoftcore" will set this to softcore.

4. Load your character in the single map in vilchal.wad, and hope the first enemy becomes Diabloist. As Diabloist is spooked, he will run around and start attacking, when he starts approaching the wall of the map, the entire Server will crash and rcon will show the "[Time this occurred on the server] zandronum-server: /home/sean/zabuild/src/src/p_sight.cpp:660: bool P_CheckSight(const AActor*, const AActor*, int): Assertion `t2 != NULL' failed."
message.
Additional InformationFor Diabloist, this seems to happen regardless of which map pack you use, anytime Diabloist is encountered in a map and it walks near a wall, the server wipes out, staying on the "Waiting for server..." message. I believe these are the only 3 monsters that seem to have a fit with Zandronum.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2019-03-11 02:13JanoschNew Issue
2019-03-14 08:21JanoschNote Added: 0020443
2019-03-23 14:13Edward-sanNote Added: 0020453
2019-03-23 14:13Edward-sanStatusnew => closed
2019-03-23 14:13Edward-sanResolutionopen => no change required

Notes
(0020443)
Janosch   
2019-03-14 08:21   
Patched all three monsters out using actor replacements under permission of the Wad Developer; the monsters seemed to be bugged themselves; I highly doubt at this point this is a Zandronum issue, but rather a mod issue; feel free to delete the report.
(0020453)
Edward-san   
2019-03-23 14:13   
Got it. Closed by user's request.