News | Forum | People | FAQ | Links | Search | Register | Log in
Mapping Help
This is the place to ask about mapping problems, techniques, and bug fixing, and pretty much anything else you want to do in the level editor.

For questions about coding, check out the Coding Help thread:
First | Previous | Next | Last
Triggering Monsters (Quake 1) 
For teleporing monsters via trigger once.

1. Make some monsters and place in into "trigger_teleport" brushes. Each monster in separate "trigger_teleport" entity. All teleport entities must have one targetname.
2. Add some teleport destinations - one "info_teleport_destination" for one "trigger_teleport", and connect it one to one.
3. Connect your "trigger_once" to "trigger_teleport" ents. 
Spawn a monster in. (I know you've done some of this but for others:)

How to teleport in a monster upon triggering something:

1. make an area outside your playable level and place your your monster
2. make a brush with the trigger texture that covers the center of the monster.
3. right click and make the trigger brush into a trigger_teleport give it a targetname (i.e. monster1) and a different target (i.e. dest1)
4. place a info_teleport_destination where you want the monster to teleport to give that the targetname of the target in step 3 (in this case dest1)
5. set your trigger (in your case above it's picking up a nailgun) the target of the nailgun should match the trigger_teleport targetname in #3 (monster1.)
6. make sure you keep track of your targetname and targets - it's easy to get these confused. Just remember targets trigger targetnames in other entities

something to note: if you are spawning in two at the same time they need their own info_teleport_destination entities so they can share a targetname and be triggered at the same time but they each need their own separate target. If you use one destination they will telefrag each other! And you may want to add a key of delay and a value of 0.1 to the second monster so there is a tiny delay between their spawns. I recall this solving an issue before so try it if you see problems.

2. there's no real-time lighting preview right now in any of the editors. NetRadiant will show you a representation of the falloff of a light. ericw had hinted he might do an application that does realtime lighting preview at some point. Which would be instantly popular. 
@doomer is correct and I wasn't clear above. Each monster needs its own trigger brush and separate destination but they can share a targetname. Also I think you can just add a target to the nail gun instead of making a trigger_once. But if you wanted the monsters to teleport as you walk into a room then you'd make a trigger brush right click and make it a "trigger_once" Good luck!!! 
Awesome. Thanks guys. I love your levels and you're both big reasons why I started learning Trenchbroom. You guys, Sock, Ionous, Skacky, etc are incredible at this. 
Wow, that's very kind of you. I am currently working on video tutorials for Trenchbroom. You seem to figuring out thing on your own though! The first one will be out early next week. As time progresses there will be some advanced tuts you'll want to check out. I'll post here on fucn with links. 
Beautiful. Got it on the first shot as you guys explained it perfectly. Definitely looking forward to the tutorials. Thanks again, guys. You rock. 
Just To Be Safe 
I made a post about this, but I might have made a mistake with that. Here's what I wanted to ask:

I've been looking for a tutorial on the use of Jackhammer for a few hours now, but I can't seem to find anything. Is there a tutorial out there I can use to see what's up? 
If you can't find any tuts for JACK then you have some options that will get you close.

First, JACK is based on Valve's Hammer editor. You will find tutorials for Hammer out in the wild. There are many similarities between the programs. I believe JACK has more features but I haven't used it too much.

The other option is to use Worldcraft tutorials. JACK is based on Hammer which was based on Worldcraft and many concepts from Quake will carry over.

Good luck and consider trying TrenchBroom 2. I will be publishing a Quickstart video tutorial sometime this weekend (or before) and you may like what you see.

The tuts will be on my YT channel is here 
Artifacts In Q2 Sun/lightmap 
Hello guys, this is my first post here. It's interesting to finally have some reason to post here. I'm following func_msgboard for sometime, following all the cool maps and mods are being born here... Good stuff :)

Anyway, i decided to try something in Q2 engine. Right now, i'm having some problems when using _sun. Compiling with qrad3, i get this result:

it doesn't happen when i compile regular lights only, just when I use Sun... :/ Anyone have some idea? Thanks! 
Ah, Arghrad 
Arghrad solved my problem :D
back to work 
Scaling Models 
Is there a way to scale (prop) models easily? I have downloaded Preach's crane and helipad models from his site, and after placing them on my map in Trenchbroom they look so small, about the size of a cat. Quite endearing, actually. xD

Will I have to resort to some mdl editing in a separate editor? D: Guess I'm going down the deep end of Quake custom content creation, no more simple map making, huh? xD 
I usually just jump into QME here? and scale the model:

Of course, QME sucks ass and tends to mangle models if they look at it funny so... have fun? 
QME likes to break mdls. Should only be used to view models. :( you may get lucky tho. 
Mdl Scale 
Scale is defined by just one float in the .mdl binary file, I think (Can anyone confirm? Does anything else need to be tweaked other than this one float?)

If so, you could be able to just hax0r it with a hex editor. Preach - any ideas? 
Actually it's a vector of 3 floats

you'll probably want to scale bounding radius too. 
Yeah, you only need to change those 4 floats, so a hex editor will do the trick. If you prefer, you can install the qmdl python module then run the following script against the model.

from qmdl.helper import Helper

#read the model file
mymdl = Helper()
mymdl.mdl.scale = tuple ([i*4 for i in mymdl.mdl.scale])
mymdl.mdl.boundingradius = mymdl.mdl.boundingradius * 4
#save again"bigcrane.mdl")

This is multiplying the scale by 4, vary the value as required. 
It Worked! 
Thanks guys, you just keep helping out, no matter what I keep throwing at ya', AND always in a timely manner, might I add! :)

And for your information Preach, I used your script on a newer Python version 3.6.4. 
Adjusting Mdl Centerpoint 
I'm guessing it's model dependent, but I noticed that the larger I made the helipad, the further away the model diverged from the model entity (or is it in this case just a handle?) in Trenchbroom. Is there a centerpoint in the mdl I should adjust? Can it be done with qmdl or should I use something else? 
One of the quirks of the mdl format is that the model keeps the bottom left corner fixed when you rescale it, rather than the centre. If you add a line like

mymdl.mdl.origin = (-64 -64 -64)

after the mymdl.mdl.boundingradius line in the script from the previous point, you can specify the coordinates you'd like the bottom-left point to be at. Play around with the values! 
I figured it would be something like that. Thanks a heap for going through the trouble of helping me out! :) 
No Worries 
It's cool to see someone using it, I worried that it being a python module was a bit off-putting 
Func_train Question 
How to make train move through four path_corners? I named each correspondingly and gave paths corresponding direction. 
I made a sample map linked below. It's pretty easy to do as you'll see.

I made 4 path_corners. t1 - t4 make sure the target/targetnames are correct and that they close a "loop" - that's the part that people mess up on the most.

I don't think you need to specify a direction. I didn't in this case. Sorry for the weird name. Also you can use Quake101.wad or q.wad for the textures in this map. 
Thank you for your help! watched your tutorial on tuesday so thaks for that as well! 
You're very welcome. LMK if you have any requests for tutorials. :) 
Texture Wads 
New to mapping (thanks @dumptruck_ds) and wondering where everyone gets their textures?

For the moment I'm just looking for the default Q1 textures, but it'd be good to know where to get custom textures come from too. 
Here's A Start. 
Texmex will let you open a map/bsp and save as a wad 
Tex Mex 
Does TexMex have a homepage somewhere? Or is it just floating around, no longer developed. 
Looks Like Floating Out There 
Looks Like Floating Out There 
Guessing this one is the one people are using texmex_34 
This is more of an engine question but does quakespasm or vkquake support increasing the playback speed for animated textures using the +0, +1, +2 naming convention?

DP lets you circumvent this with Q3 shaders but i'm just curious if there's a more universal option for having an animated waterfall look smoother 
Not that I know of, but there's a tutorial on Preach's site about using func_wall's on-trigger function (switching texture between two sets) to double the framerate from 5FPS to 10 using two sets of premade textures. 
I Should Add.. 
That the method in the tutorial is a bit convoluted, because it describes how to get the effect in unmodified Quake. It would be much better to achieve the same effect with a simple mod that added QuakeC code to perform the switching between the textures. 
I'm Using Func_illusionaries 
So i guess i'll just deal with the low framerate.

I have another question/problem - I made a huge lift in my map that goes up slowly, it's a door -

It has items on it, but seemingly at random while the player is riding it he will get snagged on it and take damage, and send the lift back down.

Is there any reason for this/workaround? I know i could make it so you ride it down slowly instead of up, but I have to redesign it if i do that. I wanted to avoid using a func_train but if it's some sort of engine problem I'll switch.

I'm using quakespasm btw 
Wait What? 
I switched to a train and the collision does not match up with the position of the train - i tested in quakespasm and vkquake and it's broken in both, but oddly enough in darkplaces the collision of the train is correct

I have no idea what's going on 
Check for an "angle" or "angles" key on the func_train and delete it if there is one. 
I feel like a dope, that was it. Leftover from converting door > train

Check Your Server Fps Too 
Another thing that can cause weird physics glitches, like the one you had with your elevator, is setting the server fps too high in the config (default 72, if I recall correctly). When I use Quakespasm, setting it to 150 still seems to allow everything to work correctly. 
I Actually Kept Quakespasm Running At 72 Fps 
It still would happen. Sometimes the train gets caught too and does a point or 2 of damage but it's alright since it doesn't break the whole sequence 
I had the same stubborn func_plat that caused me headaches to solve.
Glad finding the solution here.

(for the the func_plat head) P: 
Lava Alpha 1 
It's been asked many times, but here I go. There is a worldspawn key to set the lava alpha for that particular level, right? Which one is that, again? 
Meet The "alpha's", Hehe (Hope This Is Correct) 

----- Alpha Options -----

water_alpha(string) : "Water Alpha" : : "Set the transparency of water (ex .70), which are brushes textured with a water(ex *04water) texture. This setting tranfers directly to the other 'liquid' types and teleporters, UNLESS you are using an engine that supports individual 'alpha's' for each(see below). NOTE - Defaults to the players own 'r_wateralpha' settings if no value is assigned."

lavaalpha(string) : "Lava Alpha" : : "Set the individual transparency of Lava, brush solids textured with a lava(ex *lava1) texture. Default inherits the 'water_alpha' setting. If 'water_alpha' is not set then it defaults to the players own 'r_wateralpha' setting."

slimealpha(string) : "Slime Alpha" : : "Transparency of Slime, works the same as 'lavaalpha' except for solids textured with a slime(ex *slime0) texture."

telealpha(string) : "Teleporter Alpha" : : "Transparency of Teleporters, works the same as 'lavaalpha' except for solids textured with a teleporter(ex *teleport) texture."

This works for me and I believe it to be accurate but if it is not, please let me know otherwise. 
I Forgot To Bold This... 
... and it threw me when I was testing:

IF 'water_alpha' is NOT set, then it defaults to the players own 'r_wateralpha' setting."

That means, that to set lavaalpha, it IS necessary to set a starting water_alpha to get the results you desire! 
Sorry For The Empty Post Above 
Is this Quakespasm? Do these work in other engines? 
Yes, Quakespasm. I just assumed it was a QS related question since it was a specific lava alpha question, maybe that was wrong?

I tested with DP, FTE, AD-MOD/QSS etc... I only remember I had mixed results, not the specifics to what each one did upon map load. 
Thanks, But 
I hope I can still set water_alpha 0.5 and lavaalpha 1, transparent water and opaque lava. Will try later. 
Water_alpha Is An AD Feature 
It works on any engine, but only with the AD mod.

Quakespasm and MarkV both support "_lavaalpha" and "_wateralpha" worldspawn keys. These work on any mod includong id1. This is relatively new (last 2 years ish) and not sure if any other engines recognize these keys. 
Really Wish I Could Edit My Post, Grrrr 
I should have used my modified version of Daz's FGD for reference, doh. I forgot the subtle differences.

Which has the correct entry for wateralpha, which is:

wateralpha(string) : "Water Alpha" : : "Set the overall transparency of liquids, default = (1.00)"

This I just tested with stock id1. No underscore needed at all?

Apologies for the confusion. 
Just checked MarkV and QS source, they will both accept underscore or no underscore. 
What About Telealpha For Mark V? 
In my map it's not recognizing it? 
MarkV Doesn't Seem To Support A Telealpha Key 
I think were technical reasons for not doing it.

Mark V has automatic underwater transparency detection (which isn't hard to implement, btw --- I told qbism how to do it and he added it qbism super8).

But the underwater transparency test cannot be applied to all teleporters because a small teleporter might not even materially affect vis.

Recommendation: Add automatic underwater transparency to Quakespasm (you'll like it) and then also remove support for tele-alpha.

Qbism added automatic underwater transparency to super8 because if a map isn't water-vised, honoring the user's r_wateralpha value (unless r_novis 1) is just silly looks horrible.

If you add automatic underwater transparency, you'll never see that ugliness ever again! 
Original Id1 Wads 
#14672 #14678
"Are the original id1 wad files somewhere? I wanted to re-compile all the maps to try this but got a lot of missing textures when I used wads from my collection.


For example: I was also looking for the original wads and after finding these two posts I decided I was bored enough today to do this:

I found that the available METAL.WAD had only 99 textures in whereas mine now has 144.

I opened each original map from Romero's source and then made a list of which maps used which wads. I then extracted the textures from each map as its own named wad. After that I merged all the wads into their correct wad according to the list I made.

Adding these to /Trenchbroom dir/gfx now allows all the source maps to be textured without having to open Quake101.wad or similar afterwards. 
I always found the lacking textures super annoying, but oGkspAz, you have finally fixed the problem that has annoyed me for so long.

Thank you thank you thank you! 
Help, I Am About To Release My First Map But I Have Some Problems 
Ok, so I am a long-time Doom mapper and have recently taken up Quake mapping as well. I like it a lot and you can expect to see more stuff from me. Forgive me if I come across as a massive noob. I still feel like an outsider.

I have two problems that prevent me from releasing the map:

First, I have a func_door descending lift but whenever I step on it it only goes 48 is driving me nuts.

Second, the surface of the lift and a brush near it are acting very strangely. If I just walk on them then it alright but if I jump, I get instagibbed. I don't get it...

Would someone mind taking a look at the map? I could also use some feedback on the map itself.

Now I don't know how to package the thing. I just use the compiler but when I drag the .bsp file in Quakespasm, it crashes, so I will just upload the .bsp, .map and .WAD files that I used in a RAR. Again, excuse my noobishness.

I hope you will enjoy the map. 
func_door descending lift but whenever I step on it it only goes 48 is driving me nuts.
func_door will move the extent of the bounding box, minus the "lip" value (but if lip is unset or 0, it uses a default value of.. 8, I think?).

Easiest fix is probably to add a "pedestal" to the lift to give the overall func_door the right height.

If I just walk on them then it alright but if I jump, I get instagibbed.
Check that your host_maxfps cvar is not set above 72. If it's too high elevators will hurt the player. 

Yay, that worked. I knew it had something to do with the bounding box!

It is not set above 72. I have an instagib trap in a nearby room but I checked and there are none of the brushes going in the affected room. Really werid. 
You get gibbed when jumping there is because of the way the trigger_hurt is done. The size of trigger volumes is always determined by an (axial) box around all of the brushes it's made of. In this case, the trigger consists of two brushes, a big one and a smaller, but the touchable volume spans across both. Check with r_showbboxes 1. You need to make it two trigger_hurt entities, one for each brush; then the space above the lift will be unaffected. 
Got it!

Now how do I package the whole map so I can share it? 
You'll want to name your .bsp file in all lower case, no spaces or special characters. You will zip up the following in an archive:

1. your .bsp file (the map)
2. a readme.txt file. please name it <yourmapname>_readme.txt This explains what your map is and any specific info you want to share including your email or social media contacts.
3. it's customary but optional to include your .map file (it's considered polite in these circles.)
4. if you have any colored lighting in your map there will be a .lit file with the same name as your bsp. Make sure to include that as well.

Congrats on making a map!! 
Hey dumptruck! Your YouTube videos were very helpful in making this!

What about the .WAD files? Or are they included in the BSP? 
Here is a link to the final map if anyone is interested in playtesting. 
Seems like a good first effort. Though unfortunately it's pretty much unplayable currently. The map is unsealed (leaks) and unvised - this is something you must address before the final release. In addition, there are many issues concerning entity placement: nine items (including a grenade launcher) fall out of the level, and a large number of monsters are being reported as partially stuck in geometry. Check the map with developer 1 and you'll see all the warning messages in the console:

walkmonster 'monster_ogre' in wall at '768.0 -80.0 265.0'
walkmonster 'monster_zombie' in wall at '-784.0 -704.0 41.0'
walkmonster 'monster_zombie' in wall at '-352.0 -400.0 41.0'
walkmonster 'monster_ogre' in wall at '528.0 -1008.0 489.0'
walkmonster 'monster_ogre' in wall at '296.0 -1072.0 488.0'
walkmonster 'monster_ogre' in wall at '368.0 -976.0 489.0'
walkmonster 'monster_ogre' in wall at '296.0 -1240.0 489.0'
walkmonster 'monster_enforcer' in wall at '632.0 -952.0 296.0'
walkmonster 'monster_ogre' in wall at '224.0 -1288.0 184.0'
walkmonster 'monster_ogre' in wall at '-2400.0 -1472.0 -424.0'
walkmonster 'monster_ogre' in wall at '-1704.0 -1880.0 -72.0'
walkmonster 'monster_ogre' in wall at '-2224.0 -2288.0 -72.0'
walkmonster 'monster_ogre' in wall at '-2528.0 -2032.0 -72.0'
walkmonster 'monster_knight' in wall at ' 32.0 -1808.0 25.0'
walkmonster 'monster_knight' in wall at ' 96.0 -1808.0 25.0'
walkmonster 'monster_knight' in wall at '-32.0 -1808.0 25.0'
walkmonster 'monster_knight' in wall at '192.0 -1840.0 25.0'
walkmonster 'monster_knight' in wall at '128.0 -1840.0 25.0'
walkmonster 'monster_knight' in wall at ' 64.0 -1840.0 25.0'
walkmonster 'monster_knight' in wall at ' -0.0 -1840.0 25.0'
walkmonster 'monster_knight' in wall at '-64.0 -1840.0 25.0'
walkmonster 'monster_knight' in wall at '-128.0 -1840.0 25.0'
walkmonster 'monster_knight' in wall at '-160.0 -1872.0 25.0'
walkmonster 'monster_knight' in wall at '-96.0 -1872.0 25.0'
walkmonster 'monster_knight' in wall at '-32.0 -1872.0 25.0'
walkmonster 'monster_knight' in wall at ' 32.0 -1872.0 25.0'
walkmonster 'monster_knight' in wall at ' 96.0 -1872.0 25.0'
walkmonster 'monster_knight' in wall at '160.0 -1872.0 25.0'

bonus item 'item_shells' fell out of level at '624.0 -48.0 22.0'
bonus item 'item_health' fell out of level at '216.0 -1312.0 166.0'
bonus item 'item_spikes' fell out of level at '-2240.0 -576.0 -410.0'
bonus item 'item_spikes' fell out of level at '-2016.0 -576.0 -410.0'
bonus item 'weapon_grenadelauncher' fell out of level at '-1760.0 -992.0 -378.0'
bonus item 'item_shells' fell out of level at '-1632.0 -1280.0 -658.0'
bonus item 'item_shells' fell out of level at '-2544.0 -1648.0 -202.0'
bonus item 'item_rockets' fell out of level at '-1296.0 80.0 38.0'
bonus item 'item_rockets' fell out of level at '-1264.0 80.0 38.0'

The monster in wall warnings may not be critical in most cases (usually if placed too close to a wall or ceiling - have at least 4 units space between), but it's still a good idea to try to fix it.

Apart from that, it seems there are no difficulty settings whatsoever and a very large enemy count to the point where at least the entire upper (outside) part feels extremely overcrowded and unfair - and especially since most of them seem to wake up all at once.

I didn't play the map properly in light of the aforementioned issues, but my initial thought: I don't really like it when enemies spot you and attack the very moment the map starts, at least if it's without warning and they spawn close by. I would remove all monsters from the start room; maybe put them in the room to the left (partrolling maybe?). This would have the benefit of keeping them from opening the door to the right and making even more enemies wake up right away.
The population in the outside area should be thinned out somewhat, or made to wake up in waves (e.g. "ambush" spawnflag), or the ones on the battlements only appearing at a later point when the player has cleared the majority of enemies in the area (e.g. by having them move up from holes on top of the wall or teleporting in). As it stands, it's pretty messy and bullethell on top of being low on health and ammo at the start. 
Wasn't supposed to come across as bashing the map, just highlighting some things to improve for the next beta. 
I'm Having Problems With My Map (compiling). 
At first my map compiled with no lights at all and in the end it didn't compile at all.

I'm making it in JACK (I'm too used to Hammer and it's like Jackhammer) and compiling in TrenchBroom or Quark (because JACK fails to create .bsp file). TB can't launch the map and Quark gives me the error: «SubdivideFace: didn't split the polygon».

Could anyone, please, take a look at the map and say what's wrong with it?

Link to the .map file:

P.S. It's obviously not finished. BTW, placing buttons made it crash for some reason and triggers don't seem to work. Golden key changes position for some reason and other weird shit only here, only now.

P.P.S. Quark log:

5227 leaffaces 4806 nodefaces ************ ERROR ************ SubdivideFace: didn't split the polygon

!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-! Build failed, because it did not create the (+BSP) file: D:\Steam\SteamApps\comm on\Quake\tmpQuArK.\maps\pipe_dream.BSP Build failed, because it did not create the (+PRT) file: D:\Steam\SteamApps\comm on\Quake\tmpQuArK.\maps\pipe_dream.PRT

_________________________ GO ! (textures+build+Quake) _________________________

D:\Steam\SteamApps\common\Quake\tmpQuArK> "E:\Закуток Разраба\GoldSrc Games\J.A. C.K\quake\qbsp.exe" maps\

Quake BSP Compiler (build Oct 8 2015) ----------- qbsp ------------ qdir: D:\Steam\SteamApps\common\Quake\ gamedir: D:\Steam\SteamApps\common\Quake\tmpQuArK\ outputfile: maps\pipe_dream.bsp --- LoadMapFile --- maps\ 465 brushes 41 entities 48 miptex 233 texinfo building hulls sequentially... --- Brush_LoadEntity --- 445 brushes read ---- CSGFaces ---- 2845 brushfaces 7194 csgfaces 2277 mergedfaces ----- SolidBSP ----- 3247 split nodes 1546 solid leafs 1702 empty leafs 0 water leafs 6231 leaffaces 5777 nodefaces ----- portalize ---- ----- FillOutside ---- 806 outleafs ----- SolidBSP ----- 2480 split nodes 1309 solid leafs 1172 empty leafs 0 water leafs 5227 leaffaces 4806 nodefaces ************ ERROR ************ SubdivideFace: didn't split the polygon

!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-!!-! Build failed, because it did not create the (+BSP) file: D:\Steam\SteamApps\comm on\Quake\tmpQuArK.\maps\pipe_dream.BSP Build failed, because it did not create the (+PRT) file: D:\Steam\SteamApps\comm on\Quake\tmpQuArK.\maps\pipe_dream.PRT 
SubdivideFace: didn't split the polygon typically means that there's a face somewhere on which the texture is scaled too low for QBSP to handle. For example a small face/brush with a texture scale of less than 0.25, or something along these lines.

It seems you use the compilers that come with Quark. I don't even know what those are, but they're definitely outdated. Try some newer ones, e.g. these, and it should either take care of it right away or at least give you some indication of where the problem originates. 
1st thing I did is changed textures to default wall and checked scale, it's 1.0 for everything.

Quark uses the same compilers as JACK and TB. 
JACK log

** Executing...
** Command: Change Directory
** Parameters: D:/Steam/steamapps/common/Quake/pipe_dream

** Executing...
** Command: Copy File
** Source: D:\Steam\steamapps\common\Quake\pipe_dream\
** Destination: \

** Executing...
** Command: E:/Закуток Разраба/GoldSrc Games/J.A.C.K./quake/qbsp.exe
** Parameters: "\pipe_dream"
Quake BSP Compiler (build Oct 8 2015)
----------- qbsp ------------
************ ERROR ************
SetQdirFromPath: no 'maps' in \pipe_dream

** Executing...
** Command: E:/Закуток Разраба/GoldSrc Games/J.A.C.K./quake/vis.exe
** Parameters: "\pipe_dream"
Quake VIS Compiler (build Dec 11 2013)
------------ vis ------------
************ ERROR ************
Error opening \pipe_dream.bsp: No such file or directory

** Executing...
** Command: E:/Закуток Разраба/GoldSrc Games/J.A.C.K./quake/light.exe
** Parameters: "\pipe_dream"
Quake LIGHT Compiler (build Oct 6 2015)
----------- light -----------
************ ERROR ************
Error opening \pipe_dream.bsp: No such file or directory

** Executing...
** Command: Change Directory
** Parameters: D:/Steam/steamapps/common/Quake

** Executing...
** Command: D:/Steam/steamapps/common/Quake/quakespasm.exe
** Parameters: +map pipe_dream

for some reason it launches the old version, no lights. 
I will look at your map this evening after work. I can load it at work but I can't compile it without a lot of trouble. I'd suggest compiling with ericw tools and using Necro's compiling GUI. It will eliminate any issues that may be arising from switching between editors. Here is a PDF I created with step by step setup instructions on page 2.

I'm not sure if you've seen my TrenchBroom 2 tutorials but this pdf if is specific to the Quickstart tutorial. But it's shouldn't matter.

One thing is I am seeing you have wads in 2 locations on your system. I would move them to a common folder and re-link them in your editor of choice. Try to compile with ericw tools and Necro's GUI.

I'd also recommend you watch my Quickstart video as well. In it I recommend setting up a "dev" folder for Quake and show how to do it. 
it seems that some columns caused "integer" trouble. I deleted 'em. Nothing changed. 
@ Dumptruck_ds 
Oh, thank you for the step by step instruction. I'll try it as soon as possible. 
Common Compiling Errors 
I think if you take Negke's and my suggestion and ensure you use ericw's tools to compile you will be able to supply us with better information overall. Please try that and share the .log files that are generated. 
I found that some portion of errors was tied to the root folder name (сyrillic). After I changed it, EricW made me a .bsp. (Still no lights. And keys dissapear for some reason)

I adjust the archive with logs and .bsp.

It's a middle of a night here, so I'm signing off. Again, thanks for the quick answers, wasn't expecting this. 
Hey we're getting somewhere. I'm assuming ericw found some leaks. I loaded up the map in TB2 and the level in Quakespasm.

First off you want to run Quake with the +developer 1 command line option or type developer 1 in the console and then restart. Either way you will now see much more information in the console. You can dump the console to a txt file by typing condump in the console. Here are your missing keys and items:

Bonus item fell out of level at '1920.0 1856.0 230.0'
Bonus item fell out of level at '1700.0 1844.0 6.0'
Bonus item fell out of level at '2272.0 1952.0 222.0'
Bonus item fell out of level at '2132.0 2144.0 -186.0'
Bonus item fell out of level at '1684.0 2144.0 -186.0'

In TrenchBroom in the View menu select Camera > Move Camera to... and type in those coordinates above. You will then be "inside" the entity. In this case your keys and other items are too low to the ground or close to other items so they've fallen out of the level.

There are lights in your level. HOWEVER, you have a light key in the Worldspawn that is making the entire level lit at 200 regardless of your light entities. If you delete that key your lights will work.

The gold key up top I think is being pushed down into the world by the func_plat you are using.

The level is pretty nice. I hope you keep working on it. We're happy to help. 
Hey we're getting somewhere. I'm assuming ericw found some leaks. I loaded up the map in TB2 and the level in Quakespasm.

First off you want to run Quake with the +developer 1 command line option or type developer 1 in the console and then restart. Either way you will now see much more information in the console. You can dump the console to a txt file by typing condump in the console. Here are your missing keys and items:

Bonus item fell out of level at '1920.0 1856.0 230.0'
Bonus item fell out of level at '1700.0 1844.0 6.0'
Bonus item fell out of level at '2272.0 1952.0 222.0'
Bonus item fell out of level at '2132.0 2144.0 -186.0'
Bonus item fell out of level at '1684.0 2144.0 -186.0'

In TrenchBroom in the View menu select Camera > Move Camera to... and type in those coordinates above. You will then be "inside" the entity. In this case your keys and other items are too low to the ground or close to other items so they've fallen out of the level.

There are lights in your level. HOWEVER, you have a light key in the Worldspawn that is making the entire level lit at 200 regardless of your light entities. If you delete that key your lights will work.

The gold key up top I think is being pushed down into the world by the func_plat you are using.

The level is pretty nice. I hope you keep working on it. We're happy to help. 
The map works well on my end but I will keep in mind what you said.

I am still getting used to how Quake feels. I mean AD got me back into it (didn't even know Quake had a mapping community before that!) so I kinda designed my maps like I would design my Doom maps. I am still getting used to tougher individual enemies and the slower speed. 
Mission Accomplished 
Thanks for all your support, it works fine now! Some trouble with the key I so wanted to place under the moving platform, but otherwise – pretty smooth.

I love making levels, but rarely finish them :).

I was so used to leaks and light surfaces overload that I assumed that there's a trouble with the light by the default xD.

P.S. Now the map looks less embarassing :

P.P.S. I must say it's really increadible work you're doing for Quake community. It's hard to belive that the tools are still being made. 
Glad this is working now. I have faith in this level. You should finish it.

SleepwalkR and ericw are doing a great job developing TrenchBroom and keeping us all mapping after 21 years... amazing. 
Free Space Around Entities 
BTW, how much space should be left around items and monsters for them not to stuck / to appear?

Dogs in my level glued to the walls of their kennels (64x128x64) and some items don't respawn if placed too close to the walls or to the other items, but not always. Like, for example, armor and rockets goes fine together, but rockets and nails don't and niches are apparently very item-unfriendly.

This key, I was speeking about early, finally it got right where I want it, but it's like pure luck. 
All monsters are Shambler-sized in their collisions, to the best of my knowledge.

64 width, 64 height 88 tall -- says the engine source code. 
That can't be right, this fullbright box compiled just fine and didn't drop the enemy into the void with an enemy's hitbox- listed as 32x32x64 in Trenchbroom- a single unit away from the wall. Making it touch the wall still spawns it but it ends up stuck (an error is shown in the console when using developer 1), but even one unit is enough to leave it free to turn around and run. 
It might not be right. I don't work with the qbsp tools. There may be other factors in play than just what the engine says is the monster hull, which is hull->clip_mins: -32, -32, -24 to hull->clip_maxs: 32, 32, 64. 
There are two bounding box sizes: 32x32x56 and 64x64x88. There needs to be some space around and above them for the monsters to be able to move and not produce a warning (or for items not to fall out) - they must not touch a wall or ceiling, but they can be placed right on the ground. As Spud pointed out, a space as small as 1 unit can be enough. 
Quake Collisions And Placing Stuff 
Vertical, have at least 1 unit of space above the heights below. 2 is recommended. The origin(center point) can be put exactly on the floor, though for monsters it is best to put 1 or 2 units above the floor at least to avoid potential position rounding errors sticking them through the floor (should be rare in newer editors).

Horizontal have at least 2 units of space beyond the sizes below.

Items are an effective 62 units tall. Items are 32x32x56 tall and get moved 6 units up on level start so that they can be "dropped" straught down to instantly put them on the floor and also check to see if they are below the floor and thus "fell out of level".

Monsters have 2 different collision hulls regardless of the bounding box sizes shown in Hammer/Worldcraft or other which negke mentioned above. The bounding box size for monsters shown in the editor should be close. Most smaller or narrower enemies use 32x32x56 (hull1), the larger enemies such as shamblers and vores use the 64x64x88 (hull2) size.
Dogs are a little wierd in that they have same size collision as shamblers, BUT...

There is a 4th layer of collisions...the qc code can define any bounding size it wants for an enemy. The engine rounds this size to the hull closest to either of the 2 enemy sizes for all collisions except raytracing and bullets. The qc lets, for unstance, giant monsters such as the gug, vermis, or boglord, get shot more easily in a way that is believable rather than only having bullets affect it right in the center 64units. Also tiny monsters such as fish or spiders don't get hurt if you shoot the empty air above or below them even though there could be 20-30 units of collision hull above these smaller enemies, shooting the air doesn't hurt them.

That is why, even though enemies appear to fit in niches in the editor and make sense from where you can shoot them, the tiny enemies still all need 57 units of vertical space. You can cheat it visually by using func_illusionary so long as the player can't reach the niche. 
That explains a lot. 
Odd BBOX Sizes 
Also note that entities with bboxes will collide with each other according to their actual size, even though when colliding with BSP entities they snap to the two fixed sizes discussed above. Useful applications of this fact are left as an exercise... 
Possibly A Stupid Question But 
Do I need a different gbsp light and vis for Quake II or do the ones we use for q1 work? 
They're Different For Q2 
I think these are the most commonly used ones: 
Falling Through Part Of A Brush 
First up: swear I had the screenshots folder selected but oh well. I have had a quick look through mapping help re: nonsolid brushes but not finding this issue atm.
My brushes look like this in TB2 (view from above)
If i move past the vertical line here I fall through the brush (view from below)
I am using Ericw's latest tools. 
Not sure but you can try downgrading to a different version of the tools first just in case. 
Are the brushes a func_ of some sort? Or plain bsp. Workarounds: clip to split them up into diferent brushes, make new brushes from scratch, make another brush inside them that is 1 unit smaller all around...or to add a clip brush around them.

Check that they DO NOT have an origin key. 
This is an annoying one. Assuming these are worldspawn brushes, it's a qbsp bug, but usually it can be worked around. Try the command in TB to snap the selected selected brushes to integer. Try turning the selected brushes into func_detail (not a direct fix, but it will cause qbsp to chop that area of the map in a different order and might randomly fix the problem) 
Re: Non Solid Brush 
I'll have to give these suggestions a go but I'm half asleep atm. Will update when I do. Thanks 
Hey OGkspAz 
QBSP really doesn't like 45 degree angle world brushes and generally does stupid things when you want to use them to close a space.

In this instance why not make the platform a func_wall to remove it from QBSP completely - I mean the whole chunk selected in red in your first image.

This won't affect the structure or visuals and will shorten the build time by a few microseconds. It might make the red armour drop through to the bottom floor though (can't remember) if so then a small lump of normal geometry inside that platform will fix the problem without making QBSP pee on the carpet. 
Hi, I'm new to this forum.

I've been having some issues, running quakespasm with qompiler/ericw (+fgd) & j.a.c.k.

I have few questions :

1. Exporting bmp 256 color 128x128 pixels from photoshop, and importing (ctrl+e) in wally, exporting quake 1 wad (the texture appear to be right in wally, but totally wrong in j.a.c.k. like if the color were inverted, or dark).
When I compile the map and run the game, the texture appear to be right.

2. When launched qompiler.bat (after un-zipping the latest compatible version of ericw, which is "0.15.10", when I click 1, 2, 3 or 4 (for the different commands in the menu) nothing happen, but I hear a "beep" coming from the cmd window.

3. When I compil a map, quakespasm.exe keep being deleted from the quake folder, for no reason.
I've tried with both "Don't run the game" disabled and enabled (this is when using j.a.c.k. for compiling).

Many thanks and brush well ! 
Starting Something New Seems To Be The Hardest Thing. 
After 14 years making maps (in my case, mostly for Unreal), I seem to have run dry of new ideas. How do you guys come up with new layouts? Everything I try seems to go nowhere or be severely flawed (instead of severely flowed, eheh). 
1. I think what youre seeing is the difference in "gamma" between Wally, JACK, and your Quake engine. (What engine are you using?)

2. Do you have qompiler in the directory that holds the bin/doc folders for erics tools?

For your first use, youll need to make a configuration by following the on screen prompts and entering the options you wish to use. Reference the doc folder for the various options you can use in Erics tools.

3. Im not sure why qompiler would be kicking quakespasm.exe? Its only set to manipulate files directly related to the compilation process. You mention using "dont run game" which is an option in JACK during the compilation process. So perhaps we should start from step one and see if we can spot where things are going wrong.

For starters get your .map file and qompiler in a folder with the "bin" and "doc" folders from Erics tools.

Perhaps call it "Qompiler"

So the hierarchy would look like this:

.map files

Run Qompiler. If you dont have a config saved youll need to choose option 1 and follow the prompts. If you havent a clue what to enter here its likely you can skip entering ANYTHING and just hit enter through the various prompts Qompiler gives you.

You can reference the files in the doc folder for information on the various arguments you can pass to Erics tools.

If you didnt have erics tools, itd tell you. if you dont have any .maps..itd tell you.

When Qompiler is done running it puts your compiled maps into a folder named "maps" and moves all the source .maps into "qompiled" 
btw, i wrote Qompiler so feel free to ask questions specific to it. 
I've had this same issue a few times recently. The ideas aren't coming or I hate what I am attempting. One suggestion I'd make is play more levels you love and try to discover what it is you enjoy about them.

Another suggestion would be to try a jam. There was a Speedmapping Jam last week and there's a 100 brush jam going on right now that has a few weeks left. Working within limitations may be a good way to snap out of a creative rut. 
Thanks for the reply, and for Qompiler.

I was pressing [1], [2], [3] and [4] instead of [N], [L], [E] & [Q].

I still have random issues, but like usual when setting a new engine, a lot of hassles comes with it. Time to handle the tools.. 
Yes, I'll do that. I've played less and less as time went by, this is probably a reason I don't spontaneously have interesting ideas anymore, I need to get back into the game to get back into the right mindset.

I'm not a fan of contests, but I did one a few years back and it was a fun experience (size limite, make a map weighing 512 Kb or less), but my method when I'm on such tight time constraint is to shift through my folder of abandoned projecs and drafts and conflate a couple half-completed levels. 
Multiple Targets 
Probably has a simple workaround, but say I have a monster I want to target a trigger_counter for a door and a path_corner for a patrol. How do I do this? Only one target field in an entity. 
Have a continuous trap spikeshooter attacking a func_button wih health tucked away in a box far off where the player can't hear it.

Put a func_wall blocking the shooter.

Add a killtarget to your monster that kills the func_wall.

There might be a simpler info_notnull hack but I can't remember one atm. 
Holy Shit 
Are you serious? Over 20 years of Quake mapping and no simple workaround for more than one target? 
You Could Wait 200 Years 
but the id1 progs.dat isn't going to change.

If you include customs progs, then lots of them have supported target1, target2..... etc. 
Im Using Quoth 
I still know nothing of progs. Just figured out how to map with Quoth today so you can see how little I know of Quake mapping. How could I set up progs to add targets to entities? 
You Can Do It In Qouth 
Thanks. I thought Quoth would have something for it. Preach to the rescue as usual. 
Still A Little Confused 
Preach's article makes no mention of how to actually use the feature. Do you just add the key manually to the entity or what? I tried adding target2 to my monster to the path_corner but it doesn't work. 
path_corner is handled differently to usual targeting - try just using the default "target" field for the path_corner and the extended "target2" (etc) fields for things that trigger on monster death. 
That Does The Trick 
Thanks. Why or how are they handled differently? 
A target field can always trigger multiple entities that share the same targetname, right? I think the issue there is probably just with the path_corner... if it's not the first entity with that targetname that find() comes across, then the monster won't patrol.

I wonder if that particular multiple target situation would work even in id1 progs if you could guarantee that the path_corner was lower in the edict table. 
I posted that before refreshing to see the other two posts above.

More for sevin:

When a monster is first "initialized" in the QuakeC code (progs) that shipped with Quake, one of the things that happens is as follows. If it has a target specified, it looks for the first entity it finds that has that targetname. If the entity is a path_corner, it starts patrolling.

Later when a monster dies, if it has a target specified, it triggers any trigger-able entity that has that targetname.

So in the original Quake game code they didn't think about supporting the case where a monster is BOTH patrolling and is ALSO meant to trigger stuff on death.

It sounds like that in Quoth only the original "target"/"targetname" fields are used for that patrol behavior, but all of the new additional target/targetname fields can do other triggering stuff. 
When a monster is spawned, it checks to see if is a path_corner, or something else. If it's a path_corner, it makes the monster start walking straight away, otherwise the monster is told to just stand, which is also the default behaviour if it has no target.

I can only assume (without looking at the quoth QC code) that quoth only does the path_corner check for This sounds reasonable because you do not need to target multiple path_corners, so there's no need to overcomplicate things. target2, 3 and so on are thus assumed to be regular targets, not path_corners. 
I posted that without seeing Johhny Law's posts above 
two ships passing in the night ;) 
#19595-#19600 Re: Multiple Targets 
This can actually be done in vanilla id1, at least for the given scenario- no map hacks needed, just some prior knowledge of entity priority. No idea how it'd work with other entities being targeted, but enemies can be set to both patrol a path and activate a relay or counter on death by simply creating the path_corner first, then creating the relay with the same name. As long as the path_corner comes first in the entity list, the monster will follow the path, but still trigger the relay on death.

Basically, the enemy should target two entities with the same name- a path_corner and a trigger_relay placed in the map after the corner (so be careful if you're deleting or remaking things constantly). If the relay comes first, the enemy will still activate it on death but won't patrol to the path_corners. Here's a webm of an example map (ignore the "holy shit I figured out how to get custom conchars working" kludged HUD) and here's the .bsp and .map themselves. The left and center Grunts have the corner loading first, with the leftmost Grunt also having multiple path_corners (it takes a while for him to get there, though); the right Grunt has the relay first so he just stands there like a dork. All three function properly for the counter. 
Make That Three Ships 
Because I just got ninja'd something fierce, goddamn. 
and yeah, like Johnny Law says, it does appear that a "hack" is possible in id1 where it *would* work when both the path_corner and other targets share the same targetname, if you can guarantee the path_corner comes before all the others in the edict list.

On a related note, ever been killed by a monster who was not previously on a path, but then starts walking towards something after killing the player? That's a monster who had a target, which wasn't a path_corner. When his enemy dies, he starts walking towards this. It's a harmless bug, caused by the rather dumb way in which the "is target a path_corner?" check is performed when monster spawns. 
posted that without seeing Spud's post. I probably din't need to mention the id1 hack a third time :p 
So Many Ships In The Night 
Great info above, thank you all! To clarify, I figured that setting the first path_corner and the trigger_counter to the same targetname would allow them both work (thought I didn't know entity priority matters in this case), but I didn't want to do that. I like keeping my named entities descriptive of the entity and its relevance to other entities, so doing it another way would be better. 
And Another Thing 
Do func_doors trigger themselves at close proximity? I have a func_door set of bars with the GK spawn flag that cover another func_door. Finding the GK lowers the bars, but it also opens the door behind it. Why is this? They are not connected through I/O. I just want the bars to lower so I can walk into the door and have it open as normal. I've tried giving the actual door a targetname connected to a trigger_once that enables once you find the GK, but that didn't work. 
If the doors are physically touching each other, they'll act as linked doors, normally used for double doors that open sideways. Tick the Don't link spawnflag on both and test it again. 
Cool. Yeah it should have clicked with me that the beeping meant you were hitting a wrong key. My bad. :)

Yep just dig into the docs for the tools and youll start to piece things together. Qompilers cool for compiling multiple maps at a time, a bit overbearing for single maps but works all the same. Try getting comfy with JACKs compiling UI before relying on Qompiler. 
That Makes Sense 
But if I set Don't link on the left and right doors and the bars, the doors don't open when I walk up to them. The bars lower separately, but I can't go through the door. 
Does the center door (not the gold key one, the double doors you go through after?) have a targetname? If it does, get rid of it- a door with a name will only open upon being triggered (i.e. by a button), not by the player walking up to it. It's an easy mistake to assume that every entity needs a targetname, but as a general rule, unless it's specifically being targeted by something else and requires one, leave it blank.

A screenshot or .map upload might help too, sort of hard to visualize this in the brain without a reference point to what the door setup actually looks like. 
I Fixed It 
But I'm still curious. Just moved the bars away from the doors, which of course does the trick. Would still like to know what I'm doing wrong to make them work while they're still touching.

Here's the .map with the doors/bars touching and set to Don't link. 
Use "r_showbboxes 1" and you can visualize the trigger volume for your doors. 
Issues With Textures 
I'm having some issues with textures :
I tried with wally and texmex, it seems to come from j.a.c.k. (which is on default). I never had this problem with goldsrc/wad3 & hammer. Ideas ? 
looks like its missing the palette and using some greyscale thing instead. specifically the 'gfx/palette.lmp' file.

make sure that your editor's basedir+gamedir paths are correct (as well as just the wad+map paths). 
I've loaded the quake.pal from j.a.c.k. folder, still it doesn't work (I see white textures).
Would it be possible to bypass quake.pal and use wad3 instead ? (ericw/quakespasm)
Many thanks 
Use It As An External/replacement Texture? 
If I remember the screenshots correctly, since you are so off the "path" of a normal texture just use it as external/replacement. In the editor it will still look messed up but ingame it will be fine. 
Aha, I don't get it.
I tried to keep the install fresh & minimal.
Why do these things tend to get obscure ?
However I got it : the Base Game Directory wasn't set on the right folder (quake main folder, instead of id1).
Those "happy" victories remains me when I was learning how to configure worldcraft 1.1 in the year 2000' without internet connection, at the age of 10. I'm so happy the quake community exist! 
Can anybody give me examples of well thought out combat in long hallways? I'd like to learn how set up a good encounter. Are enemies too weak for open areas, apart from Vores or Shamblers who pose a real threat regardless of placement. 
czg's honey has some good examples of that. The whole map pack is really a masterclass in encounter design. 
Cool! I even played it one and a half years ago. 
I've been struggling with this. I think the key to using weaker enemies are the specific combinations you use.

Knights rushing the player in a swarm are actually dangerous working as a unit. Same with Scrags. The more the merrier.

Adding multiple grunts above and farther from the player to any encounter has worked for me as they chip away at the players health fairly quickly no matter what is going on near the player.

I'm no expert, but hope this helps. 
What I like to do is try and grenade either scrags or knights as those die one shot with a direct hit, it's a nice skill to practice.
Guess that trial and error is the key to encounter design. 
Getting A Model To Animate (Quoth) And Adding Skins. 
I've been making a few models using Blender for my latest map, and I have one of them animated now. Its just a prop with a few frames. There are no frame groups set up on it (I don't think this can be done in Blender) I want to make it animated in quoth using custom mapobject entity. Is there anyway to specify a series of frames without having frame groups set up.

Also I want to add a second skin to the model, and again it seems Blender only exports the mdl using the last active skin in the UVmap. Is there a simple way to do these things, or do you have to use python and qmdl? 
Cont'd From 19634 
To elaborate a little, I'm trying to get the butterfly model seen in this pic:

To animate like this:

I'm using the mapobject_custom entity which has a 'frame' key but I have no idea if there is support for multi frames or what the correct syntax is for listing them. I think it would animate automatically, but I don't have any framegroups set. 
Ok, so I've used qmdl and Preach's tutorial here:

and I finally got the model to animate in Quoth with custom_mapobject.

A huge mess was caused by the fact that Blender exports do not have a frame 0. I grouped the frames in qmdl from 0 to 10 and the model appeared as an ugly mass of pixels. This confused me because the same model animated from frames 0-10 in AD. I edited again in qmdl this time grouping frames 1-10 and the model now loads and animates perfectly in Quoth if you enter frame 1 as the start frame. What an exercise! 
In Blender 
Set the start frame to 0 and the end frame to 10 in the Timeline editor. If you leave it at the default 250, your model will be unnecessarily bloated. 
An Exercise In Frustration... 
Thnx @Qmaster. Yeah there are so many ridiculous little nuances to making a model for Quake and then getting it to animate. I really did not like having to install Python and enter commands into it with the qmdl plugin. It feels so detached an out of date with how you can just make a model and slap it into your unity games today. But thanks to Preach's tutorial I just did a monkey see monkey do approach and it works now.

I should go back in to blender and start the frames at 0 and export again to see if it works better that way, apparently Quake wants a 0 frame for some reason... 
Select Next Level, Screenshots 
I've run into two small problems with a new map:

1) In a multiplayer game after the timelimit expires the next map that gets selected is from the single player campaign. I want it to continue with my map though. In my previous maps (made with worldcraft) I somehow managed to set this somewhere but I can't figure out how with TrenchBroom.

2) I'd like to take screenshots in Quakespasm without the weapon visible but don't know how to go about that either.

Any ideas? 
1) You can place a trigger_changelevel somewhere outside the map and point it back and the same mapname. Though I think standard behavior is that a map without any changelevel trigger will always repeat (unless the server has some map list cycle set).

2) Console command r_drawviewmodel 0 
Thanks negke, I'll try that. I had this problem on a ProQuake server and my local Quakespasm, and only with my new map. Thanks again. 
Worked like a charm, thanks again, negke! 
Alright, the weapon model is gone too, but embarrasingly I still need to figure out, how to take the actual screenshot. Man, it's been a really long time... 
You Might Have Already Figured It Out But... 
F12 is the key for screenshot in Quakespasm. 
Thanks esrael. I posted a few shots in the terrafusion discord. 
Hello, there are textures with alpha channel on some maps, usually used for cobwebs and grass. How do they do it? 
Alpha Channel Answer 
Textures in a .wad file, whose name begins with { and use the garish pink color(255?) of the Quake palette will, in engines that support the feature, be rendered as "alpha". 
I Should Have Included This... 
These are called fence textures. You'll want a texture in your wad that begins with a bracket "{". Here's a wad with a couple of grates:

1. make a brush
2. make that brush a func illusionary
3. apply the skip texture to the whole brush
4. then apply the fence texture to just the faces that the player will see
5. use clip brushes to enable collision on the brush if needed. i.e. walking on a grate you would want this.

My map from jam 9 jam_dumptruck has an example. It's in the map source folder. The grates are near the info_player_start (map requires Quoth to play.)

Good luck! 
Since I'm so full of fail tonight a third, and final(?) post on this!

In editor create a brush, apply a "skip" texture to the whole brush then select a single face and apply your "alpha'd"(cobweb) texture.

Now, turn that brush into a func_detail_fence or a func_detail_illusionary(non-solid) and add a key/value pair of: _mirrorinside "1"

This requires you to use ericw's tools for it to compile correctly.

If you need any more specific help than what I have stated... ask away. 
Thanks to all. It's amazing how helpful this community is. 
Thanks to all. It's amazing how helpful this community is.

Does vanila Quake have grates/fences textures? I'm asking, 'cause I don't recall it to, and default wad has none. 
It does not, and vanilla Quake doesn't actually support alpha-masked geometry textures, only 2D elements (HUD and sprites)- one of the few if any objective steps backwards compared to Doom. 
Why they is black? How fixed it? 
It's in quakespasm.
In fitzquake normal light, but for this monster only.

I think because they stand on func_train. In the air, far from surfaces, the monsters are also black in both engines. 
They are lit by the point directly under them. Either add a light source on the ground below inside a black func_illusionary brush or possibly add _minlight to them. 
I have a brush of the sky that the floor is made of. I made the bottom surface with a different texture. It returned normal lighting 
Create A Func_illusionary Floor With Sky Texture 
About 16 thick and 16 above the floor with a normal texture. 
there is a TF channel 
I'm wondering if there is any way to set it so when a level is started, it plays a song from quake, I know there is a property for entities called "music" but i don't know what to use the property on if that is what you use for the music 
In Vanilla Quake Or A Mod? 
Also, i have the music files working in the normal game 
Add a sounds key to worldspawn with a number for the track you want.

sounds | 3 
I've been working on a death match map that has moving parts, I've noticed that for some reason, things aren't targeting properly. I have 2 moving doors that both use buttons, one of the doors has the targetname da1, with a button targeting it with the target da1, then I have a door with the targetname db2, and a button with the target db2, and what happens is one of the buttons doesn't open a single door, whilst the other button opens both! I need some help. 
This is a very common issue. By default, Quake groups doors which are close by into a single system. If you want to opt-out of this behaviour, you can add the DOOR_DONT_LINK spawnflag (3rd tickbox, numeric value 4) to each of the doors. 
I have another question, why do item_blank entities go through the floor sometimes? 
Bonus Content 
You might wonder why this door linking feature is included. It doesn't seem all that helpful at first, and often confuses mappers (even after they've encountered it before, it's easy to be caught out again!)

But door linking actually has good reasons for existing as well. I'm going to borrow a clear example from Dumptruck's tutorials on Trenchbroom. Take a quick look at theis gold key door setup.

Here, the bars are separated into two different entities, so that they can move in different directions. If they were not linked together, you would require two gold keys to get past, one to unlock the left-hand bars and another to unlock the right!

It's also worth noting that the way that both of the left hand bars are combined into a single entity is crucial to pulling this off. Door are linked if their bounding boxes overlap or touch. The bounding box extends between the left-hand bars, so that they intersect the right hand bar. If all three bars were separate entities, none of them would link, and you'd need three keys to open them all. 
Item Fall Out 
Avoid overlapped items.
Make sure they aren't sticking more than 6 units into the floor.
Make sure there is at least 56 units of vertical space.
Make sure you have at least 1 to 2 units of space on all sides, preferably 4 as a safe minimum.
If you are using JACK/Worldcraft, the fgd file may show the box in an incorrect visual object position relative to the actual origin (look for the X in the 2D views):
•In vanilla Quake, origin is in the bottom left corner
•In AD and other mods, custom items may use the center bottom of the visible item as the origin point instead.
Also, they might fall out if you place an item inside a solid brush such as a door. 
Minor Correction 
Origin in bottom left corner is for ammo and health boxes only; all else use center bottom. 
does anyone have entity definitions for the team fortress mod? 
or at least the entity names? 
22 posts not shown on this page because they were spam
First | Previous | Next | Last
Post A Reply:
Website copyright © 2002-2018 John Fitzgibbons. All posts are copyright their respective authors.