Doesn't really work in text, does it?*

Anyway, "maths" is what we say in England, "math" is what Americans say. I wonder if they also say "mathematic" instead of "mathematics".


Unless I put it like this "You say tomayto, I say tomarto". Works best in phonetic script, but this doesn't support rich text, and most people don't have the phonetic script fonts installed anyway. 

Mathematics 

Anyway, "maths" is what we say in England, "math" is what Americans say. I wonder if they also say "mathematic" instead of "mathematics".

We say "math" which is short for "mathematics." I can only assume you say "maths" which is short for "mathsematics." 

mathsemantics

lol

*shoots self* 

I'm working on my Quake Travail maps and am using Hipnotic spawn code (func_spawn) to bring in some of my enemies. This is needed to keep bmodel counts down by replacing teleport brushes with direct spawns.

I have a problem in that if I want to spawn a floating scrag, it just drops until it hits the ground. This results in them not being where I want them and if they drop into lava or water, they are effectively invisible.

Is there anything I can do to stop the drop? Any workarounds can't use bmodels otherwise I'd just go back to the old spawning method if I have bmodel counts to spare. 

I've just had a quick look at hip2m1.bsp (Ancient Realms), and the scrags in that particular map are spawned in the traditional manner.

I've had a quick look at the func_spawn code and it's noticable that scrags are not included in the random spawn function. Also, there is a reference to MOVETYPE_NONE; in the section that deals with the non-random code.

I don't know enough about the code to go any further but perhaps the above is a pointer to someone else to help you (if this was of any help anyway?) 

Saddly i have hit the limit yesterday :(
I think the reason is I have too many triggers and func_walls in the level (used some in light supports). I have two questions:

Can I combine func_wals from nearby places in the map into one bigger func_wall?
Do trigger_counter and trigger_relay eat up a precache slot everytime I use them in the level? 

Can I combine func_wals from nearby places in the map into one bigger func_wall?

YES! As long as they aren't too far apart. Sometimes the engine can start to render them badly if the bounding box becomes too big. They might become invisible from certain angles etc. Typically if they are in the same area and not separated by any walls, then you can group them.

Do trigger_counter and trigger_relay eat up a precache slot everytime I use them in the level?

trigger_relay does not use a model precache, since it is just a point entity. However, I think the counter does. All the other solid triggers take up a precache too.

If you don't want a trigger (for example, a trigger_secret) to take up a precache slot, you should set flag 1 (in Worldcraft it's labelled "entity only"). This way, no model is precached and no touch field will be spawned. 

This really helps a lot :)
I didn't know about the "entity only" solution 

you can make the trigger_counters point entities, too. ;) 

I was worried already that I have to cut something out. Yesterday I have panically deleted some triggers to get below the limit :) 

What is going on here?
v = (a.d * (CVector::crossProduct(b.n, c.n))
+b.d * (CVector::crossProduct(c.n, a.n))
+c.d * (CVector::crossProduct(a.n, b.n)))
/ denom;
Are you dividing a vector? How the hell does that even work? Is / denom; the same as * (1 / denom);?
This is why I don't like operator overloading. :( 

I've forgotten completely. I don't even remember what denom was.

Here's the CVector declaration for the / operator.

inline CVector operator / (float s) const { s = 1/s; return CVector(x*s, y*s, z*s); }

So er, yeah, dividing a vector I suppose.

I think I assigned it that operator because some tutorial in a book or on the net had done that, and I really liked operator overloading.

I don't think I ever understood the maths for this part of the compiler, I just accepted it and got on with the other shit :)

Why are you interested in this stuff, btw? Are you making a game of some sort, writing a tool to export from .map to .3ds/whatever or something more sinister involving dancing badgers?

Anyway, like I said before, you can have the source if you like. The game and all the really badly written documentation can be found here: http://than.spawnpoint.org/files/clayer_full.zip (10mb, sorry, it includes the game and some other shit.)

SHIT! I just looked in the zip and found probably the exact file that you need. I looked it up on google just now and found a link for you http://folk.uio.no/stefanha/MAPFiles.pdf 

the google results also included the file linked in a reply to a question I asked on Flipcode, back when it was running. 

Time dulls the mind, again.

Which Quake level had the pharaoh-looking monster that rose out of the ground? 

Do you mean the dudes with the staves in Dissolution of Eternity? 

You got it, thanks. 

those 'dudes with the staves' are bad models with utterly abominable animations. The skins are pretty good, but that doesn't save them. Please don't put them in a map. 

So, are there any good tutorials about this on the net? 

http://zippy
egoboo.sourceforge.net/tutorial_1.htm
http://www.cc.gatech.edu/classes/AY2000/cs4455_spring/planetquake/modediting.html
http://www.xs4all.nl/~renep/qmehelp/tutmyfirstmdl.htm 

Yes, now I have seen it again, I agree that it's not too clever.

I was only thinking about the code for making a monster rise out of the ground. I didn't realise that it was done via animation - I though it would be the opposite of a sinking dead monster. 

So anyway, hub, spokes, rim... 

...axle? 

Jeez, I doubt that I'll manage two wheels! 

even one needs an axle, otherwise you don't have a wheel, you just have a disk.