Talk:Point angularvelocitysensor

The AngularVelocity output of the point_angularvelocitysensor is fired like ten times per millisecond when the angular velocity changes. Does someone has an idea on how to prevent it from flooding the engine ? --NykO18 16:21, 7 Jun 2007 (PDT)

maybe you could include a logic_timer thats your sampling frequency and just disable the target entity cause it looks like this doesn't have an enable/disable to target it directly... I'd code you a fix but that may not work depending on what your doing. --Angry Beaver 16:28, 7 Jun 2007 (PDT)

Hmm, I'm trying to increase/reduce the pitch of a sound depending on the angular speed of a given func_physbox constrained to a phys_hinge. You could possibly code something yes, but I believe it wouldn't be useful for a standard HL2 map.. and I don't want to make a mod, this is just a map. The thing is that it works somewhat great, but due to the overwhelming amount of outputs sent by the point_angularvelocitysensor, the ambient_generic doesn't know how to deal with it and the inputs are treated in a chaotic order. I tried to use several point_angularvelocitysensor with the OnGreaterThan and OnLesserThan outputs, but it doesn't work because : when the physbox is turning at a speed of 150 degrees per second, it triggers the angularvelocitysensor for the "10 degree step", the "20 degree step", the "30 degree step", and so on..