And I really had no good reason to enable the optimization in the first place, so overall using this experience as an excuse for a patch seems unnecessary. Thanks for your attention though. It's not every day you find a reproducible bug in software everyone's been using with satisfaction for years. :) 

if you're going to do a patch, it might be nice to fix the bug with multispawners and auto-awake monsters. 

Which way round was it broken? It was failing to wake monster with the flag set, right? Not waking everyone without the flag 

yeah, basically nothing happens when you turned on the setting. They would spawn in one at a time, but because they weren't awake, only the first would spawn and the spawner would wait until the space was free before spawning again. 

FitzQ .85 - is it possible to slow the frame rate down by some command? I have an effect that doesn't quite look right and I want to slow it down so that I can see what's happening. (Intel i7 is just too damn quick!) 

This is the multicore timing bug. The only way to fix it is to use a different engine afaik. Quakespasm is a good alternative. :) 

...me trembles with fear...

Wish me luck, and if I don't return I leave my goldfish to Mildred, and my conkers to Jeremy. 

Mike, if you just want to turn on slow motion for testing purposes, the command you are looking for is:

host_framerate.

I find that setting it to 0.002 gets me a slowmo which I can study animations by, but my understanding is that the appropriate setting varies depending on the computer (so you couldn't use it to make good a bullet-time powerup) 

My bacon is saved, and I get to keep my conkers after all. Thanks Preach. 

Oh sorry, I misunderstood when you mentioned the i7. :)
You can also try host_timescale which is in fitzquake engines only. 0.5 is half speed, 1.0 (or the default 0) is full speed. 

It's staggeringly pretty in slow-mo.

(but it does show nails appearing from the side of the gun and not from the end of the barrel) 

yeah i created host_timescale because host_framerate is sort of confusing to use. 

Put succinctly, my map currently runs awesomely, until I light it. After running light, the monsters start spawning above the ground, getting stuck in the air, and walking through walls.

Any idea how the HELL this is possible? 

... do you have flying shell boxes that attack you with Scrag green fireballs ?
If it is the case, then it is because you loaded a saved file generated from the previous version of your map... I experimented this kind of behavior and it indeed a kind of "surprising" :) 

what? 

.. sorry Von, I've been screwed by the green color of Fern's name. Actually post #12166 was for Fern :P 

I had the same on responding you for jtl.
Someone must have made that teleporter, falling out in small cubes. 

Is it possible to create an entity in Quoth that would sit and quietly emit a rocket/grenade trail? 

Search the teaching old progs dat thread. What you need is to assign a mdl - either the rocket or grenade (or create a new one which is empty but still has the rocket or grenade trail flags on) to an entity.

I think the method is to apply such a model directly to an info_notnull.

The difference between the two trail types is that the rocket has the glow decal. 

One caveat to that: non-moving particle emitting entities do not emit particles. :(

What you could do is make a one vertex model with an emitting flag set, attach that as a model on a func_rotate_train and have it move between two path_rotates 1 unit apart at a very slow speed. 

I know I'm usually the one suggesting hacks, but this case I'd say don't. Firstly because hacks are a problem in mods that might release a new version: either the people making the mod need the testing power of a major studio to catch potential breakages, or you run the risk of your map being broken by a patch. We don't have that kind of testing, so why take the chance?

The second reason you shouldn't use a hack is that there is an entity specifically for this purpose: mapobject_custom
http://www.quaddicted.com/webarchive/kell.quaddicted.com/quoth/quoth_tutorial.html#mapobject_custom
Make a model with your required flags and away you go.

Once you've done that you might find that no trail appears from an object that isn't moving. If so then look at spawning an invisible model with the grenade trail set using the info_rubble
http://www.quaddicted.com/webarchive/kell.quaddicted.com/quoth/quoth_tutorial.html#func_breakable

There is a model called air.mdl in the quoth pak which is intended for this purpose (it's the effect used by the polyp breath attack). 

ta for the info guys :) Will try it when I build up the motivation again :p 

negke mentioned that they have two skins... but I have no idea how to change the skin. I want one to match a blood theme and negke said there was a brownish one, which might work better than the red one. 

i think by just setting 'skin' to '1'. there's no 'official' code to support the skin.

incidentally, fitzquake allows -quoth which can be used in combination with -game, so you could make a mod dir with a new polyp skin and then you would run quake -quoth -game than and the 'than' mod files would override quoth files without interfering with quoth itself. 

Kell made a nice tutorial website you should read. Please have a look here http://www.quaddicted.com/webarchive/kell.quaddicted.com/quoth/quoth_tutorial.html ;)

For Vermis skin answer, please look here: http://www.quaddicted.com/webarchive/kell.quaddicted.com/quoth/quoth_tutorial.html#vermis