[Important] Proof of the netcode issues.

C

CobaltIsLife

Guest
Im unsure if this has been posted before, i no the problem has but here are 2 short vids that prove beyond doubt the issues of the CS:S netcode:

This is a vid of a guy using commands to show the hitbox wireframe

http://www.roughnex.co.uk/css.rar

The commands are:

sv_cheats 1
sv_showhitboxes 1
thirdperson 1 (not totally nessacary)

OR

r_drawclipbrushes 1

This is a vid of the problem in a real ingame situation

http://nupo.org/source/huh.avi

As you can see this is proof beyond all doubt that there is horrific problems with CS:S which need sorting straight away.

Yes this is the reason most fail to hit moving targets even when it seems aim is perfect. Yes this is why sprayers get lucky with their shots and kill others when they shoot nowhere near them. Yes this is why most professional gamers refuse to play the game

Now for what really scared me:

http://www.teamnoa.net/?q=news&id=561

Yes it seems CS:S will be replacing CS 1.6 at CPL tornaments in this current condition and that worries me intensly.

I know you know about this Valve, what i want to know is what your plans are to fix this and what sort of time are we looking at?

Please, any official word from Valve or a mod would be much appreciated.

http://www.steampowered.com/forums/showthread.php?s=&postid=1814016
 
This was pointed out a few times, back when we beta tested CS:S.
Try a search for hit boxes to see what was said about it by members back then.

I'm sure valve has know about this for a long time, what they plan is unknown to me at this time though.
 
one is to very rightfully ask why CS:S gets so many ping issues as it's exactly the same game as CS 1.6 with.. barrels/cabinets/etc not being really movable ?
i've messed around with every kind of netcode settings (updaterate etc..) and on my 8000/715 connection i can't seem to get lower than 80 for my ping, where i frequently had 30 or lower on 1.6.

come on valve, what happened ? WHAT makes the game lag so much ?
 
odd.. No wonder why that guy would not die when I was playing CS:S last night I was right behinde him and I started shooting I was burst shooting at his head first and no hs then I just held the fire button down hopeing to kill him then the guy turns around and hs me =o whats up with that crap ! "crosshair was dead on his head too" Also remeber seeing a video and a guy had a auto shotgun and he was right in front of the guy and not one bullet hit him ? lol

I have a Cable Modem
rate 20000
cl_cmdrate 100
cl_updaterate 100
 
These vids were taken on LAN so there is nothing as far as i can see in terms of net settings that will sort this problem out, it seems deep routed in the game itself


:afro: an afro for good luck
 
CobaltIsLife said:
These vids were taken on LAN so there is nothing as far as i can see in terms of net settings that will sort this problem out, it seems deep routed in the game itself
:| didn't know that, this is truely frightening.
 
Hmm well the netcode for cs 1.6 and source is all set up for 56kers reason for that because during the beta days LPB "Low Ping Bastards" had a advantage over the 56kers so valve tweaked there netcode so it would be more towards the 56kers and the cable/dsl people still have a advantage but its not like it used to be and I think its causing some problems with people with cables/dsl. If I am wrong about anything please fix it for me :imu: ..
 
I see gross, blaring errors with these tests. Namely the fact that the fps on the computer that is doing the recording (likely the server for the game) is running at 17fps.
Woah, who'da thunk, if the server is running sub-acceptable framerates there will be inconsistencies.
These results would be far easier to believe if the pc it was recorded on was not so bogged down.
 
Iv been playing cs since beta 5. EVery time a version came out people would complain about the hitboxes. Back in the day they werent perfect sometimes even horrible but once you got to about cs 1.3 there really wasnt a problem. Cs 1.6 is pretty much perfect. Cs:s is also the same as 1.6. The hitboxes videos these kids show are retared. 1st of all while playing the game with your [*******RATES**********] Set perfect for each server you wont have ANY hitbox problems. I have a good conection and i set mine at 101 101 20000-25000 (depending on server) i get 0 choke 0 loss 10-20 ms. 25-35 ping. My hitboxes are perfect. Hate all these retards who complain about the game over and over again while they know shit about it. Keep inmind you also need to know what to set your interp at. Back in 1.5 it shifted the hitboxes behind or infront people. Now it takes away the server prediction./

xio2k3 said:
Hmm well the netcode for cs 1.6 and source is all set up for 56kers reason for that because during the beta days LPB "Low Ping Bastards" had a advantage over the 56kers so valve tweaked there netcode so it would be more towards the 56kers and the cable/dsl people still have a advantage but its not like it used to be and I think its causing some problems with people with cables/dsl. If I am wrong about anything please fix it for me :imu: ..

Your 100% wrong. Read what i wrote. 56kers used the ex_interp cmd back in 1.5 to shift the boxes etc. Now its all rates and interp being used together.
 
Raziel-Jcd said:
Iv been playing cs since beta 5. EVery time a version came out people would complain about the hitboxes. Back in the day they werent perfect sometimes even horrible but once you got to about cs 1.3 there really wasnt a problem. Cs 1.6 is pretty much perfect. Cs:s is also the same as 1.6. The hitboxes videos these kids show are retared. 1st of all while playing the game with your [*******RATES**********] Set perfect for each server you wont have ANY hitbox problems. I have a good conection and i set mine at 101 101 20000-25000 (depending on server) i get 0 choke 0 loss 10-20 ms. 25-35 ping. My hitboxes are perfect. Hate all these retards who complain about the game over and over again while they know shit about it. Keep inmind you also need to know what to set your interp at. Back in 1.5 it shifted the hitboxes behind or infront people. Now it takes away the server prediction./



Your 100% wrong. Read what i wrote. 56kers used the ex_interp cmd back in 1.5 to shift the boxes etc. Now its all rates and interp being used together.

how do i set .. whatever it is you are talking about? i really want to know how to do this..
 
I just want a cheat free game that works. But I guess people are too big a jerk to ever get anything close.
 
Raziel-Jcd, you sir are retarded.

We are all aware of the net settings that can increase the amount of data coming into the server but thats all it is, you are the one with the limited understanding, do you think playing since beta 5 impresses anyone?

There is a flaw in the code of the game which is completely unavoidable, go ask anyone with any real knowledge of game developing and they will tell you how flawed this game really is.

Change your rates all you want that will never change how the game was made.
 
I don't understand how people can say nothing is wrong with it I mean I have read and read net code stuff I have tested millions of settings the only settings that seems ok our 101 101 20000 and thats it an everyone keeps telling me to lower it but thats even worst when I do. I mean I can put my crosshair dead on someone and nothing will register something has to be wrong ! "its not my Internet connection I have Cable and I play awsome on 1.6 and other games I also tweaked my computer to get rid of some resources running in the background. If there is not a problem prove me wrong then ?
 
These two videos completely contradict one another. In the video showing the hitboxes, they are infront of the model. On the second video, they are behind. Explain.
 
Bolleh said:
These two videos completely contradict one another. In the video showing the hitboxes, they are infront of the model. On the second video, they are behind. Explain.

Not sure i can explain mate, i have limited to no knowledge of games in that sense though im not sure it is really that relevent, it would take a proper programmer to tell me otherwise.

Best asking a programmer what is up there.
 
bullets not hitting another player are most likely due to packet loss. Check your lan dosn't have any collision issues.
 
well I guess I'm the only soul on the earth that has no problems with this.....
 
CobaltIsLife said:
Not sure i can explain mate, i have limited to no knowledge of games in that sense though im not sure it is really that relevent, it would take a proper programmer to tell me otherwise.

Best asking a programmer what is up there.
It is relevent, there is no logical reason that this problem would suddenly reverse itself. All those two videos prove is that atleast one of them is bollocks.
 
This issue has been around since old CS days! Why bring it up now?
 
nagual678 said:
one is to very rightfully ask why CS:S gets so many ping issues as it's exactly the same game as CS 1.6 with.. barrels/cabinets/etc not being really movable ?
Oh dear.
 
There is a problem with Counter Strike: Source. CS:S just doesn't feel right, and so much bs keeps happening during games. I just wish VALVe would either acknowledge or fix these issues.
 
Erm, does this issue of the hitboxes lagging behind have anything to do with "cl_lagcompensate 1"?

I haven't tried it yet as I can't get on my computer right now, but lag compensation does just that. Because there's a delay for 56kers from when they click to shoot, and when they actually do, they have to aim infront of everyone while trying to kill 'em. The lag compensation means that when the 56ker is aiming at someone and shooting, the bullets will still hit the person even though they fall behind, because the hitboxes are lagging behind for them. If you get me. :p

Somebody try it I wanna know :)
 
This video was posted before, and this was also said before: why the hell does the name of the teammate pop up when you hold the crosshair over him? It doesn't react to the wireframe hitbox, just to the terrorist model. Call me stupid, but don't team tags also use hitboxes to determine if a player is under your crosshair? To me it just says that the hitbox visualisation isn't accurate and the real hitbox is just fine at the location of the player model.
 
Xio2k3 said:
odd.. No wonder why that guy would not die when I was playing CS:S last night I was right behinde him and I started shooting I was burst shooting at his head first and no hs then I just held the fire button down hopeing to kill him then the guy turns around and hs me
That, sir, is why you should knife when you are behind someone. 100% accuracy :p

Ckabusk said:
This is why you guys should play America's army!!! www.americasarmy.com and download it for FREE!!
You realise advertising is banned unless admin agree? Yeah, and why are you on a half life2 fan forum, not playing AA?

Also, agreed, one, hitboxes are slightly laggy, but I have no problem with it, since I actually have some skill in the field.

And digging up 1 month old threads is pointless... Utterly pointless...
 
CobaltIsLife said:
Raziel-Jcd, you sir are retarded.

We are all aware of the net settings that can increase the amount of data coming into the server but thats all it is, you are the one with the limited understanding, do you think playing since beta 5 impresses anyone?

There is a flaw in the code of the game which is completely unavoidable, go ask anyone with any real knowledge of game developing and they will tell you how flawed this game really is.

Change your rates all you want that will never change how the game was made.


The only problem is your incessant ****en whinging and your full of shit posts. The fact remains that these so called "professionals" are now used to playing on the, what i believe is flawed 1.6. If they took the time to actually play the game rather than whining like the rest of the world gives a shit about them they would relise that the game is built on virtually the exact same framework.
You have gotta love people who have knowledge of game developing, now they can decompile code using only their brainpower so they can give some load of shit story about how a competitors product is flawed, fan -****en -tastic.
 
I installed the game, never changed my rates and I've never had issues with hitboxes.
My tip? play on servers where the other players ping in a similar range to yourself.
 
must admit i dont have probolems either, unless i join a distant server and lag
edit: and a few server prediction errors on laggy servers
 
yay lets make a modern game that still uses Hitboxes instead of the infinitely better per-pixel hit detection![/sarcasm] All seriousness though the hitbox lag isnt really that bad it only causes 5% of my deaths
 
Uni-Ball said:
yay lets make a modern game that still uses Hitboxes instead of the infinitely better per-pixel hit detection![/sarcasm] All seriousness though the hitbox lag isnt really that bad it only causes 5% of my deaths
Well find a server that has about 20 ping on it, and join. Now don't aim BEHIND the player, like people say, but aim at him. Most hitbox errors are actually while spectating, and it's because of the time it takes to recieve both pieces of information (Where the player your looking at is, and where the player the player is aiming at is). When playing there's rarely (If at all) Hitbox lag, unless you're on a high-ping server.
 
I turned on the showhitboxes command (or whatever the name is) while playing with bots and while spectating I saw that when the bot crouched, the hitboxes were still as if he was standing. When I was playing a few minutes later, when the bot crouched I shot at the air right above him and didn't hit him, what means the hitboxes weren't actually there. This command that shows hitboxes is just buggy and doesn't show where the hitboxes really are. They cannot be, therefore, considered as a proof of the hitbox problem.
 
Back
Top