Fnatic FragOut League Season 2
HLTV Ip's
-
(99)
(33)
(11)
(25)
(3)
(87)
(112)
(0)
(7)
(322)
(2)
(7)
(12)
(1)
(7)
(79)
(153)
(14)
(16)
(78)
(5)
(1)
(98)
(7)
(71)
-
-
-
pRopaaNS
FACEIT
moxierawr
Umeroff
-
-
(72)
-
myDGB.net2
LDLC.com1
CPH Wolves15
n!faculty15
k1ck16
ENTiTY11 n!faculty16
Wizards12
BX316 Kraftlaget12 Western Wolves16 plan-B7
ESC Gaming14 TCM-Gaming16
Virtus.pro16 LDLC.com8
/10/16 n!faculty11 ESC Gaming16 ELTZ9 -
-
-
CS:GO New player tips
2012-08-15 15:16
After reading same questions over and over I decided to put together few tips for new players in Counter-Strike: Global Offensive Beta
Rates
rate 35000
cl_cmdrate 200 // this will be autoreplaced with current max (128)
cl_updaterate 200 // this will be autoreplaced with current max (64)
cl_interp 0 // this will be autoreplaced with current min (1/64)
Binds
bind KEY "buy XXX"
KEYS ... same as in CS 1.6 (examples: KP_PLUS, KP_5)
XXX ... again same in CS 1.6 (examples: vest, weapon_hegrenade, weapon_smokegreande, weapon_flashbang, ak47, m4a1, awp, usp)
Crosshair
Experiment with numbers, these are what I currently use:
cl_crosshairthickness 1.2
cl_crosshairsize 5
And of course dont forget to switch to Classic cross in Game settings.
Console
Yes. I mean, yes, there is console in CS:GO, it's last option in Game settings, something like Enable in-game Console.
Video settings
I recommend just maxing everything to the point you are above 100 FPS, there is no advantage of small resolutions like in 1.6, so I just use all max and native resolution 1680x1050.
Size of text/HUD
hud_scaling 1
That is to the settings, now I'd like to talk a little about in game stuff.
Recoil
Don't start to panic when you can't hit shit, it's because you've played 1.6 for too long :) It takes some time to get used to new recoil and tapping. My tip is to move your mouse AGRESSIVELY, that is if you shoot you need to move your mouse a lot down and sometimes to sides, depending on weapon and your movement speed. You can kill people with sprays or tapping, but it's gonna feel impossible for some time.
Audio
Audio is a little bit fucked in the game, but it's not that bad. You can still hear direction of the sound, just the distance is fucked right now imo. I mean it sounds like a guy is 10 miles away, so you look and he's behind corner, I think this is gonna be fixed soon.
Walling
Do not wall on purpose. And I mean it, most of the time it won't work, but... if you shoot at enemy and he hides behind corner, keep shooting trough corner, since it's gonna work, trough middle of the wall it doesnt work, but corners do.
Movement
Movement in CS:GO is more free, dont want to compare it to anything, but you should move much more in CS:GO than in 1.6. You can try doing O or 8 before you attack the enemy around the corner, the toon will respond more to your keys than in 1.6
And I think that's all I wanted to share with ya guys, hope it be helpful.
Rates
rate 35000
cl_cmdrate 200 // this will be autoreplaced with current max (128)
cl_updaterate 200 // this will be autoreplaced with current max (64)
cl_interp 0 // this will be autoreplaced with current min (1/64)
Binds
bind KEY "buy XXX"
KEYS ... same as in CS 1.6 (examples: KP_PLUS, KP_5)
XXX ... again same in CS 1.6 (examples: vest, weapon_hegrenade, weapon_smokegreande, weapon_flashbang, ak47, m4a1, awp, usp)
Crosshair
Experiment with numbers, these are what I currently use:
cl_crosshairthickness 1.2
cl_crosshairsize 5
And of course dont forget to switch to Classic cross in Game settings.
Console
Yes. I mean, yes, there is console in CS:GO, it's last option in Game settings, something like Enable in-game Console.
Video settings
I recommend just maxing everything to the point you are above 100 FPS, there is no advantage of small resolutions like in 1.6, so I just use all max and native resolution 1680x1050.
Size of text/HUD
hud_scaling 1
That is to the settings, now I'd like to talk a little about in game stuff.
Recoil
Don't start to panic when you can't hit shit, it's because you've played 1.6 for too long :) It takes some time to get used to new recoil and tapping. My tip is to move your mouse AGRESSIVELY, that is if you shoot you need to move your mouse a lot down and sometimes to sides, depending on weapon and your movement speed. You can kill people with sprays or tapping, but it's gonna feel impossible for some time.
Audio
Audio is a little bit fucked in the game, but it's not that bad. You can still hear direction of the sound, just the distance is fucked right now imo. I mean it sounds like a guy is 10 miles away, so you look and he's behind corner, I think this is gonna be fixed soon.
Walling
Do not wall on purpose. And I mean it, most of the time it won't work, but... if you shoot at enemy and he hides behind corner, keep shooting trough corner, since it's gonna work, trough middle of the wall it doesnt work, but corners do.
Movement
Movement in CS:GO is more free, dont want to compare it to anything, but you should move much more in CS:GO than in 1.6. You can try doing O or 8 before you attack the enemy around the corner, the toon will respond more to your keys than in 1.6
And I think that's all I wanted to share with ya guys, hope it be helpful.
Good blog, keep up the good advice, will be much to learn for everyone in CS:GO.. :)
Movement
Movement in CS:GO is more free
Are you serious? xD
Movement in CS:GO is more free
Are you serious? xD
It's hard to explain, just try to move in one place left and right, you will see you can change direction as many times you want, unlike in 1.6, where you just move right and it takes time to move left again.
Don't take me wrong, I'm not saying it's good or anything.
Don't take me wrong, I'm not saying it's good or anything.
just call it quake3 movement :)
Movements harder because you actually have to strafe with the shot now.
useful!!! thx a lot!!
glad to hear ;)
Post edited 2012-08-15 16:19:28
Post edited 2012-08-15 16:19:28
to fix the mouse feeling:
m_customaccel "0"
m_customaccel_exponent "1.05"
m_customaccel_max "0"
m_customaccel_scale "0.04"
m_forward "1"
m_mouseaccel1 "0"
m_mouseaccel2 "0"
m_mousespeed "1"
m_pitch "0.022"
m_rawinput "0"
m_side "0.8"
m_yaw "0.022"
set the weapon model like in 1.6:
viewmodel_fov 65
Viewmodel_offset_ x 2
viewmodel_offset_y 2
viewmodel_offset_z -2
cl_bobcycle "2"
cl_bob_lower_amt "0"
cl_bobamt_lat "0"
cl_bobamt_vert "0"
cl_viewmodel_shift_left_amt "0"
cl_viewmodel_shift_right_amt "0"
myHYPER.de has some interesting articles about that!
m_customaccel "0"
m_customaccel_exponent "1.05"
m_customaccel_max "0"
m_customaccel_scale "0.04"
m_forward "1"
m_mouseaccel1 "0"
m_mouseaccel2 "0"
m_mousespeed "1"
m_pitch "0.022"
m_rawinput "0"
m_side "0.8"
m_yaw "0.022"
set the weapon model like in 1.6:
viewmodel_fov 65
Viewmodel_offset_ x 2
viewmodel_offset_y 2
viewmodel_offset_z -2
cl_bobcycle "2"
cl_bob_lower_amt "0"
cl_bobamt_lat "0"
cl_bobamt_vert "0"
cl_viewmodel_shift_left_amt "0"
cl_viewmodel_shift_right_amt "0"
myHYPER.de has some interesting articles about that!
I'd not recommend turning RAW input off, unless it's broken. It's actually the best thing you can use, in 1.6 we had to use RInput and RAW settings should be exactly the same, it is basically bypassing Windows registry and take instructions directly from mouse.
i set it on off because the sensivity is way too fast for mee!
Post edited 2012-08-15 16:30:58
Post edited 2012-08-15 16:30:58
nice bro
nice tips man, but i won't agree with resoulution thing, i've tried all resolutions and fount (again) that 640X480 is best for me.Updaterate and cmdrate , depends on server configuration, most servers use 64 64, but servers with tickrate 128 will take 128 update adn cmdrate for best connection, rate should be 30000 or 35000.
.More info, tips and tricks can be found here http://www.netcodeilluminati.com/forums/counter-st..
I also found this tips very helpfull http://www.youtube.com/watch?v=eaYOblCYMS4&fea..
Post edited 2012-08-15 16:46:05
.More info, tips and tricks can be found here http://www.netcodeilluminati.com/forums/counter-st..
I also found this tips very helpfull http://www.youtube.com/watch?v=eaYOblCYMS4&fea..
Post edited 2012-08-15 16:46:05
nice blog bro it helped me a lot.
btw to all those that have fps issues you guys should download game booster.i had 30~50 fps and now i have 100~
btw to all those that have fps issues you guys should download game booster.i had 30~50 fps and now i have 100~
Gamebooster just turns off all the crap you don't need, you can do that yourself in taskmanager.
i know but its much more easier let gamebooster do it
nice blog.
btw, you say that there is no more advantage playing with low resolution, but there is any *disadvantage playing with low resolution?
btw, you say that there is no more advantage playing with low resolution, but there is any *disadvantage playing with low resolution?
No.
Very useful! :). Maybe I can add you on Steam so that we can play some GO mixes?
I live in CZE too :D
Post edited 2012-08-15 17:06:58
I live in CZE too :D
Post edited 2012-08-15 17:06:58
by Walling, do you mean Wallbang or the cheat?
I agree with you about the sounds, hope they'll fix it, can't know approximately the distance with the enemy.
Good article, very useful.
Good article, very useful.
really nice, thanks mate for the great blog!
helped me a lot :)
helped me a lot :)
Figured I'd sort out the net settings you posted, as they are quite far off from what they should be.
Rates
rate 35000 <- Nope, the minimum rate value you should be playing with is 80000 (which will do fine on 64 tick public servers), if you're playing on a 128 tick server you should put your rate to 128000.
cl_cmdrate 200 // this will be autoreplaced with current max (128)
You'll never be able to use a cmdrate of 200, as it only goes as high as the server tickrate, therefore the maximum will be 128 (which you did point out will be fixed, given that the server has a proper config running)
cl_updaterate 200 // this will be autoreplaced with current max (64)
Nope, the current maximum updaterate is the same as the cmdrate (which is 128), and for the same reasons mentioned above, you won't be able to run it at 200.
Rates
rate 35000 <- Nope, the minimum rate value you should be playing with is 80000 (which will do fine on 64 tick public servers), if you're playing on a 128 tick server you should put your rate to 128000.
cl_cmdrate 200 // this will be autoreplaced with current max (128)
You'll never be able to use a cmdrate of 200, as it only goes as high as the server tickrate, therefore the maximum will be 128 (which you did point out will be fixed, given that the server has a proper config running)
cl_updaterate 200 // this will be autoreplaced with current max (64)
Nope, the current maximum updaterate is the same as the cmdrate (which is 128), and for the same reasons mentioned above, you won't be able to run it at 200.
Sry mate, you got it all wrong, dunnno where you take your informations from, but I'd delete that site.
I don't understand it...
Most of you have high bandwidth connections, but you still set your rate to 30000bytes/second which is for ISDN or DSL Light (384DSL, 768DSL or similar).
Stop using a low rate of 30000 while having cmdrate/updaterate set to 66, 100 or even 128. Your bandwidth of 30000 will most likely exceed, which leads you to having choke.
You're pretty much giving yourself a disadvantage!
VALVE/HPE have seen this problem in CSS and set the standard value for rate in CSGO to 80000 for a reason!
Let's do some quick theory:
The biggest packetsize you can receive in CSGO is set through net_maxroutable which has its standard and maximum value set to 1200.
If you receive 66 packets per second (tickrate of 66), and each one is 1200 byte, your bandwidth maximum of 30000bytes/second will not be enough...
.. and so on and so on..
Most of you have high bandwidth connections, but you still set your rate to 30000bytes/second which is for ISDN or DSL Light (384DSL, 768DSL or similar).
Stop using a low rate of 30000 while having cmdrate/updaterate set to 66, 100 or even 128. Your bandwidth of 30000 will most likely exceed, which leads you to having choke.
You're pretty much giving yourself a disadvantage!
VALVE/HPE have seen this problem in CSS and set the standard value for rate in CSGO to 80000 for a reason!
Let's do some quick theory:
The biggest packetsize you can receive in CSGO is set through net_maxroutable which has its standard and maximum value set to 1200.
If you receive 66 packets per second (tickrate of 66), and each one is 1200 byte, your bandwidth maximum of 30000bytes/second will not be enough...
.. and so on and so on..
actually he's right..
nah, he's not
cl cmdrate and updaterate has numbers 64 and 128 as i described, correct someone without even testing the values is dumb, thats why i didnt even reply to that
and about rate, you can set as much as you want, but ive got 35000 from my experience, ive used high numbers, but the game didnt feel right
and that i set high numbers to be autoreplaced, it replaces it on client, so changing it to maximum value makes no sense
cya
cl cmdrate and updaterate has numbers 64 and 128 as i described, correct someone without even testing the values is dumb, thats why i didnt even reply to that
and about rate, you can set as much as you want, but ive got 35000 from my experience, ive used high numbers, but the game didnt feel right
and that i set high numbers to be autoreplaced, it replaces it on client, so changing it to maximum value makes no sense
cya
rofl so only from "your experience", which most likely is from GoldSrc-engine games, you actually claim that you know better than someone like, for example, J3di who is the main developer of zBlock and who has done research on the source engine since ~6 years ago and who has been in close contact with VALVE in developing CS:GO especially netcode-wise? yes, this seems legit
direct quote of J3di:
"Since competitive matches are likely to be played on a 128 tickrate server, these are the optimal settings:
rate 80000
cl_cmdrate 128
cl_updaterate 128
cl_interp_ratio 1
cl_interp 0
Rate above 60k is likely to be absolutely fine, you'll want to set it accordingly if you have lower bandwidth.
Leave everything else at defaults!"
cya
direct quote of J3di:
"Since competitive matches are likely to be played on a 128 tickrate server, these are the optimal settings:
rate 80000
cl_cmdrate 128
cl_updaterate 128
cl_interp_ratio 1
cl_interp 0
Rate above 60k is likely to be absolutely fine, you'll want to set it accordingly if you have lower bandwidth.
Leave everything else at defaults!"
cya
just fucking type cl_updaterate in console after your 128 and stop being such a dick
how am I a dick now? vendetta only corrected your netcode settings and you claim he's wrong (which he clearly isn't), and when I back him up I'm a dick?
yes, that's how the ego works :) when a self-proclaimed expert gets corrected, he's bound to start calling you names :)
self-proclaimed expert, made me smile, i just give tips here to fix basic issues most people have with the game and if obvious idiots keep telling total bullshit again and again, i might call them what they deserve
ill say it one last time:
IF YOU WANT TO CORRECT SOMEONE, AT LEAST SPEND 5 SECONDS AND PUT THAT FCKIN COMMAND IN CONSOLE
ill say it one last time:
IF YOU WANT TO CORRECT SOMEONE, AT LEAST SPEND 5 SECONDS AND PUT THAT FCKIN COMMAND IN CONSOLE
THanks nice stuff :)
how can u save commands? I mean, I have to set viewmodel settins everytime I join the game, it's annoying
I use my userconfig.cfg that I created, then in the game I bind:
bind "F4" "exec userconfig.cfg"
put that file next to config.cfg ofc
bind "F4" "exec userconfig.cfg"
put that file next to config.cfg ofc
thank you very much :)
I did the same thing as well. Or you can just write every command in the valve.rc and it works automatically.
kinda weird about that wallbangs coz today i made sick wallbang on aztec, it was 100% wallbang through big wall :/
Post edited 2012-08-17 23:08:19
Post edited 2012-08-17 23:08:19
its not wierd, ive just said it mostly doesnt work
u should check PROJECT_X blogs, he describes wallbang spots map by map, very useful
u should check PROJECT_X blogs, he describes wallbang spots map by map, very useful
"Don't start to panic when you can't hit shit"
this sentence is awesome.
this sentence is awesome.
I have a tip... Stop playing this crap
is not bad, they don't need to change mechanics, only those things that make gameplay too random
bind "F1" "buy flashbang;"
bind "F2" "buy deagle"
bind "F3" "buy hegrenade;"
bind "F4" "buy ak47;buy m4a1;"
bind "F5" "buy awp"
bind "F6" "buy famas;buy galilar;"
bind "F7" "buy vest;buy vesthelm;"
bind "F8" "buy defuser"
bind "F9" "buy p90"
on every public server I played on buytime is like 2-3sec so I would recommend everyone to make binds ;p
bind "F2" "buy deagle"
bind "F3" "buy hegrenade;"
bind "F4" "buy ak47;buy m4a1;"
bind "F5" "buy awp"
bind "F6" "buy famas;buy galilar;"
bind "F7" "buy vest;buy vesthelm;"
bind "F8" "buy defuser"
bind "F9" "buy p90"
on every public server I played on buytime is like 2-3sec so I would recommend everyone to make binds ;p
Video settings
I recommend just maxing everything to the point you are above 100 FPS, there is no advantage of small resolutions like in 1.6, so I just use all max and native resolution 1680x1050.
o.O really? lol bad tip
low everything and put the lowest resolution like 640x480 is the onlyway if u have a crapy/standart pc to run this game with good fps.
I recommend just maxing everything to the point you are above 100 FPS, there is no advantage of small resolutions like in 1.6, so I just use all max and native resolution 1680x1050.
o.O really? lol bad tip
low everything and put the lowest resolution like 640x480 is the onlyway if u have a crapy/standart pc to run this game with good fps.
We also made a CS:GO Guide which also includes our CFG for the game.
http://www.netcodeilluminati.com/csgoguide
http://www.netcodeilluminati.com/csgoguide
Login or register to add your comment to the discussion.
