I remember this when it first came out, and it was definitely controversial because it's hard to accept what he says if you believe in cleanly built maps.

The non-controversial part is that an increase in visual detail does not always cause an increase in quality of experience -- an obvious example is high-res replacement textures in quake. The harmony of many different ingredients is more important.

The controversial part is "misaligned textures can be better." I think the best way to re-state this so that I can accept the idea, is to say "impressionism can be better" -- this could be because the "magic" of quake and doom is the low-res, low-poly filter that we see that world through, which gives the player room to imagine the rest. It's hard to do this in high-res, high-poly. At low res, 8-bit lighting, there are so many filters that muddy everything up that you can't always see the texture misalignments, they are hidden by dithering and aliasing and palette banding. These filters help the player experience the whole and not focus on the details, since you can't see the details very well anyway. 

The higher fidelity and realism of the graphics the more visible the flaws, not only technically, but artistically.

Maximum realism is the goal of most modern games, but I don't think we're quite there. IMO, it would better better if designers worked within the boundaries of the tech and made cohesive, artistic interpretations instead of attempting realistic duplication. "pushing the boundaries" is not the safest route, as I feel people push them too far. 

How do you make them constantly fire? 

Use trap_shooter instead. 

 

 

Just use trap_shooter. For trap_spikeshooter I think you can set its target to a info_notnull. 

http://quakewiki.org/wiki/Entity_guide wants the answer. 

yeah! 

If memory serves I believe that trap_spikeshooter uses a rotation flag or a up or down firing flag and is dependent on what type of level it is in the worldspawn (lasers in tech levels and spikes for everywhere else).

But I might be wrong on that, it might be possible to put spikes in any level or lasers in any level. I never really played around with them. The timing just seemed a bit too fiddly to get right without a lot of blind tries and recompilings until you got it right. 

Do I remember someone having some rope and/or chain models, and if so, can I pick them up somewhere? 

they were actually .bsp, but does that matter?
Just look into the file at quaddicted.
And Ijed has some chain models, hanging from ceilings, maybe he�s so kind to distribute them? 

are also to be found on the tome of preach, its the cable model with skin set to 0.

Here:

http://tomeofpreach.wordpress.com/2013/09/29/cable/ 

Thanks to both 

is there some sort of specific reason to use plats instead of doors?

I ask because I have a use for one but the plat is a bit finicky so I'm using a door instead. Is this ok or is there something more to plats that I'm missing? 

Plats are slightly easier to set up in an "inactive, then autonomous" way, but when you need better control then a door is the standard solution. 

thank you 

do you set the gravity in a map? I want a low grav map in my quake episode.... 

set in worldspawn.
I don�t know the actual default value, maybe 800?

http://quakewiki.org/wiki/Sv_gravity 

Is to name it e1m8.bsp. 

had a patch for it, I thought.
Maybe in the qc somewhere. 

It may be in the QC as both of the official expansion packs came with a patch to the engine but far more likely that it's in their own custom progs.dat otherwise all of the new features would have been carried over so anyone with a 1.08 Quake engine could take advantage of, lets say particle walkways or rotating objects (or anything else that didn't have a special sound or model attached to it) in Vanilla Quake levels (ie in the ID1\maps folder). 

There's a hack to execute console commands like sv_gravity, but it's messy as it has negative side effects which would have to be worked around.

If you go for a custom progs dat with universal gravity support, be sure to also fix some of the common standard bugs like fish count, death solid frames, and so on. 

That fixes it. No idea if it fixes anything else 

Am I using the wrong combination of compilers, or does using func_detail really make it impossible to compile -onlyents? Building BSP with TxQBSP 1.13 XT -onlyents, func_details apparently don't get stripped out they way they do with a normal compile, leading to a corrupt unloadable BSP with extra bmodels in it.