I tried "ent_nextlight" but if I use it, then view entity misses static lightning... I used it right after changing entities "blue" with "hit.blue" I got from downwards trace.

Yes, hinge stops turning in ROLL and PAN as well, they both stop about 179 degrees. BTW, I've noticed when setting hinge angle with "vector(0,0,0)" first one is ROLL, second TILT and last one is PAN... Shouldn't PAN be first one?


Edit: BTW, I don't know if it already in you to-do list but, I wanted to request built-in debugger for PhysX collusion hulls.

I could provide demo level with all different hinge angles if this could help.

PAN is always the first element in an angle vector, not the last. Look in the manual for "Euler angle". But there is no function to set a hinge angle. Maybe you're confusing this with the hinge axis?

No, I guess I'm not confusing this with hinge axis:
pXent_setangvelocity ( entity, VECTOR* speed );
When I use first vector (which should be PAN) entity changes it's ROLL parameter, but if I use last one, then entity changes it's PAN.


And, any ideas about combining dynamic lights from "ent_nextlight" and static ones from trace? Just poke me in a right direction.

An axis is a direction in space where the object rotates about. An angle however gives the orientation of an object relative to the coordinate axes. Both are different and must not be confused. The engine uses the ANGLE struct for angles and the VECTOR struct for an axis, as you see in pXent_setangvelocity. Hope this helps.

There is no function that finds both static and dynamic lights, but you can use c_scan to find the nearest static lights, and combine this with ent_nextlight to find both sorts of lights.

OK, so what about HINGE, why does it stop?

That I don't know. Hinges don't stop here.

But you can upload your project if you want, or send it to Support, and they'll look into it.

OK, that what I'll do.