Separate names with a comma.
Discussion in 'Counter-Strike Source Chat' started by Nomy, Apr 21, 2013.
Forget about capping or vsync. That processor will give you 40 to 60 fps anyway.
I play it all on low
Also: ragdolls disabled and no phys_props
Yeah, here are my settings:
(cuz I'm also an Intel HD 3000 user)
well then turn them up till you get a good balance then...
That's pretty impressive that you're pulling that kind of frame rate even if you are on an empty bhop map.
EDIT** I'm not even trolling ICI
Wow, thats an amazing FPS for a HD3000 :\ Wish mine could compete
Added more info on sm_netstats command usage on first post. I hope its understandable... if not, please feel free to ask.
I have a nice tip for you. Just disable vsync to avoid getting detected by server. Use fps_max 60 on regular servers instead because it gives the same effect you get with vsync.
You can cap your fps with fps_max 60 on 66 tick servers like pub, jb, gungame etc.. When you try to join bhop server with fps_max 60, it will just kick you reminding you that your value is below the minimum 120.
I don't think anyone can help you further so I hope this really helps.
Much easier t understand now, that helped me a lot understanding what you meant, thanks for the useful information Nomy. Will keep an eye out
So if i connect with less than 120 it will kick me? Cause that is what i need to remember it :>
Yes. You can try it. We have a script running on server that check fps_max value on clients connecting. It will only issue kick.
Not sure if I missed it but how can you get css to show the showkeys? What is the command in console?
keycheck to check key strokes for the person you are specing.
keycheckme to try on yourself (great for learning).
Added to first post, thanks
yay -.- what is choke? anyway I can improve this stuff?
Check your rates.
Maybe its your internet. or bad PC? That choke is very high, you are sux atm because of it... If your choke is fixed your bullet reg will be a lot better.
I have a bad graphics card and its a laptop which overheats a lot. :/
I think that's the cause. Get a desktop
I don't think there is a fix for this. Btw you can check your choke with net_graph 3.