DP_EF_NODEPTHTEST

[mh]

6. The "shouldn't really happen, but does occasionally" stuff - more pointcontents and in cases where it does happen (i.e. the trace leaves you stuck in solid) even more.

pointcontents is another killer by the way. If I modify PF_pointcontents to always return CONTENTS_EMPTY I can get a 4-5 x speedup in some maps.

[Ghost_Fang]

[Spike]

customizeentityforclient is called by the engine just before it sends the data to the client.

if it returns false, then the server will consider the entity(self) to be invisible to the player(other).
the function is generally expected to modify the entity's various fields to be player-specific (note that the changes will not be undone, so changing origin will affect physics later on).
so you can return false to filter the entity, and you can call setorigin inside to ensure that the model moves with whatever rate the server is sending out packets.

[Ghost_Fang]

So i don't have to specify who "other" is? It just automatically assumes all clients? And only the client(s) (other) who return TRUE can see it and/or the changes?

[Spike]

the engine calls it for every single client, even spectators.
self is the entity who's self.customizeentityforclient is set.
other is whatever client the server is currently trying to send a message to.
you don't call it from qc code, you only set the field so the engine knows what to call at the appropriate time.

'other' is each and every client, in turn. the engine will call your function as many times per (network)frame as there are clients that need new messages.

[Ghost_Fang]

Ok i think i understand, but do I gotta set the conditions of it to be viewed my a specific client?
I did something simple like if(self.owner != other)
Or would I put more arguments in there such as if(self.owner == other) self.nodrawtoclient = other;
Man, I apologize, for some reason this one isnt clicking for me :/