hitch warning: frame time of 278 milliseconds
hitch warning: frame time of 152 milliseconds
hitch warning: frame time of 260 milliseconds
hitch warning: frame time of 298 milliseconds
hitch warning: frame time of 150 milliseconds
hitch warning: frame time of 248 milliseconds
hitch warning: frame time of 242 milliseconds
hitch warning: frame time of 232 milliseconds
---- killed ----
hitch warning: frame time of 281 milliseconds
hitch warning: frame time of 241 milliseconds
esx_ambulancejob: — is reviving a player!
hitch warning: frame time of 256 milliseconds
hitch warning: frame time of 242 milliseconds
Sending heartbeat to live-internal.fivem.net:30110
[SAVED] ----
hitch warning: frame time of 314 milliseconds
hitch warning: frame time of 426 milliseconds
hitch warning: frame time of 185 milliseconds
hitch warning: frame time of 365 milliseconds
hitch warning: frame time of 611 milliseconds
hitch warning: frame time of 506 milliseconds
hitch warning: frame time of 179 milliseconds
hitch warning: frame time of 292 milliseconds
Bullshit, if that’s what zap-hosting is telling people, then they should consider scratching behind their heads.
Even small hitches warnings indicate that a server runs slower than it should, around ~200ms hitches indicates that the server is running 4 times as slow as a normal tick. Saying “hey it’s fine, ignore it” makes no sense in this case.
Consider disabling a couple of resources and see if the issue pesists. My bets are at a slow query somewhere, a synchronous query that is.
Maybe they [zap] are talking about the warnings on initial server launch. If the warnings show up only once when the server is booted and all resources are being started, then that’s acceptable. Depending on the amount of resources, you’re likely to have resource warnings (no matter the server specs) on initial server boot.
If the warnings happen constantly even way after the server was started, then that is an issue and most likely caused by a/some poorly coded resource(s).
but since im pushing a 500-600 hitch warning since it was bullshit. can you help me too? Because server side, I have noticed no issues. If anyone knows any ways to trouble shoot it let me know. Thanks
I get that, but with that hitch warning. I had no issues. If you guys figure out a better way to check it out let me know. Thanks will be following this topic.
Version mismatch, you are currently not using the newest stable version of essen
tialmode. Please update
Loaded MySqlConnector, Version=0.26.0.0, Culture=neutral, PublicKeyToken=null in
to ScriptDomain_1386755828
hitch warning: frame time of 767 milliseconds
Loaded System.Threading.Tasks.Extensions, Version=4.1.1.0, Culture=neutral, Publ
icKeyToken=cc7b13ffcd2ddd51 into ScriptDomain_1386755828
Loaded System.Buffers, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ff
cd2ddd51 into ScriptDomain_1386755828
Current MelloTrainer Version: 0.5.5
Latest MelloTrainer Version: 0.5.5
MelloTrainer is up to date!
MELLOTRAINER: mtsaves folder found!
hitch warning: frame time of 1634 milliseconds
Sending heartbeat to live-internal.fivem.net:30110
Sending heartbeat to live-internal.fivem.net:30110
Sending heartbeat to live-internal.fivem.net:30110
[SAVED] All players
Sending heartbeat to live-internal.fivem.net:30110
I removed some scripts but how can I reduce it more?
If you had read above, hitch warnings are fine if they only happen on first server boot. And as long as they’re only a reasonable amount of ms. If you have 30000ms hich warnings, then you definitely have something broken on your server.
will be following this topic.
