|
Notes |
|
|
|
|
Can you try to rip apart one of the maps that has this problem to see which property of the map causes this? |
|
|
|
(0001699)
|
|
unknownna
|
2011-05-20 04:26
(edited on: 2011-05-20 05:01) |
|
I copied D2IG05 to a new WAD. It seems that a LOADACS-script is acting as the catalyst here. It works as intended if I remove the SWLIGHT lump.
Here's the source:
#library "swlight"
#include "zcommon.acs"
script 256 ENTER net
{
int usesoftware = GetCVar ("vid_renderer");
//I would have used an array for the gradient textures,
//but ACC is convinced it isn't a map script. Oh well.
if (usesoftware == 0)
{
ReplaceTextures("XLIGHT-B","TNT1A0");
ReplaceTextures("XLIGHT-G","TNT1A0");
ReplaceTextures("XLIGHT-O","TNT1A0");
ReplaceTextures("XLIGHT-R","TNT1A0");
ReplaceTextures("XLIGHT-W","TNT1A0");
ReplaceTextures("XLIGHT-X","TNT1A0");
ReplaceTextures("XLIGHT-Y","TNT1A0");
ReplaceTextures("YLIGHT-B","TNT1A0");
ReplaceTextures("YLIGHT-G","TNT1A0");
ReplaceTextures("YLIGHT-O","TNT1A0");
ReplaceTextures("YLIGHT-R","TNT1A0");
ReplaceTextures("YLIGHT-W","TNT1A0");
ReplaceTextures("YLIGHT-X","TNT1A0");
ReplaceTextures("YLIGHT-Y","TNT1A0");
}
}
|
|
|
|
|
|
Interesting. Is the source of swlight available? |
|
|
|
|
SWLIGHT = compiled ACS
SLITESRC = Source (the code above)
The "x minute warning" bug occurs even when I remove all scripts, things and sector/line specials from the map. An empty shell of the map is all that is left and it still happens. |
|
|
|
|
|
Strange, I can't reproduce this. Tested D2IG01 and D2IG05. |
|
|
|
(0023609)
|
|
unknownna
|
2024-04-14 23:30
(edited on: 2024-04-15 14:44) |
|
Revisiting this years later, it seems to be caused by some undefined behavior from linedef action 103: Scroll Texture Down
Here's the interesting part: The textures have to be scrolling at a speed for it to happen, and it has to be at minimum 14 linedefs present on the map that is using this special for the glitch to occur.
1. zandronum -iwad doom2.wad -file 1minwarning_01.wad -host +timelimit 1
2. zandronum -iwad doom2.wad -file 1minwarning_01.wad -connect localhost +cl_startasspectator 0
3. "reconnect" in the console. Upon every reconnect, the announcer will shout "1 minute warning!".
Double-checking today, it seems to not always occur in the example wad. Sometimes after reconnecting the glitch doesn't happen, but I'd say that it happens around 80% of the time. I use a local wireless connection from a laptop to a router located around 3 meters from it, if it helps.
Edit:
Even more confusing is that the example wad only breaks in 3.1, but not in earlier versions. I guess this commit'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/ee36bf542180b8b74d641cf72449c52a9077de44 [^]' is causing some underlying issue to appear more frequently in 3.1 compared to before. Feels like some packet order issue.
|
|
Screenshot_Doom_20110520_222705.png (201,685) 2011-05-20 20:37
1minwarning_01.wad (4,446) 2024-04-14 23:31