Each time when E2M5 and DM4 are loaded in a quake session this error occurs, no matter in which order they are loaded or how many maps were loaded between them.
Reported by Ghettoblasta from Clan Jaegermeister
More error producing combinations are...
E4M6 and DM4
Mission Pack #1:
HIP2M1 and HIP2M4
HIP2M2 and HIP2M4
HIP2M6 and HIP2M4
HIP2M1 and HIP3M3
HIP2M3 and HIP3M3
Capture The Flag (Allstar CTF):
CTF2 and CTF6
CTF2 and CTF2M5
CTF2 and CTF2M7
CTF2 and TWCTF2MC
Mission Pack #2 is o.k.
Malice is o.k.
Beyond Belief is o.k.
Zerstörer: Testament Of The Destroyer is o.k.
reason:
This error is raised because a map (here DM4) uses a texture with the same name like in another map (here E2M5 or E4M6), with a different size.
A handling for this by GLQuake would be great.
workaround:
use BSP Texture Renamer, and make sure you read the part about QW's map checksumming in its readme
An example can be seen here, where "comp1_1" of E1M1 was renamed to "city2_6". The modified E1M1 was loaded in GLQuake and then DM6
A handling for this by GLQuake[World] would be great
In the most cases it starts at offset 13 and contains "3f 3f 3f 4b 40 00"
Many current and early versions of WAD creating tools do not pad texture names with 0x00. Unfortunately QBSP copies the mip textures directly from the WAD files, although it has a "cleanupname" function in WRITEBSP.C.
consequences:
This garbage gets into the BSP file and can cause problems with QW's mapchecksumming.
Renaming textures, like BSPTXREN does, should be done with care, as you can not recreate this garbage.
Unfortunately the whole texture name is used for mapchecking in QW (16 bytes = max. 15 chars + EOS) including the garbage.
solution for new maps:
TexMex can clean existing WADs, just load and save
QuArK does WADs right
TreeQBSP 1.63 cleans up texture names
a fixed QBSP is available for download
fixed in URQP 1.05 for QuakeED (incl. Stoneless, QERadiant)
solution for WorldCraft:
@PointClass base(PlayerClass, Targetname) size(-16 -16 0, 16 16 56) = info_teleport_destination : "Teleport destination" []
In some maps visible skies are handled like walls by the engine.
When you fire a rocket at those wrong skies, then it will explode when it touches the brush.
Reported by Jonathan "Perged" Down
texture names of skies must start with sky, so QBSP sets the CONTENTS_SKY flag of the face or brush(?).
assumption:
this is caused by early versions of QBSP during the development phase of Quake.
Reported by Pete "GanGrene" Rondeau
I could only reproduce this when I started the client on the same machine as the server, all other clients in the lan did not crash. Btw it is not related to the missing "wad" attribute of the map, adding a "wad" attribute to JVX1 does not fix it.
workaround:
It only happens when the client never loaded a map before, so connecting to another or the same server with another map helps. Even playing a demo works.
Reported by Necris
Reported by Paul "PaK" Koehler
Reported by Ryan "Frika C" Smith
Reported by Necris
"monster_shambler" entity "t399" is spawned in all skill levels, but not the corresponding "trigger_once" and "trigger_teleport".
comment:
The shambler should be removed, like its triggers, to keep the difficulty of the skill levels (spawnflags 768).
This not a problem, he just spawns too close to the wall, but is not stuck.
Reported by Raymond Martineau
The problem is that id placed the weapon into the balcony.
solution:
Remove the super nailgun at "-1200 208 -112" to keep the weapon balance of the level.
A fix for E2M3 is available for download
The problem is that id placed three triggers to open the caves, but when you spawn in the room directly above you can easily avoid them.
solution:
Add 2048 ("not in deathmatch") to the spawnflags of all triggers with target "t72" and to the the func_doors with targetname "t72".
An updated fix for E1M4 is available for download
Reported by Carl "Lord Sméagol" Lloyd-Parker
The spikemines are placed too close to the walls.
solution:
Move them a little bit more into the room.
A fix for HIP2M4 is available for download (provided by Carl himself)
Read by Robert "Frog" Field on Duel Manifesto
A demo is available for download
The problem is that the "info_teleport_destination" in the cave is just too high, because many level editors assume that it has to be 24 units above the ground. That's wrong, because the QuakeC code adds 27 to it's origin to let the player not get stuck in the floor.
A fix for DM4 is available for download
Note that the teleport brushes are not flushed with the borders and the teleporter and its destination are not too close to each other, as assumed earlier.
Reported by Robert "Frog" Field
A similar error occurs in the START map under the exit to the end level (by Robert Field too) and at top of the start gate in E4M8 (by Max Bartlett)
Screenshots here
reason:
incorrect "trigger_teleport" entities have been overseen
solutions:
Here's the QuakeC workaround to avoid similar crashes on any other map
In START change the trigger_teleport's (model *54) target from "t11" to "t8"
In E4M5 remove the trigger_teleport (model *95).
In E4M8 remove the trigger_teleport (model *75).
Fixes for START, E4M5 and E4M8 are available for download
Reported by Carl "Lord Sméagol" Lloyd-Parker
Typo. Change their targetname from "4500" to "3400".
A fix is available for download (provided by Carl himself)
Reported by Carl "Lord Sméagol" Lloyd-Parker
The wraith with the targetname "t77" is outside the teleporter brush, move it to "-2558 -2186 240" into the teleporter brush.
A fix is available for download (provided by Carl himself)
func_door entities without a related brush (BSP model).
solution:
A fix is available for download.
Additional there's a fix for the engine which avoids unnecessary MOVETYPE_PUSH errors.
Remove spawnflag "start open" (1) from "func_door" entity "t39" with the model "*33"
A fix is available for download
workaround by Raymond Martineau:
The Ogre gets teleported if you go to the blue key door and kill the monsters in front of it before you go into the underwater building to get the blue key.
Add "not in deathmatch" (2048) to the spawnflags of the "item_sigil" entity and the func_doors "t87" and "t17"
The partial fix is available for download
Reported by the Quake Done Quick Team
"trigger_relay" entity "t58" has no target, it should target trigger_relay "t66", which then triggers the teleports
A fix is available for download
Add "not in deathmatch" (2048) to the spawnflags of the trigger_multiple (model *110) and trigger_once (model *105), also give a wait of "2" to the trigger_multiple to reduce the annoying sound of the message.
A fix is available for download
Reported by the Quake Done Quick Team
"monster_demon1" entity "t190" is spawned in easy skill, but not the corresponding "trigger_teleport".
comment:
As there are already two zombies at the teleporter on the graveyard, the fiend should be removed (spawnflags 257).
A fix is available for download
Reported by the Quake Done Quick Team
The "trigger_changelevel" entity was intended for deathmatch only, but the corresponding spawnflag (1792) was not set.
A fix is available for download
"trap_spikeshooter" entity "t62" stucks in a solid brush, just move it outside (y coordinate 2166).
A fix is available for download
This is why some patches do not work correctly with those maps.
Reported by Daniel "Athos Kryn" Olsen
This is why nails are sometimes called "spikes".
Reported by Greg Lewis
with QuakeC 1.06