Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CS 1.6 Beta build 5961] interpolation of models #405

Open
AndreiRomania opened this issue Feb 19, 2013 · 19 comments
Open

[CS 1.6 Beta build 5961] interpolation of models #405

AndreiRomania opened this issue Feb 19, 2013 · 19 comments

Comments

@AndreiRomania
Copy link

removing ex_interp 0.1 as default and making ex_interp 0.01 default and along with cl_cmdrate 101 and cl_updaterate 101 to match ex_interp 0.01 for corectly placing the HITBOX stickman with the model layout.

http://www.youtube.com/watch?v=r3gvnQ7qenY

http://www.youtube.com/watch?v=3avJ6ylbflU

@ghost ghost self-assigned this Feb 19, 2013
@ghost
Copy link

ghost commented Feb 19, 2013

again whit those 101 myth`s

@konschta
Copy link

There is a discussion about this topic in issue #395 - [HL1/CS] Automatically set ex_interp to the correct value.

@ghost
Copy link

ghost commented Feb 20, 2013

@kirvs I totally agree.
@AndreiRomania 101/101/0.01 are not the best values you can play with. also 101 is totally bullshit

@MaximilianKohler
Copy link

What are the best values than? I think that the point is that the best values should be default and set automatically.

@ghost
Copy link

ghost commented Feb 20, 2013

It really depends on many things but especially on the server load and numbers of players. Also everyone has a different connection/bandwidth to the server and so on.

Those 101 values are myth's, they are capped at 100 by the engine. Also I don't like to play with an ex_interp of 1/cl_updaterate. I'll lag with such an interp. I usually do 2/cl_updaterate or 1/cl_updaterate + 0.01

Finally there are many myth's about netsettings. According to my experience I deal with it at the best with a toggle :)

@MaximilianKohler
Copy link

It was said in another thread that updaterate is capped at 102 and cmdrate isn't capped at all.

@ghost
Copy link

ghost commented Feb 20, 2013

Well I used wrong phrases. I mean higher than 100 is unnecessary and makes no sense actually :) However, the thing is everyone will experience other rates as the best :)

@AndreiRomania
Copy link
Author

Leon291 -> with ex_interp 0.01 cl_cmdrate 101 cl_updaterate 101
My gameplay

http://www.youtube.com/watch?v=NJrgzA7JvEA

@ghost
Copy link

ghost commented Feb 20, 2013

And? What do you want to say with it? Try 100, 100 its the same ;) but as I said its not the point where the cap is. The point is many users can't play with 100, 100 or 101, 101 like you ^^

@Antoweif
Copy link

The correct value for cl_cmdrate is "FPS+5". Also, cl_cmdrate is capped by FPS, but there is an ultimate limit. cl_rate 20000 (which is removed now) and defaulted at 20000. Somewhere above 160 updates and you'll need more allowed bandwidth. Again, it's capped at 20000 (cl_rate) internally.
Just set cl_cmdrate 1000 and let the engine do the talking, unless you have limited bandwidth, which would be an incredible feat considering how old this game is.

@leon291, more than 100 updates makes perfect sense if you want to boost your client on servers that allow it. Check out #350 ;)

@ghost
Copy link

ghost commented Feb 20, 2013

@Antoweif cl_rate was replaced with rate command. And it's set to 30000 by default, and limited to 100 000

@Antoweif
Copy link

@Maxkorz No, cl_rate determined upload rate in CS1.6. rate controlled download.
Why was rate limit increased to 100000 anyway? The game doesn't need more than 20000, because cl_updaterate is limited to 102. I don't get the logic.

@ghost
Copy link

ghost commented Feb 20, 2013

@Antoweif where did you get that? http://steamcommunity.com/games/70/announcements/detail/1028214575930748973
Removed cl_rate command, "rate" is the appropriate command to use
I think they were the same commands

@Antoweif
Copy link

I have tested it. I know why everyone says what you say, but I have tested it. I wanted to use cl_cmdbackup 105, but was unable to, because of a rate limit. I figured out it was cl_rate's fault.

@ghost
Copy link

ghost commented Feb 20, 2013

@Antoweif ValveSoftware/steam-for-linux#1623 (comment)
And why would you set cl_cmdbackup to 105? As far as I know, it determines the amount of information that helps to recovery sent packets on poor connection

@AndreiRomania
Copy link
Author

Stay on topic pls this is about the ex_interp witch should be 0.01

@ghost
Copy link

ghost commented Feb 20, 2013

ex_interp is part of the net settings as long as the other values 👅

fps + 5 o.O ???

There are too many myths :D How about to lock it on your fps? 1 frame, 1 package send/received

@ghost
Copy link

ghost commented Feb 20, 2013

I think cl_cmdrate = fps_max + 5 is a real deal. Check this:
http://s020.radikal.ru/i709/1302/9c/8cfdd4a34f26.bmp
http://s019.radikal.ru/i619/1302/54/eee270a8828a.bmp
http://s001.radikal.ru/i195/1302/fc/218fd42323ff.bmp
http://s019.radikal.ru/i619/1302/91/87b30f4d8ce3.bmp
cmdrate 105 with 100 fps makes the connection very stable (you can see two float lines)

@Antoweif
Copy link

@Maxkorz, haha I used cmdbackup because I really thought it would help me perform better in my younger days!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants