[L4D(2)] Tickrate < 33

[css]

CrimsonGT Wrote:I can change the tickrate on TF2 to 100 (actually to anything, but clients cvar wont go over 100).

(01-20-2010, 11:58 AM)loopyman Wrote:  Just like TF2 is locked at 66 Tick.

I don't know what is true, but I believe loopyman is correct because he had it bolded.

[realchamp]

(01-20-2010, 06:03 PM)css Wrote:  

CrimsonGT Wrote:I can change the tickrate on TF2 to 100 (actually to anything, but clients cvar wont go over 100).

(01-20-2010, 11:58 AM)loopyman Wrote:  Just like TF2 is locked at 66 Tick.

I don't know what is true, but I believe loopyman is correct because he had it bolded.

Hahaha nice

[CrimsonGT]

After I finish my pending jobs this week I will write a version for L4D2 and make a nice little video. My post will be in Italics.

[CrimsonGT]

(01-21-2010, 02:10 AM)CrimsonGT Wrote:  After I finish my pending jobs this week I will write a version for L4D2 and make a nice little video. My post will be in Italics.

I put my jobs on hold because I was curious if it was possible in L4D2. It seems the updaterate cvars are just completely ignored now. They made them locked cvars, but even after changing them they still do nothing now. I was able to change the cmdrate however, but it seemed to cap out around 80.

[egor1908]

Just changing the rates will NOT help, because you wont get over 33 updates per second, the tickrate is limiting that.

Or is there something i am missing?

[CrimsonGT]

I changed the tickrate to 100, but it goes hand in hand with the users rates.

(No I didnt just put it in command line, I am running custom code to modify it)

[egor1908]

Wow that sounds nice.

[CrimsonGT]

(01-21-2010, 07:53 AM)egor1908 Wrote:  Wow that sounds nice.

Yeah, it works great for TF2 but with L4D2 since the updaterate cvar is locked, it isn't 100% on the client.

[egor1908]

And the lock can't be removed?

[realchamp]

(01-21-2010, 08:25 PM)egor1908 Wrote:  And the lock can't be removed?

No it's appartently a lock

[egor1908]

(01-21-2010, 10:58 PM)realchamp Wrote:  No it's appartently a lock

Look, you can modify locked/hidden cvars using sm_cvar, right? So what's the difference here?

Using a custom code to modify things is possible.

CrimsonGT just proved it for you.

Quote:L4D and L4D2 are LOCKED at 33 Tick. There is no way to change this.

As you say -_-

[Terrorkarotte]

(01-21-2010, 04:46 AM)CrimsonGT Wrote:  I was able to change the cmdrate however, but it seemed to cap out around 80.

As the updaterate is capped by the tickrate the cmdrate is capped by the clients fps.

[CrimsonGT]

Quote:Look, you can modify locked/hidden cvars using sm_cvar, right? So what's the difference here?

Yeah thats what I meant by it was locked, it required sm_cvar to change sv_maxupdaterate (wasn't visible/changeable without it). But even when changing it with sm_cvar it did not actually change it. Whereas in TF2, I can do the exact same thing with the tickrate, and get 100 cmdrate and updaterate running. So they did something a bit differently in L4D2.

[egor1908]

Okay. I will now be patient and wait till you get this done

[CrimsonGT]

lol I dont have any more free time to spend on it, I just tried my normal method which didn't work 100%.