Tweaking

3xtr3m3

TD Member
Hey,

I am making this thread to help some of you to tweak their setup to perform better in the game. I will not write it detailed. Google will be your friend if you want to learn more.

1-You need a decent PC to play in good resolution. I am sure most of you have 19" or bigger monitors, +2GB ram, a good video card etc.. If you don't no surprise why you lack.
I have an 24" and play in 1920x1200,

2-Sound system. SOUND is the most important thing in my opinion. You must have headphones (speakers don't work). I have a cheap Sony MDR-XD200 from Shoppers that works just fine but if you have the money go with better brands.

You need a sound card that will give you the 5.1 surround option.

Set your sound card to 5.1 and also set your audio setting is Source to 5.1 and use HEADPHONES.

I can spot someone's exact place when I hear them reloading. How ? I don't hack, i can hear it.

If you just wanna play the game and concentrate on it, mute ppl like 47, miss haze, omissions :)

3- Don't listen to Buckshot jr. Get a good mouse and a mouse pad. My preference Razer Deathadder 3500dpi and a rocketfish pad.

Mouse settings are very critical.

-Install your mouse driver. Razer has an option to adjust vertical speed. Lowering it will help you to aim better for headshots. Setting it to 1000 mhz and 3500 dpi, you have a very accurate piece of shit in your hand :)

-WINDOWS mouse speed setting MUST BE in middle. The one you adjust in control panel in windows. Don't play with that. It has to be adjusted right in the middle. If not your mouse rates and screen resolution rates will mess up.

-MOUSE ACCELERATION MUST BE OFF. There is .reg file for (xp, vista and win7) that you run and it changes the registry and disables the acceleration. Google it and you can find it.

-Open steam - game list - cs:souce (right click) Properties - Set Lauch Options

Put these in your set lauch control option box

-noforcemspd -noforcemparms -noforcemaccel -w 1920 -h 1200 -refresh 60 -nojoy -noipx -nosync

*** -w 1920 -h 1200 -refresh 60 FOR THIS; replace the numbers 1920 , 1200 and 60 according to your resolution and refresh rate. If you don't know than don't put it there :)


4- If you are using a router forwarding ports steam uses can help. You have to go to your router's settings. And forward the ports 27000-27040 UDP/TCP)
Google is your friend for this.

5-Server settings. Some stuff from my autoexec.cfg

rate "25000"
cl_cmdbackup "2"
cl_cmdrate "67"
cl_updaterate "67"
cl_interp "0.02"
cl_interp_ratio "1"
cl_smooth "1"
cl_smoothtime "0.01"
cl_predict "1"

Your connection is also really important. When you are in game, open console and type net_graph 3
You will see some numbers. Your actual ping, lerp, loss, choke

You want your loss and choke to be "0" choke can be tolerated if it goes up to 10-15 sometimes.

With my setting up there you should be getting 20ms lerp. If it is constant white you are good if it is yellow or orange, adjust your lerp till you get white. To do that you have to change the value of cl_interp. Raise it by 0.001, it is set to 0.020. Like 0.021, 0,022, 0,023 etc.. Until you are solid white. It could be at 0.030

You also should watch your FPS, you don't want it go less than 60fps if it does than you need to tweak down some settings in display. You can use -dxlevel 81 for launch control settings to help with that.


6- Some network tweaking might help with lowering your ping.

It works for some ppl and sometimes it does nothing but give it a try.

You will have to make changes in regisrty.

1) Run regedit and find the following location…

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\

Parameters\Interfaces\

2) In interfaces you will see a list of bunch of scrambled numbers and letters, click each one and choose the one that has dhcp values on the right hand side (shows your ip address, subnestmask etc.)

Add a new DWORD (32-bit) named “TcpAckFrequency” and set its value to “1″

Also add another new DWORD (32-bit) named “TCPNoDelay” and set its value to “1″ as well.

3) Next, install MSMQ by going to
control panel
add/remove programs
add/remove windows components
in the list, find "Message Queuing"
if it is selected, you already have it installed.
if not select it and press next
it should install MSMQ

Than go to regedit again and find this location…

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters

4) Add a new DWORD (32-bit) naned “TCPNoDelay” and set its value to “1″.

5) Close regedit, reboot, and you’re done.


These are all it comes to mind for now. I will edit this post if there are more things to add.
 

OG buckshot jr

TD Admin
No worries about the mouse, it's just a preference :D

Quick things I noticed:

- cl_interpolate is not a command in source; they took it away in the move from 1.6->source

- your interp is wrong/off. Darkly is 66-tic, meaning you'll only get 66-tic cmd/updaterate - so your interp must be adjusted accordingly (33ms lerp for 66-tic server is correct, i.e. cl_interp 0.033).

Question: Explain these as best you can?

- cl_predict
- cl_cmdbackup

I've read mixed answers, but I'm curious.. if you can? I'm lost on them since 1.5 lol
 

3xtr3m3

TD Member
Ok, it is your preference than but i suggest you take my advice on it.

I know interpolate is not used anymore. I just copied and pasted. Won;t do anyhthing even if you have it there.

Those numbers will still work for 66 tick. You will basically maxing them. It is better this way because when you join a 100 tick server you don't have to change anything. If you just copy and paste same values it will work just fine, except you may need to adjust cl_interp as i mentioned there.


cl_predict afaik your computer is predicting the next move of the opponent. It is kinda antilag thing. I may be wrong.

cl_cmdbackup is for the packet loss. Leaving at 2 is optimal.
 

3xtr3m3

TD Member
Ohh btw why would you want 33ms lerp when you can have 20ms (white) You are just adding 13 ms ping for nothing.

If you can set it lower you will have more reaction time. If you set it to 0.033 better reg.

I prefer reaction time> reg
 

auron

TD Admin
the cl_predict should default to 1. It's only set to 0 if you want no recoil hacks, which maybe your toggles do.
 

OG buckshot jr

TD Admin
[quote1293747290=3xtr3m3]
Ohh btw why would you want 33ms lerp when you can have 20ms (white) You are just adding 13 ms ping for nothing.

If you can set it lower you will have more reaction time. If you set it to 0.033 better reg.

I prefer reaction time> reg
[/quote1293747290]

Ya, now you're right. Setting interp to half the server tic-rate is to get hitboxes as close to the actual on-screen animation as possible. Settings an interp higher (higher lerp than half server tickrate) will result in the hitbox being "after" the animation; a lower interp (lower lerp than half server tickrate) will result in the hitbox being "before" the animation.

So we're both right - preference. I just prefer to shoot the guy where he stands, not where he was/will be.
 

OG buckshot jr

TD Admin
[quote1293763338=SiR-dreK]
Question:

-refresh 60.

Don't most LCDs support 75hz?
[/quote1293763338]

Depends on the resolution you set Windows/games to play on. On HD resolution (whether it be real HD 16:9 1920x1080, or pc blown-up not-quite HD 16:10 1920x1200) all LCD's (that I've known) run up to 60Hz, however on lower resolutions can support up to 75Hz.
 

3xtr3m3

TD Member
Jr. I think you are right about rates.

It is not a good idea to run cl_cmdrate 100 and cl_updaterate 100 in a 66 tic server.

It results in choke. Because you are trying to send or receive more than the server can handle.

I fixed my first post. So cl_cmdrate is 67 and cl_updaterate 67

Edit: I see that our server forces to set the max rates anyway. Even if you have cl_updaterate 100 in your autoexec, server will change it to default 66
Only thing to watch out for is the cl_interp and cl_interp_ratio
 

3xtr3m3

TD Member
Also added how to add TcpAckFrequency and TcpNoDelay registries.

Might help with lowering your ping a lil.
 

OG buckshot jr

TD Admin
Nooo shit, I've never heard about reg hax that fuck with network latency within your hardware... ill try it this weekend and post some before and after info. Thanks!
 
Top