Quote:
Originally Posted by FlaminSarge
Was there a particular reason for DHook + NOP instead of just patching the value inside the CMoveData.m_flMaxSpeed assignment?
e.g. https://github.com/FlaminSarge/tf_maxspeed_patch solely patches the value and I'm unclear on if it does better, worse, or the same for prediction.
Also, have you attempted editing m_flClientMaxSpeed? Does that help with prediction at all? |
No particular reason, but I believe just replacing with NOPs 1 time instead of constantly overriding the value would be better performance wise, but we're talking nanoseconds here
As far as I knew TF2 doesn't even use m_flClientMaxSpeed
__________________