BF2S Forums Possible way to fix bad hitreg!

I'll try it out also. Oh yea, a little question: is there a list of all possible cvar values somewhere?

Towelly wrote:

Is this anything like the latency compensation code thing you can do?

(I'll go and try it soon if I can actually log in)

yeah, but I never really noticed a difference with that one

hitreg is what?  thanks.

i will try it later, if this works buttsecks for sarge

Thanks for the tip.

Off topic: Don't you think your sig is kind of harsh? I mean I hate everyone who plays BF2 as well, but jeez..

StormEye wrote:

So does it mean when I shoot someone in the head with a sniper rifle, and see dust comeout but no kill, it is a bad hit reg?

yes

PS: I'm against solo TV guiding. Look at the space the dude has to crawl through to switch seats. You think the guy and crawl through that almost instantly, fire a tv missle, guide it, then crawl back through that tiny space and regain control of the chopper before it spins out of control and crashes? I think not.

Last edited by Dex Luther (2006-10-05 13:19:16)

Will try when I get a chance.

Sweet, gotta try this out later... anyone remember what the Latency compensation code was? I'm trying to remember it but my mind is drawing a blank.

My main problem is with knifing. I have gotten so many hits on people that just don't kill them. Pisses me off, hopefully this will change that.

GotMex? wrote:

Sweet, gotta try this out later... anyone remember what the Latency compensation code was? I'm trying to remember it but my mind is drawing a blank.

My main problem is with knifing. I have gotten so many hits on people that just don't kill them. Pisses me off, hopefully this will change that.

SettingsManager.floatSet GSDefaultLatencyCompensation <VALUE>

For all these ones just go

C:\Program Files\EA GAMES\Battlefield 2\mods\bf2\Settings\Usersettings

Last edited by Towelly (2006-10-05 13:58:30)

Omfg. it works. It actually works....


today was the first time i have been able to kill 4 people with on clip again! Usually it takes like a clip because of rego! But now i can own again! woo hoo!

Darkhelmet wrote:

Hmmm... I might try it I don't know yet.

do it. If you suffer from poor hit rego, do it. It worked perfectly for me.

One would imagine you would want to set it to something based on your actual latency to the server. Interpolation is effectively the process of following/calculating a line from one point to another point, but it is used in a huge variety of contexts in 3D gaming environments. I would imagine it means interpolating where people are walking to.

i.e. you receive a message from the server every <amountoflatency> ms saying where everyone is. So, for all the time in between those updates you, as the client, are interpolating all the players paths to make a reasonable estimate of where they would have moved to, by just following a line in the same direction as they were moving when you last got an update.

By setting your interpolation time to be longer as you are, perhaps you are instructing the server to process your hit detections assuming that you are under the effects of the movement interpolation for longer (to a more realistic length of time, in the cases where this works).

Could be a few other things though, as it does seem a little unlikely to me that they would allow you to define how long you're under the effects of interpolation for. Elsewise people could set it to like 2 seconds, shoot at where the person WOULD be if they'd continued in a straight line from 2 seconds ago, and kill them. Even if the person had changed direction completely. Although I suppose that's not really much of an advantage, as it'd be hard to predict.