Hello, My mod has recently started encountering a problem with movetypes. It seems that the movetypes of some entities (so far I have observed it happening to env_beam, trigger_once, trigger_hurt, func_door, and func_door_rotating) are getting forcibly changed to random numbers and triggering a warning and an assert in physics_main_shared.cpp. These seem to occur every server think and really take a toll on the server's performance. One example of what the warning prints is: PhysicsSimulate: trigger_hurt bad movetype 170. I have seen almost any number up to 254 as the movetype, and sometimes I am able to watch the console and see the number change every few thinks, growing until it reaches 254 and then starting over again from 0. The assert seems to only start happening once a player (or possibly other entities, I have not tested) touch the beam/trigger/door. I have tried to debug this problem myself, but I just can't figure out what is changing the movetype. I have put breakpoints in CBaseEntity::SetMoveType, but they never trigger as the movetype on the entity changes and causes the asserts. Any help that anyone can give is appreciated.
Jory - "Hyperjag3" _________________________________________________________________ Visit MSN Holiday Challenge for your chance to win up to $50,000 in Holiday cash from MSN today! http://www.msnholidaychallenge.com/index.aspx?ocid=tagline&locale=en-us _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
