Fix: g_forceClientUpdateRate causes hitches

[Wookiee-]

Razor and I have been testing the current build of ja++ and it seems the mod is causing cpu hitches causing problem of the thirdperson camera going out of whack for a 1 second.

[Wookiee-]

Found the problem I think it maybe openjk with Net_Sleep etc JACoders/OpenJK@7b1256b. I could be wrong but just throwing out idea's.

Seems more of an issue with camera angles.

[ensiform]

That's not likely to be reverted even if it has a cause to this at all.

[Wookiee-]

Ok, I found an old openjkded.x86_64 and still doing the same issue so Net_Sleep is ruled out.

[Wookiee-]

I think I have found the problem g_forceClientUpdateRate 250 - Force a client update if a movement command is not received within x milliseconds.

I have set it to 0 and it seems to have solved the issue, though I maybe wrong.

[ensiform]

Shouldn't be causing a hitch. Are you getting a hitch on the server or client. This ensures you don't cheat through triggers etc with low snaps and other lag related problems or cheat lag.

[Wookiee-]

This is serverside after showing Razor on my aussie ja++ server, I will let razor comment on this.

[ensiform]

If that's the case though it (potentially) affects OJK's server mod code too.

[Razish]

The issue is definitely server-side hitches.
g_forceClientUpdateRate does have a noticeable effect, but I'm not entirely sure if that's the root cause or just exposing the real issue more frequently (i.e. a hitch in Clientthink_real)