[Lux]

Originally Posted by MasterMe Giving -tickrate 95 shows ingame 96/s

Stop looking at the users netgraph of incoming snapshots persecond, does not represent the tickrate the server/clients is running, 95 ticks still means a tickrate of 95.

Originally Posted by MasterMe After that I tried 60hz, and this made it work properly. I'd rather run at a higher tickrate if possible, perhaps someone has an idea?

No idea alot of things change at higher tickrate even csgo is not immune from small differences when changing tickrate you can maybe deal with it with the vomit cvars to boost range.

[MasterMe]

Originally Posted by Lux Stop looking at the users netgraph of incoming snapshots persecond, does not represent the tickrate the server/clients is running, 95 ticks still means a tickrate of 95.

It was just an observation I made which I found curious, hence the "interestingly enough". Inbound rate is around 1% higher than tickrate from what I've seen. Though on official servers (I think 30hz) it's slightly below.

Originally Posted by Lux No idea alot of things change at higher tickrate even csgo is not immune from small differences when changing tickrate you can maybe deal with it with the vomit cvars to boost range.

I'll leave it at 60hz for a while, wonder what's going wrong on my setup compared to Spirit_12's, as it works properly over there.

[winged_box]

Not sure where I didn't config properly but I can't seem to get 100 tickrate on my server.

Platform: Windows 10

Setting:
sm_cvar fps_max 0
sm_cvar sv_minrate 100000
sm_cvar sv_maxrate 100000
sm_cvar sv_mincmdrate 100
sm_cvar sv_maxcmdrate 100
sm_cvar sv_minupdaterate 100
sm_cvar sv_maxupdaterate 100
sm_cvar nb_update_frequency 0.033
sm_cvar net_splitpacket_maxrate 50000
sm_cvar sv_client_min_interp_ratio 0
sm_cvar sv_client_max_interp_ratio 2

Plugin loaded:


Result:

[Spirit_12]

Did you add "-tickrate 100" to your server's command line parameter?

[winged_box]

Thanks for pointing that out, didn't know I have to do that.

I just added -tickrate 100 and below is the result.



And I do noticed my ping doesn't spike up very high anymore during horde which really helps a lot.

Any more configuration I should check to make it even better?

[Vinyl]

I found the cvar that fixes the boomer !

z_vomit_velocity - default is 1700, works perfectly after setting it at 3400.0

sm_cvar z_vomit_velocity "3400.0"

[Spirit_12]

Originally Posted by winged_box Thanks for pointing that out, didn't know I have to do that. I just added -tickrate 100 and below is the result. And I do noticed my ping doesn't spike up very high anymore during horde which really helps a lot. Any more configuration I should check to make it even better?

The rest are upto server settings and hardware. You also need to up your client side rates as well, in order to take full advantage of the higher tickrate.

[MasterMe]

Originally Posted by Vinyl I found the cvar that fixes the boomer ! z_vomit_velocity - default is 1700, works perfectly after setting it at 3400.0 sm_cvar z_vomit_velocity "3400.0"

Tried with this tickrate 96hz and seems to work really well, thanks for sharing!

[rtokuda]

Originally Posted by Spirit_12 I know a couple of you have been asking about it, so here it is. Try out these files and let me know, if they work. I've compiled the Tickrate Enabler for both Windows and Linux platforms against the following: Metamod:Source version 1.10.7-dev SourceMod Version: 1.11.0.6625 It ran on my test server. Can some regular windows user confirm that its working? Once I get some feedback I will update the post on main page.

I tested it on windows and managed to release the 100 Tickrate, but when there is a chapter transition in the campaign, it just freezes, I don't know why.

[Spirit_12]

Originally Posted by rtokuda I tested it on windows and managed to release the 100 Tickrate, but when there is a chapter transition in the campaign, it just freezes, I don't know why.

Does it continue after that at all ? I didn't do any testing on windows.