Good news for QuArK/Quoth users ! 

Good luck. I started that once but gave up early because it was so much work. Haven't got the files anymore, sorry. 

I'm playing with the Vermis in a small test map and notice that he doesn't follow me (shooting) once I drop below a certain point: he just keeps firing at where I was. I'm no_clipping around the map just to get an idea of what he does.

Is there a specific number of units involved e.g. x units below his centre of origin?

Also, is the spread of the missiles adjustable as if you are too far away you can just sit there and they always seem to miss. Perhaps it is a case that he only fits a certain kind of environment spacewise? 

Perhaps it is a case that he only fits a certain kind of environment spacewise.

exactly right. he, like all monsters, shoot in a cone around his fov. but unlike other monsters, his vertical size is massive, so you'll notice how he won't be able to shoot you when down around his 'waist'.

and yes, his projectile spread is constant. after a certain range, the spores stop being a threat.

designing an area for the vermis really is a matter of plopping him in first, and building the area around him.

if your map has the vermis exposed all the way down to the bottom of the model, you'll need to keep the player away from it because he won't be able to attack you or grab you. on the other hand, if you keep him at grab height, then you can let him get as close to the vermis as you want. 

necros check your email 

I tried the easy solution by necros, without qc, but could not get anything working. First tried it with a func_train, but without success. Than thought maybe better start simple and tried to built a fixed light and failed again.
Not shure if I set up everything right in quark.
Here is a screen of the setting.
http://www.kram-hochladen.de/files/25853/light-blob_test.jpg
Whats wrong? help 

I once had a complete varation of all the possible moving light types, I'm searching...

please give me a link to the movelight.zip and I'll explain. 

http://www.quaddicted.com/idgames2/planetquake/quakelab/ 

here you go...

http://members.home.nl/gimli/movlight.zip

if you need help, ask me. 

 

I didn't use the altered progs.dat and it still worked.

only effects 1 and 8 were really interesting.
I saw in the readme you can change the muzzle_bright in other options.
Qspecks can tell you which number to use. 

I have a sky emitting light throughout a level, but in one specific area, I'd rather it didn't, anyone know of a trick to achieve this? (And no removing the sky light and using lots of point entities instead is not an option). 

I think it is possible by adding a polygon within the sky brush, at least if the sky brush is thick enough to insert something inside it. I'm not sure but I think it is the way Quake shadow logo is produced in some Quake Level... 

Right, I remembered there was some trick like that, will try it out, thanks! =)

Anyone know any vis that supports dual cpu and dual core machines? 

I already asked aguiRe on that point some months ago.. aguirRe told me the very first vis.exe Id "release" was unix oriented and was supporting dual CPU usage. Unfortunately, he didn't think that any nowadays vis.exe is supporting dual CPU any more.
Maybe it will come back soon, as many brand new PCs have now dual CPU/core, that could support such a feature...
I think aguirRe would have better infos than me on that point ;P 

the quake logo shadow thing only works because the skylight is simulated using a point light entity above the shadow casting brush.

I think Bal is using the light emitting sky texture thing.

Is there a way to fudge a sky texture's name so that it behaves like a sky but the light compiler doesn't register it as one?

Hmm. what if you compiled the level with a dummy texture for your fake sky so that the light compiler didn't treat it as sky, then replaced the dummy texture afterwards in the bsp using TexMex? I have no idea if that would work correctly but it's probably worth a shot. 

Yeah good point, probably wouldn't work with the brush technique... Will try switching the textures after it's lit, thanks for the idea. 

I expect that the texture switch will work with just one problem - the surface won't be marked as CONTENT_SKY. This means that rockets that hit the surface will explode rather than being removed, and other similar effects. I'd imagine that the texture will still render correctly though. You can see the same thing happens in DM3 as it was compiled with an out of date version of the bsp tools. 

I still haven't tried any of this as I'm still at work...
But considering my sky is just pitch black in that area, any trick to simulating a false sky? some pitch black liquid maybe? 

try the dummy light trick with a negative light instead, and darken the regular sky texture for that section of the sky. 

Is it really a problem that the sky isn't truely a skybrush though? All the ID maps have this behaviour and don't seem to suffer for it, so I'd still say use Kinn's suggestion unless it causes a problem. It was just meant to be a quick warning in case it is important. Black water brushes would do a pretty good job of simulating sky if it does matter, the thicker you can make it the more likely it will be that the sound isn't audible. 

only one sky will show 

only one sky will show

My suggestion. I didn't see Preach's answer that fallowed until now. 

Did I need special build-tools to compile a map for nehahra?
At the moment I use txqbsp, rvis and tyrlite for fitzquake compiling
and it worked fine.
But for the neh-engine, Iam not satisfied, because the test-map is to dark and the brush that should be transparent, is not transparent at all.
Did I need other built-tools and other additional command-line settings
for this engine? 

Did I need special build-tools to compile a map for nehahra?
At the moment I use txqbsp, rvis and tyrlite for fitzquake compiling
and it worked fine.
But for the neh-engine, Iam not satisfied, because the test-map is to dark and the brush that should be transparent, is not transparent at all.
Did I need other built-tools and other additional command-line settings
for this engine?