what are your rates?

always wondered what rates peopled used, guess i will go first.

rate 20000
cl_cmdrate 100
cl_updaterate 67
cl_interp 0.015
cl_interp_ratio 1
cl_interpolate 1

$500 a night, but if ur mom is hot, I might give her a discount.

$500 a night, but if ur mom is hot, I might give her a discount.

LMAO, BEST RESPONSE EVER

----

rate "100000"
cl_cmdrate "66"
cl_updaterate "50"
cl_interp_ratio "1"

as suggested by A Seagull http://www.hl2dm-university.com/forum/p ... hilit=rate

Reading back over that maybe I've set my rate a little high, although I rarely get choke or loss and hit reg seems ok. opinions?

My connection is:

rate 50000
cmdrate 67
updaterate 67

hard wired
rate 22000
cl_cmdrate 66
cl_updaterate 66
cl_interp default as i've never changed this
cl_interp_ratio 1
cl_interpolate 1

wireless
rate 15000
cl_cmdrate 33
cl_updaterate 33

67/67/100000
everything else as they should be

rate 50000
cmdrate 67
updaterate 67

67/67/100000
everything else as they should be

protip: rate is capped 30000, anything higher is pretty much useless.

cl_cmdrate 100
cl_updaterate 100
rate 30000
cl_interp_ratio 2

Capped by what? The server config? Not on my pub. Maxrate there is 50000. I have had it up to 100000 in the past and it handled a full 16 slot server with no lag whatsoever. Punk can verify this as he tested it too.

DM is default 30000 because when it came out, servers, PCs and internet were not what they are today. All can now handle 50000 and probably 100000 no problem.

Case in point. Crysis Wars servers are default 50000 and there are a lot of 20 and 24 slot servers for those. Crysis Wars is a very demanding game serverwise, much more than DM, particularly in graphics alone.

Try DM at 50000 on a server that allows it and you'll find a much smoother game.

In fact we were trying to convince Fearsome to change the CAL cfgs a while back. He said he had to look into/test it and it never got any further.......

Yea in Europe we cap it at 100000 we don't follow the same server configs like cal.

All my stuff
http://files.resistance-tester.com/game ... toexec.cfg
http://files.resistance-tester.com/game ... /keefy.cfg

Copied my post from other similar thread.

Default rates are cl_cmdrate 30/ cl_updaterate 20, you should ALWAYS set your updaterate 67% of your cmdrate for the smoothest possible gameplay and hit reg. Since in hl2dm the servers tic rate is always 66, theres no point putting your cmdrate at 100 and updaterate at 67 because then you'll still be getting 67/67 from the server since it's capped at 66 tic anyway. So the best you could use should be cmdrate 66/ updaterate 44, which is what I use. Recently I've found the best mix between smoothness and best hit reg is cmdrate 60/ updaterate 40. I keep my rate at 20000, as setting it higher gives you little to no lag compensation and often the case is with really high rates that people with much lower rates or people that lag kill you a lot more than if you had your rates a bit lower.

cl_updaterate 66
cl_cmdrate 66
rate 66000
cl_interp 0

Well obviously you can't set your rates for shit. Interp 0? That would be fine if you only play in LAN's but don't even think about playing over the internet.

I'm a bit vague on this, so correct me if I'm wrong...

cl_interp doesn't do anything in HL2DM. Unless Valve changed it back, it is calculated as a ratio of interp ratio divided by update rate.

It does work in hl2dm, that would be like saying cmdrate/updaterate doesn't do anything in hl2dm , if you change interp to 0 it completely disables it.

Playing tf2 I came to learn more or less how the interp thing works. I do change it @ tf2, but afaik in hl2dm it would get locked as WT says. You can't just set cl_interp to 0.015 and if you don't like it change it to 0.040 and later 0.030. The game wouldn't let you.
It's been some time since I don't touch anything so I might be wrong....

Setting it to 0 will not make it being to 0 but to the lower value possible.

My internet provider in France is the only one which provides a special settings allowing to less check packets. Consequently I have a ping of 5 when I play on the net whereas 4 years ago in my own LAN with all the meters of cable I had about 15. So yeah I'm close to a LAN behaviour that's why I set interp to 0

in my own LAN with all the meters of cable I had about 15.P

Are you sure you weren't using rope?

if i'm reading this correctly, you can change cl_interp:

"The relation between snapshot rate and view interpolation delay is the following:

cl_interp = 2 / cl_updaterate

For example, if your client receives 66 update per second, you can set cl_interp to 0.03. This way your view interpolation lag is lowered from 100ms to 30ms. Removing the view interpolation lag completely by turning it off (cl_interpolate 0) will not work and cause jittery animations and worse hit detection."

so thats the valve recommended equation. im curious about people using cl_interp .015 (that would be cl_updaterate 130?). if you subscribe to the highest cl_updaterate being 100, you would set your cl_interp to .02 according to that valve formula. does forcing it lower than .02 have benefit? how low can a person go? i've never changed cl_interp, like WT i thought it was "assigned" based upon what you set your cl_updaterate to.

here's the info i used: http://developer.valvesoftware.com/wiki ... Networking

there's a note at the top stating "The Valve Developer Community site has gone through a major upgrade". so maybe this is newish info or clarification on the subject? the stuff i quoted above comes from the bottom of the article. but the whole page is worth reading.

Going from memory:

cl_interpolate= 1/0 turns interpolation on and off.

cl_interp is calculated and cannot be set directly, but it can be set indirectly by changing cl_interp_ratio.

cl_interp_ratio can be set manually and varies from 1 to 2, and can be fractional, eg, 1.1, 1.2, etc.

I have a bunch of different combinations of cl_cmdrate/cl_updaterate/cl_interp_ratio bound to my F1-F10 keys. I leave the rate at 50000, and vary the cmdrate from 30 to 100, with the updaterate a bit lower, and an associated cl_interp_ratio based on a relationship I found somewhere (forget where). When I join a server, I futz around with them until the game feels as smooth as possible, but it really seems to be hit or miss. I'll notch it down if I'm getting choke. But even without choke, some days it feels crisp, but more often there is terrible hit registration, esp with the 357. Sometimes the only thing I can hit people with is the xbow. So, either I have a shitty connection (unlikely since I have Fios) or I don't really know wtf I'm doing with setting these rates (likely) or maybe it's a hardware issue (P4 3.4Ghz). I've basically given up on trying to fix it any further.

in my own LAN with all the meters of cable I had about 15.P

Are you sure you weren't using rope?

Yeah with 2 glasses on each side ;D

Default rates are cl_cmdrate 30/ cl_updaterate 20, you should ALWAYS set your updaterate 67% of your cmdrate for the smoothest possible gameplay and hit reg.

false, their ratio to each other does not matter at all

you cannot manually set your cl_interp afaik, if people could then the optimal rates would be

cl_cmdrate 66
cl_updaterate 66
rate 30000 (or whatever your internet can handle, most pubs run cap 30k)
cl_interp .04
cl_interp_ratio 2

my other rate guide was determined by the fact that interp was bound by interp ratio, this is what I use in TF2 for hitscan and it's fine, the extra interp accounts for the server dropping as low as 50/sec

Default rates are cl_cmdrate 30/ cl_updaterate 20, you should ALWAYS set your updaterate 67% of your cmdrate for the smoothest possible gameplay and hit reg.

false, their ratio to each other does not matter at all

From my testing / other source netcode guides.

in my own LAN with all the meters of cable I had about 15.P

Are you sure you weren't using rope?

Yeah with 2 glasses on each side ;D

Are you sure you weren't using tin cans?