Try fov_adapt 

but not quite as good. 

Good stuff just keeps coming. Separate alphas for the different liquids also? Man, that's great. 

So I made a trigger which triggers a bunch or relays which trigger lights with a staggered delay. I set the relays to have sound but they do not play any. What gives? 

trigger_relay's .qc code is

void() trigger_relay =
{
self.use = SUB_UseTargets;
};

Literally all it does is 'use' (trigger) it's targets. That's it. No sounds or anything else fancy.

--

There's some entity hack stuff you can do to make an info_notnull play a sound, so you could target that and it will play your sound. Give it the following properties:

"use" "train_wait"
"wait" "-1"
"noise" "boss2/sight.wav" (or whatever sound, look in the .pak files for the names)

The sound must be precached, or your map will crash, so make it a sound that another entity in your map plays, that entity will precache the sound for you. For instance, the sound I used was from boss2, who is Shub, so I would need to place Shub in my map somewhere to use the sound. 

Thanks, that works. Was just confused because in the .fgd I got (the one DaZ made for JH) there is a dropdown for sound style on relay_triggers. 

you can trigger a trigger_once/trigger_multiple by giving it a targetname. then you can add any sounds you want to it. use the 'notouch' flag so you can't accidentally walk into it. 

What entity makes the "large Switch" sound then? Like the sound in e1m1 as the lights turn on as you go down the slime room with the 3 buttons. 

Quark tells me "sounds" "3" on a trigger_once/multiple makes the "large switch" sound :)

There's also 2="beep beep" 1="secret" 0=none 

the trigger volumes do. 

 

the jam has really taken a toll on him. :P 

What's going on with the multiple maps in jam6 trying to load CD track 1? It does not exist, first track is 2. Some editor definition file using 1 as default? Noticed it with ericw/tronyn's and warren's. 

Maybe they are hankering for some good old bit screeching. 

Must be a default, I never set it. 

What causes z-fighting and how does one avoid it in creating a map? 

Z-fighting is cause when faces of brushes overlap. In general this will only happen with things like func_door, func_plat etc.

So if you make a door or a platform make sure that none of the visible faces are level with other visible faces. This means that you should model in recesses for your platforms and doors to go into in most cases. 

So what about having two world brushes with overlapping faces that the player can see? Will this ever result in z-fighting? And if not, is there any rule to which of the two faces (i.e. which texture) is seen in-game? 

with world brushes you should not have them overlapping in such a way that parts of faces which will be seen are flush. You don't know and then engine does not know, hence the z-fighting. I think the gl_zfix thing only sets worldspawn to a higher prio than entities. 

Ok, thanks for clarifying. I'm working on structure where it's kind of tricky not to have any visible surfaces overlap, especially without splitting the brushes into tiny components -- but I guess I'll have to figure it out somehow, then.

Thanks again! 

Feel free to upload a work in progress of your .map and I can have a look at it and let you know what might be problematic. 

That's very kind of you, but at the moment I'm still too embarrassed to show anything I've made.

I might take you up on the offer when things look less messy ... but that's going to take a while at my pace. 

shouldn't happen. Here's a test:
http://imgur.com/a/McOtQ#Ce5LmYE

qbsp has a step where it CSG-subtracts each brush against each other brush. I think they're done in map file order, so the first brush I added there clips away the corner of the second brush.

The gl_zfix cvar in quakespasm was pushing each face of bmodels (so func_wall/func_door, etc.) out by a small amount, but it's disabled now becuase it caused arifacts making some secrets visible, and caused mappers to put z-fighting in their maps inadvertently. 

No problem :) 

That is still kinda bad practise though, right? Plopping worldspawn brushes together like that. Esp. since you do not want to keep track of which brushes were placed earlier.

So in most cases like that you should still cut one of the brushes up into smaller parts, right?