r10 lights.wad disabled under certain conditions
Posted: Mon Jan 28, 2008 14:10
This is a strange one. If I have this file sitting as a text file called decorate.txt on my desktop and if I use ZDL to load it with r10, then the dynamic lights on objects, as defined in lights.wad, do not appear. The same thing happens if I put the file into a zip or a WAD.
[spoiler][/spoiler]
However, if I drag and drop the file from the desktop directly onto the GZDoom icon, the lights are there.
ZDL is in my directory called F:\doom\gzdoom where my official GZDoom is. r10 is in F:\doom\gzdoomSVN. The same thing happened when placing the file in any directory (including the same one as GZdoomSVN) and loading it with ZDL. This happened both with lights.wad in my skins directory and in the gzdoomsvn directory loaded via the ini autoload section.
So, you'd think it's a ZDL problem because dragging and dropping doesn't show the problem, but I've done a bit more digging. If I add "+logfile f:\log.txt" to the command line in ZDL, lights.wad suddenly works again.
Checking up through the console, it told me:
adding f:/doom/gzdoomsvn/lights.wad (4 lumps)
despite the fact that there were no lights.
Because adding logfile to the command line seemed to stop the problem, I started a game, checked there were no lights glowing from the armor helmet in the first room of map01 and then typed "crashout" at the console. local.txt confirmed the command line and which files were loaded.
[spoiler][/spoiler]
Obviously the missile state of the actor above is a silly test and, I thought, irrelevant to this test so cutting it out so that the file is just:
[spoiler][/spoiler]
Should still give the problem right? Wrong. With the above loaded in exactly the same manner, lights.wad works.
So, I chopped off the renderstyle stuff instead and left the states block intact. No lights when loaded with ZDL.
Progressively chopping out lines from the states block until I was left with this:
[spoiler][/spoiler]
Allowed lights to work again.
Strange huh?
[edit] Putting the command line:
into the start/run command line box also disables the lights so it isn't anything to do with ZDL at all. However, something about that file and command line combination disables the lights in lights.wad even thought lights.wad has been loaded. [/edit]
[spoiler]
Code: Select all
actor test : Zombieman replaces Zombieman
{
renderstyle Stencil
Stencilcolor 00 255 128 00
Alpha 0.6
States
{
Missile:
BOSS E 5 A_FaceTarget
BOSS E 3 A_SetInvulnerable
BOSS E 12 A_FaceTarget
BOSS F 0 BRIGHT A_CustomBulletAttack(0,0,1,18,"NJBluePuff2",0,0)
BOSS F 4 BRIGHT A_CustomRailgun (0, 0, "9B 00 00", "40 8B B4", 0, 0, 0) //damage was 18
BOSS F 0 bright A_CustomMissile ("ManstopperCasing", 32, 10, random(-85,-95), 2 , 45)
BOSS E 5 A_FaceTarget
BOSS E 3 A_UnSetInvulnerable
Goto See
}
}However, if I drag and drop the file from the desktop directly onto the GZDoom icon, the lights are there.
ZDL is in my directory called F:\doom\gzdoom where my official GZDoom is. r10 is in F:\doom\gzdoomSVN. The same thing happened when placing the file in any directory (including the same one as GZdoomSVN) and loading it with ZDL. This happened both with lights.wad in my skins directory and in the gzdoomsvn directory loaded via the ini autoload section.
So, you'd think it's a ZDL problem because dragging and dropping doesn't show the problem, but I've done a bit more digging. If I add "+logfile f:\log.txt" to the command line in ZDL, lights.wad suddenly works again.
Checking up through the console, it told me:
adding f:/doom/gzdoomsvn/lights.wad (4 lumps)
despite the fact that there were no lights.
Because adding logfile to the command line seemed to stop the problem, I started a game, checked there were no lights glowing from the armor helmet in the first room of map01 and then typed "crashout" at the console. local.txt confirmed the command line and which files were loaded.
[spoiler]
Code: Select all
ZDoom version 1.0.32 - 2.1.7xx (r723) (Jan 28 2008)
Command line: "f:\doom\gzdoomsvn\gzdoom.exe" -iwad "F:\Doom\gzdoom\doom2.wad" -file "F:\Documents and Settings\Nigel_Rowand\Desktop\decorate.txt"
Wad 0: gzdoom.pk3
Wad 1: doom2.wad
Wad 2: bba.wad
Wad 3: Blud.wad
Wad 4: flashlight.wad
Wad 5: flashlightres.wad
Wad 6: KEEN.WAD
Wad 7: NJBLK01.wad
Wad 8: scope.wad
Wad 9: Variants.wad
Wad 10: Xhairs.wad
Wad 11: njsplash.wad
Wad 12: lights.wad
Wad 13: decorate.txt
Current map: MAP01
viewx = -6291456
viewy = 51380224
viewz = 6369456
viewangle = 40000000Obviously the missile state of the actor above is a silly test and, I thought, irrelevant to this test so cutting it out so that the file is just:
[spoiler]
Code: Select all
actor test : Zombieman replaces Zombieman
{
renderstyle Stencil
Stencilcolor 00 255 128 00
Alpha 0.6
}Should still give the problem right? Wrong. With the above loaded in exactly the same manner, lights.wad works.
So, I chopped off the renderstyle stuff instead and left the states block intact. No lights when loaded with ZDL.
Progressively chopping out lines from the states block until I was left with this:
[spoiler]
Code: Select all
actor test : Zombieman replaces Zombieman
{
States
{
Missile:
BOSS E 5 A_FaceTarget
BOSS F 0 BRIGHT A_CustomBulletAttack(0,0,1,18,"NJBluePuff2",0,0)
BOSS F 4 BRIGHT A_CustomRailgun (0, 0, "9B 00 00", "40 8B B4", 0, 0, 0) //damage was 18
BOSS F 0 bright A_CustomMissile ("ManstopperCasing", 32, 10, random(-85,-95), 2 , 45)
BOSS E 5 A_FaceTarget
BOSS E 3 A_UnSetInvulnerable
Goto See
}
}Allowed lights to work again.
Strange huh?
[edit] Putting the command line:
Code: Select all
"f:\doom\gzdoomsvn\gzdoom.exe" -iwad "F:\Doom\gzdoom\doom2.wad" -file "F:\Documents and Settings\Nigel_Rowand\Desktop\decorate.txt"
