What are the best ones? :<

I remember changing something a long times ago when playing in an American tournament that required me to change something just to get on the server (I can't remember what), and I've also upped my fps to 111. Does anyone know what the optimal commands are for ensl/euro servers are?

I'm sure this has been asked before but for some reason I can't find the second page of topics for any of the sub forums. All I can view is the front page, none of the topics contained in which mention rates. Thanks for any help.

This ? http://www.ensl.org/articles/423

Shit, forgot about the article section there.

Ok does anyone know what the actual commands are to change these rates? For instance, when I try putting in "updaterate 111", it just says unknown command :<

cl_updaterate
cl_cmdrate
rate

dont listen to those articles. they are all lies.


i use:

cl_cmdrate 100
cl_updaterate 102

most ppl put cmdrate on 116 (due to the "fps+5" principle) but HL engine cant send more then 100 packets anyway so 100 is the actual max (and i think best)

updaterate is capped at 102 and thats my choice. faster updating skulks = less warpy aliens


for reg: ex_interp 0 really helps reg, but its harder to aim cuz everything is a little warpy. id suggest using 0.08 for marines and 0 for aliens, works for me

x0x0x0! "best" rates are unique for everyone. =)
You can use defaults one(follow the guide in the article).

Necros

dont listen to those articles. they are all lies.

There's no false information as far as I know.

Necros

most ppl put cmdrate on 116 (due to the "fps+5" principle) but HL engine cant send more then 100 packets anyway so 100 is the actual max (and i think best)

If your cl_cmdrate is above 100 then the engine will set it 100 and it does not matter if it was 100 or 150 or begin with. I base this on the code Multi pasted.

But I agree with you on ex_interp and I've said it in the article too. I use personally 0.05, this is something you have to test out manually.

ex_interp 0 forces your interp to be 1/updaterate.

tbh ex_interp 0.01 is best, however not with the servers we have got =)

Some ppl use ex_interp 0.05 because of "bad" servers. Half of max. possible, and that's basicly end of explanation for this variable...

Also you can try this:
10 ping and below = 0.01
20-29 = 0.02
30-39 = 0.03
you get the idea...

Jerky's article is probably the single place on the internet you will find that information.

Regardless, rates make very little difference unless you're a German so that you're privy to whatever black magic Nazi ubersoldat program they're running over there...

If you have german citizenship, you get tanking skills from your ISP, for free, so, rates are just useless.

Okay, I did some testing and I think Multi and Necros are wrong about cmdrate cap. I think its somewhere between 125 and 200.

net_graph, FPS=120, cmdrate=100

We're getting red dots on bottom which means commands are cumulated for deferred sending. Cmdrate is 100 and out is 3.3kB/s

net_graph, FPS=120, cmdrate=125

We're not getting red dots, which means we're sending updates (or commands) every frame, which is a good thing. Cmdrate is shown 125 and out is higher, around 6.5kB/s.

So in other words, there's no cap @ 100.

bHack, now with 1000FPS ENSL #2, the delay caused by server is 1ms, while the connection delay is 20ms-70ms depending on where you live. When server can send updates maximum at 102 per second (Half-Life limitation), you cannot go below ex_interp 10ms (ex_interp 0.01). This is an educated guess, but I think eg. ex_interp 0.05 = 50ms causes you to wait 50ms for data before drawing it, making it more smooth. This makes sense since interpolation is about calculating new values from existing data, and you need more existing data to calculate better. So setting ex_interp to 0.05 increases your actual latency with 50ms at the benefit of smoother skulks . If you set it to 0, it will set it to 9msec with updatrate 102, meaning it will wait 9ms before drawing stuff, which is either zero or 1 update (with updatrate 102, you'll receive an update every 9msec). To make it smooth with ex_interp 9ms, NS would have to get more than 0 or 1 update during that 9msec, meaning HL would have to support higher updaterates.

Here's the difference between different ex_interps and server FPS. I think a jittery skulks happen because when it has to interpolate with 1 update, it sometimes arrives faster and sometimes sooner. A much better solution would be if HL would support higher updaterate than 102.

I updated the rate guide, it should be ultimatum to this shit.

And Patrick is right, stop worrying about rates. People put just way too much value on rates.

In first image cmdrate is only 1/2 your fps like 60/61 (if it less then engine adjust it to 1/3 and then 1/4.. So it need to be same as your fps or more also it wont send anymore than your fps or real fps (Try OSD tools like ati tray tool to check your fps, its more than your fps_max..).

HL engine can send more than 100 updates. The cap is locked to cl_rate 10 000 (or 9999) wich cmdrate and cmdbackup use (lower cmdbackup will allow bigger cmdrate).

http://personal.inet.fi/koti/ylemikki/Fps%20influences.png

Can rates be configured in order to help increase registery performance on ENSL server? I did tweak the rates a little to create the best setting for NS but i am just not sucessful with it. I made it pretty disgusting my making everything warpy and a lot of the bullets and bites don't seem to register sometimes. (Yes i did hit the target :p) If there is a suggestion, all is welcome.