Anyone looked at it or found a fix yet?
I looked at the should freeze object code and it's bool ShouldFreezeObject( IPhysicsObject *pObject ) { return true; }
Return true all the time? Is it supposed to be like this?
Yes. I described the exact behvaior in my previous mail. But basically this function gets called after you hit the limit of collisions per timestep for a particular object. For HL2 once we hit that limit we want to freeze the object (note that this freezes the object only for the remainder of the timestep, not permanently) to avoid using too much CPU for physics.
The hook is there so you can make a different tradeoff in your mod if you'd like. You can always increase the limit by setting it in the performance settings, or you could do other things in the callback (e.g. add a timer for physics and let it do more as long as you haven't exceeded your real-time budget).
Jay
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
-- Knifa SourceForts http://knd.org.uk/sourceforts/
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
