It's rather late in the night and my mind doesn't work right so I can't think of the word I mean... it's a thingie on medieval castles, it's a gate and if you open it it lowers and it's a bridge over the moat. Anyway, I guess it'd need the ability to move and/or rotate 3D floors, is it in the realm of possible features or should I forget about it at all and use MD2 models for this purpose?

OK it's morning again and thus I know the word again, it's drawbridge. <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) --><br><br>Anyway, the idea behind using sectors is that I could have any length/width/height and any textures for a drawbridge, independent of other drawbridges. Also, I don't think Vavoom yet supports rotating of 3D models, right?

Well, since Vavoom is a very different engine to the original doom, it may be possible, but most likely you will have to use an md2 and some scripts to do that effect...

Technically Vavoom represents floor/ceiling slope with normal vectors, and when level is loaded normals are calculated (world.c, MakeFloorSlope() and MakeCeilingSlope()), and passed to the engine using SendFloorSlope()/SendCeilingSlope(). I wonder what happens if I call these functions while level is running?

Well, this can be done with md2 models. The md2 models can be rotated in any way you like.<br><br>SendFloorSlope()/SendCeilingSlope() writes into sv_signon message and must be performed only while loading level. Writing later will have no effect for current clients and in worst case can cause sv_signon to overflow.

Okay, so it was a bad idea =)