New Update

[z3speed4me]

the new update says any1 that got rid of cl_smooth
as in set it to 0 can delete it from their autoexec, .has any1 done this yet???


saur its ur time to chime in now....

[wihadmin]

Server updated!

:thumbsup:

[APOC]

So what part of the gameplay did this one mess up that the next one will have to fix?

APOC

[The_Professor]

saur its ur time to chime in now....

(Clear's throat)

[SoReal]

I was talking to Saur on teamspeak, he said it would be safe to delete his autoexec, as the update apparently fixed some server side settings for optimized hit boxes. (Rendering his autoexec useless, maybe)

[DemonEyes]

So should we erase the autoexec file that mad had us use? Somehow I doubt valve just fixed all the hitbox problems.

[Saur]

Everyone's raving about this being one of Valve's best updates. The fanficial update thread at steam forums is littered with Good Job Valve's and Thank You's. Forums are down for now it seems.

I've been experimenting with the new adjustments and I'm happy to fill you in on some of my findings.

One of the most important ones includes all players regardless of whether or not they tweak their settings. Before, having a cl_cmdrate or cl_updaterate of 30 would only yield half at around 15-17 tick updates. Now, you get the full 30.

This means that people who play with default settings should notice a difference in their performance which probably explains why a lot of folks on the steam forums are happy. The game should feel more fluid coupled with better hit registration. Again, this is because their default rates have figuratively "doubled" from 15~ to 20/30 defaults. However, setting cl_cmdrate and cl_updaterate at 33 will provide the maximum amount of updates WiH's server will send/receive -- so there is a minor benefit with upping your rates a tad, at least for here.

For different servers with higher tickrates, as long as their server boxes can handle it, you can receive/send the exact tick settings as well with properly configured cl_cmdrate and cl_updaterate settings. For instance, I witnessed unparalleled game play on a novelty customs server with a tickrate at 41 -- full 41 tick. Never dropped to 38 or 26 or some other number.

Side notes, overall choke has decreased and loss is almost nonexistant (again, on good servers). Some people have commented on higher FPS too!

As rune said, you can delete the autoexec if you wish and should play fine without it. I did the other night with a default config on wih and still got the usual KDRs.

I'm going to make a post on what you can do if you decide to keep the autoexec.cfg file. These .cfg's were handed out as a temp. fix for those who wanted them. I'll try to keep it short, but at the same time provide a juicy tweak guide so you can make informed adjustments accordingly and decide what to do yourself. Competitive players 'n clanners may want to look for this.

I've been planning it for a week or so now, and I'm thankful I didn't post it prior to this update :P

As for cl_smooth 1, I have noticed a difference between using cl_smoothtime .01, .1, .8, and 2.0 -- but certainly more testing is needed. x.X;

I'm trying to find a correlation between smoothtime and interp

<3 Saur