I have successfully got 100 tick working. If anyone wants to see it, they can pm me for the ip.
ODKAZ NA STAHNUTIE
Kód: Vybrat vše
http://didrole.com/tickrate_enabler/Tickrate_Enabler_0.1.rarPlug-in Link: Tickrate Enabler
Simply extract this into your cstrike and your good to go. Requires server restart...
Bhopping, it feels identical to as before.
Registry, it is even better. With 66 tick rates, you feel no difference, but as long as you have your rates set again for 100 tick it feels even better. Read down for info on that...
I need to go into detail about tickrate, as we have those who think tickrate is what they see in net_graph 3.
100 Tick means the server processes 100 ticks a second. This also means that 100 kbs can be uploaded and 100 kbs can be downloaded.
NetGraph - You most likely do not understand it
I am pretty sure you notice when looking at net_graph you see, in 67 kbs and out 67 kbs. Or on my Server 67 is replaced with 100. KBS is kilobytes per second. Not Tickrates per second.
In netgraph, you are seeing the bandwidth of yourself. That value you see is clientside. You see yourself uploading 100 kbs, and downloading 100 kbs. 100 Tick servers have drops in these bandwidth rates, as well as any other server. This is caused by a few reasons.
1. The maps, Dev textured maps and maps with func_doors and moving objects cause this value to go down. From 100 Kbs to 70 Kbs. I ran aim_ag_texture_city 24/7, it is dev textured. When dev textured maps fill with players, the bandwidth rates drop/ I proved to 15 players when switching to de_dust2, still with 15/16 players, that those values would be stable. They were.
2. Smokegrenades and Flashgrenades, the client and server struggle with these, all servers do. Little do people know that these drops in net_graph were always present, even in the old version of css.
3. Your rates are not set. The new update set everyone to download and upload 67 kbs. To fix these, cl_updaterate 67, and cl_cmdrate 67, need to be set to 100 each. Also changing your rate to 30000 can help (rate 30000).
If you have a faster internet connection, you can get the max out of the server by raising your rate even higher (maybe rate 70000.)
The only thing net_graph shows is that the server has 100 tick on, as the upload and download can reach 100 tick. The tick caps the value for bandwidth. 66 tick servers show the bandwidth at 67 kbs at in and out.
Server tick does not drop. It is always consistent. If you try to bhop, or surf, you will notice it feels smoother, aswell as the movements. Registry is also improved as the server is running at more optimized settings.
There is no such thing is 100% registry. Connections (pings,etc.) affect registry too. If I (with 20 ms) shoot a guy with 200 ms ping, and he shoots me at the same time, he dies not me, because I have a faster connection to the server.
Hopefully we have learned something here, and have not made up stuff to pretend we are smart.
100 Tick - "100 tick is worse on orange box", No it isnt...
Hidden Path:
They stated that they took out -tickrate starup command and forced 66 tick to keep the game consistent. 66 tick was chosen as some servers cannot run 100 tick with a high slot count. 66 tick is the ideal tickrate for average servers. 100 tick works well on smaller slot servers that are ran on good hardware, mainly under 20.
For those who have mentioned earlier, that 100 tick is worse for registry, etc. They are wrong.
Well they are right in the sense that they are getting bad registry, but that is because they do not have the proper rates set.
Rates/ Server Settings:
The 100 tick, increases the smoothness of the game, allows bhopping as the server processes faster and it allows has even better registry. To completely optimize yourself for 100 tick servers, two things must happen.
1. The server must have the server-side rates set to allow clients to receive the proper upload and download rates. The server must also allow a higher rate value.
For hosts that are running the 100 tick plugin, you should use the following.
Code:
sv_minrate 30000
sv_maxrate 75000
sv_maxcmdrate 100
sv_maxupdaterate 101
sv_mincmdrate 67
sv_minupdaterate 67
sv_client_max_interp_ratio 2
sv_client_min_interp_ratio 2
note: Again, on the orange box engine, the higher rate is fine. I believe that majority of players have upgraded from dial-up. sv_maxrate 75000, My servers are located with huge amounts of bandwidth so I can use a high value for maxrate, if your server lags, lower this value to 50000.
2. Client-sided settings.
I have not found away to force cl_interp on clients. If clients, want to get the best possible out of a server with 100 tick or 66 tick, they need to lower there cl_interp value from the default. This syncs the client with the server's hitboxes.
To figure out what your cl_interp value should be, you can use this small formula:
cl_interp_ratio/sv_maxupdaterate = cl_interp
(sv_maxupdaterate, because the server forces your updaterate to this..)
In most cases your cl_interp_ratio is 2 by default.
so if you want to be fully optimized for 100 tick, you should take your interp_ratio and divide it by the server's sv_maxupdaterate.
If a server is 100 tick, the owner should realize that the updaterate should be set to 100. So whenever on 100 tick servers use 100 as the updaterate value. And same with 66 tick, the value should be 66
100 tick: 2/100 = 0.02
cl_interp 0.02
66 tick: 2/66 = 0.0303
cl_interp 0.03
If you follow these rules, you can optimize the registry you get in the game as you are syncing yourself with the server's connection.
I hope we have a basic understand now.
*** Suggestion to Hidden Path team, allow servers to control their clients cl_interp value. It is our job as server owners to make sure clients can connect well, allow us to do this.. Also restore tickrate back, as players can decide on their own if they want to play 66 tick 100 tick or 33 tick ***
.
[/url]
(Stejnak se najde někdo kdo to nebude umět