Avirox's Rotation Tutorial Adapted to NetQuake

[Spike]

-1 and -2 mean 'up' or 'down', don't remember exactly which is which. So those are proper and required values.

worldmodel with angle -92 makes no sense, although its possible it was some hidden flag for some specific mod, but I'm unaware of which it could be.

[mh]

Hmmm; this is where my mapping-fu hits it's limits, but I do believe you're correct there and that these are legal values indeed. Which means that this is a slightly more insidious problem as we have a case of legal values causing trouble.

I wonder if checking for - and clearing - an "angle" (not "angles") of -1 or -2 on map load would be a more robust solution? Probably not. Although these values are explicitly used for nothing else (up to and including map load time) aren't they, so maybe it is safe? Unfortunate that ID chose a field that has two different uses with no clear distinction. Would have been better to create a new _ field and throw it away in the compiler. (Edit - I think that's probably all rubbish as QC uses them, doesn't it?)

Angles set in worldspawn are nothing new by the way, e3m3 has them too.

[Spike]

[mh]

[mh]

[Spike]

[mh]

[metlslime]

[mh]

angles[1] is the only one that needs special handling though; [0] and [2] can keep the rounding.

[ericw]

Was playing with this recently. gb's and baker's test maps are very cool.
I made another little test map that requires no special qc:
http://quaketastic.com/files/misc/bboxangletest.zip

The focus was to look at how engine bbox rotation could break old vanilla quake maps.
There's a drawbridge that's half open (func_train with "angles" "-32 0 0"). In the map/bsp, the bridge lies flat on the floor. Depending on whether then engine does bbox rotation you either clip through the half-open bridge, or walk up the ramp.
In hindsight I think it's basically a safe change (with regard to breaking vanilla content), because I think the bbox -not- rotation when you mess with "angles" could be considered a bug, and I think it's an unlikely kind of bug for mappers/modders to have exploited.


One note: my test map seems to give trouble in RMQe and DirectQ. As soon as you touch the bridge you sink in and get stuck. I know those aren't maintained, but this might be a useful debug test case if you're still using the same collision code in your research engine, mh,

[mh]

[Max_Salivan]