DOD:S shot registry or lack thereof.

Silent_Predator

EGO Addict
Joined
May 9, 2010
Messages
1,281
Is it just me or has the shot registry of this game gone straight to h*ll? I know the "points" are a lie, but K:D is not. I have been haveing No Reg Hits on headshots, chest shots and da*n near point blank. I am getting frustrated watching my points go down, as my K:D gets better. Its not my fps, I get average of 125fps... its not my ping which is under 60ms at all times... and its not my crosshair as I run a pin point red dot. What the h*ll is going on with these so-called" updates".... Valve is ruining this game.

I have gone from the 400's to 1000's in rank because of this registry issue.

Funny how Hit Boxes in CS:S and TF2 work like magic but DOD:S is the redheaded step-child.

I was in an Xfire group called "The DoubleEdged Sword" -- it was a group of gamers, by invite only, to talk to the game designers and hardware producers about any issues or point of interest. One of these chats was on the future of CS:S.... the first thing that was talked about was "updated hitboxes". DOD:S did NOT get that update... it was CS:S only.

I swear that on somedays, the opposeing team is made of Kevlar.

:facewall:
 
Last edited:
yes... DoD:S hitreg has always been notoriously bad...

The most common solutions, by order, to this problem are:

1) Play assault class

2) Check your rates

3) Cry...


I personally have settled for option 3 :)


-K^^
 
I didnt have reg issues until the last 2 updates or so.... now its hit or miss when I join a server if I have good reg or I dont. My rates are excellant - my interp is set right and I run cl_lagcomp_errorcheck 1 .... I just dont understand it... I can shoot someone in the face, blood flys everywhere and no damge is done. H*ll, 1.3 had/has better hit boxes then this.
 
Last edited:
I didnt have reg issues until the last 2 updates or so.... now its hit or miss when I join a server if I have good reg or I dont. My rates are excellant - my interp is set right and I run cl_lagcomp_errorcheck 1 .... I just dont understand it... I can shoot someone in the face, blood flys everywhere and no damge is done. H*ll, 1.3 had/has better hit boxes then this.

Curious, did you set your rates in your autoexec.cfg or did you do it through console one day? And what are they? What is your interp?
 
I didnt have reg issues until the last 2 updates or so.... now its hit or miss when I join a server if I have good reg or I dont. My rates are excellant - my interp is set right and I run cl_lagcomp_errorcheck 1 .... I just dont understand it... I can shoot someone in the face, blood flys everywhere and no damge is done. H*ll, 1.3 had/has better hit boxes then this.

Same thing has been happening to me. Horrible registry problems. I can spray a good 5 STG44 shots on a head and see the blood splatter on the walls, but they still have 100HP. :cursing:

I set some better rates the other day using the Rate guide somewhere here in the forums, and it did help, but it's nowhere near as good registry as I had before the last few updates.
:confused1:
 
This^^ Im having this same problem:( Its really pretty bad ha i cant even snipe anymore ill get about 1 kill out of every 7 shots that were right on.

i can contest to that! have had a few kills stolen from me here and there.
 
my curent rates:

cmdrate - 66
updaterate - 66
interp - 0.01
rate 25000
interp_ratio - 1
cl_smooth 1
lagcomp_errorcheck - 1
 
Last edited:
lol my kdr always goes up and on anzio my points go way up. I hate points but love my kdr
 
Try this

rate 30000
cl_cmdrate 101
cl_interp 0
cl_lagcomp_errorcheck 1
cl_lagcompensation 1
cl_smooth 0
cl_smoothtime 0.1
cl_updaterate 101
cl_interp_ratio 0
cl_interpolate 0

What iam using
 
Try this

rate 30000
cl_cmdrate 101
cl_interp 0
cl_lagcomp_errorcheck 1
cl_lagcompensation 1
cl_smooth 0
cl_smoothtime 0.1
cl_updaterate 101
cl_interp_ratio 0
cl_interpolate 0

What iam using

cmdrate and updaterate won't go past 66, those are our server's maximum supported values. lagcompensation is enabled by default so he would have had to turn that off. I don't recommend using 0 interp on a 66tic/public server. The odds are good that you will lose a server update from time to time and then your game will appear jerky. Interp is designed to smooth out the game and has no effect on hitboxes whatsoever. The lower the interp, the more accurate and up-to-date the players around you will be. Ideal interp is "white" interp. For your rates silent that should be at least .015 (which will give you your first yellow interp value) or .033 which will be a solid white interp. Setting interp lower than the rate you receive updates from the server will cause jerkiness. That's orange/yellow interp. White interp is perfectly timed so you can interpolate between two snapshots even if one is lost, enemy players will never appear jerky.

Those settings are for competitive play DDay, I can't imagine how well they run on a public server. My match/scrim cfg looks pretty close to that though so I can't say it's wrong, just inappropriate for pubs I think
 
cmdrate and updaterate won't go past 66, those are our server's maximum supported values. lagcompensation is enabled by default so he would have had to turn that off. I don't recommend using 0 interp on a 66tic/public server. The odds are good that you will lose a server update from time to time and then your game will appear jerky. Interp is designed to smooth out the game and has no effect on hitboxes whatsoever. The lower the interp, the more accurate and up-to-date the players around you will be. Ideal interp is "white" interp. For your rates silent that should be at least .015 (which will give you your first yellow interp value) or .033 which will be a solid white interp. Setting interp lower than the rate you receive updates from the server will cause jerkiness. That's orange/yellow interp. White interp is perfectly timed so you can interpolate between two snapshots even if one is lost, enemy players will never appear jerky.

Those settings are for competitive play DDay, I can't imagine how well they run on a public server. My match/scrim cfg looks pretty close to that though so I can't say it's wrong, just inappropriate for pubs I think

Use this rates becouse i play alot competitive yeah. il will recommend a 033 interp value to a pub server.
 
This^^ Im having this same problem:( Its really pretty bad ha i cant even snipe anymore ill get about 1 kill out of every 7 shots that were right on.

ahah, and that's not good even for u :P

Just compensate. aim a bit in front of the target and it will fix it.

I hope that was a joke :scared:

if so,

hahahahaha

i would have to agree with Ron on that, aiming in front doesn't help :P cause i have tried lol
 
What about the interp_ratio and the cl_smooth?

cl_interp_ratio 1 and cl_interp .033

cl_smooth 1 will show you player models a little less accurate but you'll have a smoother gameplay, the server will move the player model FROM where your client predicted it would be if smooth is on, and it does that "smoothly", less jittery. With cl_smooth 0, the server just teleports the player model to the correct position if the client prediction was wrong, so it's more jerky but you see the most up-to-date and accurate player models.

I use smooth 0.
 
cmdrate and updaterate won't go past 66, those are our server's maximum supported values. lagcompensation is enabled by default so he would have had to turn that off. I don't recommend using 0 interp on a 66tic/public server. The odds are good that you will lose a server update from time to time and then your game will appear jerky. Interp is designed to smooth out the game and has no effect on hitboxes whatsoever. The lower the interp, the more accurate and up-to-date the players around you will be. Ideal interp is "white" interp. For your rates silent that should be at least .015 (which will give you your first yellow interp value) or .033 which will be a solid white interp. Setting interp lower than the rate you receive updates from the server will cause jerkiness. That's orange/yellow interp. White interp is perfectly timed so you can interpolate between two snapshots even if one is lost, enemy players will never appear jerky.

Those settings are for competitive play DDay, I can't imagine how well they run on a public server. My match/scrim cfg looks pretty close to that though so I can't say it's wrong, just inappropriate for pubs I think

I changed my interp to 0.015 and it has my lerp at 16.7ms(orange) game play isnt choppy so I'll see if I found my sweet spot or not.
 
rate 30000
cl_cmdrate 66
cl_interp 0.033
cl_updaterate 66
cl_interp_ratio 1
 
Back
Top