Hit Detection

[Ruci]

Some of the GW guys and I have been playing on WiH alot lately. Last night, one of the guys was just saying flat out the hit detection wasn't right. I was runnin around with a shotgun myself and it was pretty damn accurate. I'd have the shotgun in someone's chest and it's not that I didn't kill the guy it's simply that the shots didn't register.

So we moved over to a different server for a little and wow the difference was night and day. So I'm really not sure whats going on but we were having some really significant hit detection issues on the conquest server.

=(

[JustMeBF2]

I experienced a lot of lag on the WiH servers Conquest and Rush Chicago yesterday.
It is easy for me to recognize lag as I always lose knife fights.
I tried several others and still had lag. I finally found one without lag and owned.
My machine and ISP are both in good shape so I think it relates more to the code, RSAs and EA's servers.
I always see more lag in the evening then during the day.

[FiLTHY_SNiPER]

I get infuriated with the hit detection all the time, but I haven't been playing much on non-WiH servers to see if there's a difference.

[Crotch-Rot]

I definitely have lag on the servers. It's lag bc I'd be running behind cover and then getting killed from the guy who was shooting at me before I ran behind cover. Sometimes, I'd empty about 10 rounds into a guy at point blank only to have him knife me. :/

I haven't played much on non-WiH servers to tell if it's our servers or a problem with the client and/or servers in general.

[=HR=Gumby!!!]

Sometimes, I'd empty about 10 rounds into a guy at point blank only to have him knife me. :/


This is going to be the thing that makes me quit playing despite how long I've been waiting. I can't count the times that I've been crouched down, firing from a stationary position only to have someone run right through my stream of bullets to knife me. If Dice wanted to make melee so powerful in this game they should have given us swords and said f*** the guns.

[JustMeBF2]

Do not rule out the "ceramic chest plate" perk, its similar to the juggernaut in COD.
A buddy and I checked out a suggestion from another about this perk on a empty server and the solution is funny.

When the enemy has the "ceramic chest plate" it is best to shot him in the head or the nuts.

I think I remember something like this in BF2 where the different classes had more built in body Armour and someone pointed out the legs were unprotected.
ie shoot them in the foot.

[antigen]

People that have a rank of 4 don't have the ceramic chest plate perk...

I was seriously about to throw my pc out the window, quit gaming forever, and take up knitting last night I was so frustrated.

Sorry to those who were around long enough to hear my incessant ranting...

I don't know if it's a server issue, or a client issue, or my dinky 486 (with TURBO!!).

Just kidding. my system isn't that crappy.

But seriously... my ping is about 90 to chicago.. I have an 8800gt.. and a core2duo. Settings are on medium, and the game runs great. Except I paid $50 for a game that is causing me to have high blood pressure and brain hemorrhaging.

Ugh..................

[Bonez]

Crotch, they are probably routed through the same servers that i am to the Chicago servers.

AS6453.net is the host for the ones that I'm getting huge loss from, anywhere from 500+ms to complete packet loss.

[JustMeBF2]

People that have a rank of 4 don't have the ceramic chest plate perk...

I was seriously about to throw my pc out the window, quit gaming forever, and take up knitting last night I was so frustrated.

Sorry to those who were around long enough to hear my incessant ranting...

I don't know if it's a server issue, or a client issue, or my dinky 486 (with TURBO!!).

Just kidding. my system isn't that crappy.

But seriously... my ping is about 90 to chicago.. I have an 8800gt.. and a core2duo. Settings are on medium, and the game runs great. Except I paid $50 for a game that is causing me to have high blood pressure and brain hemorrhaging.

Ugh..................

I know it won't look as good but setting your machine to low settings will decrease your problems.
In first person shooters, higher frames per second always helps with teh ownage.

[Ruci]

I'm just posting this to say that really I've seen it on this server and it seems to be a server side issue. I played on a different "cannon fodder gaming dallas, TX" server and my shots were all registering. I'm not trying to promote a different server but I'm just saying that is one that I saw had good hit detection and it really made the game a different story.

Not trying to bag on WiH I like playing with you guys and love the servers except they're just not registering hits properly like other servers currently are and it really is something that needs to be looked at.

[Ruci]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Rooch>tracert 68.232.166.143

Tracing route to 68.232.166.143 over a maximum of 30 hops

1 9 ms 17 ms 11 ms gateway.cca2-arc.reshsg.uci.edu [169.234.64.121]

2 9 ms 6 ms 13 ms kazad-dum-vl123.ucinet.uci.edu [128.200.2.222]
3 3 ms 2 ms 2 ms dc-lax-dc1--dc-uci-egm.cenic.net [137.164.24.41]

4 14 ms 10 ms 9 ms dc-lax-core1--lax-agg2-ge.cenic.net [137.164.46.
111]
5 21 ms 33 ms 52 ms dc-svl-core1--lax-core1-ge.cenic.net [137.164.47
.24]
6 28 ms 36 ms 30 ms dc-svl-px1--svl-core1-10ge-1.cenic.net [137.164.
46.205]
7 12 ms 25 ms 25 ms te4-4-482-tr01-plalca01.transitrail.net [137.164
.131.61]
8 58 ms 16 ms 23 ms paix.99.xe-0-1-0.cr1.pao1.us.nlayer.net [198.32.
176.13]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 83 ms 87 ms 86 ms po3-30g.ar1.dfw1.us.nlayer.net [69.31.63.126]
13 80 ms 82 ms 90 ms as20473.te5-2-106.ar1.dfw1.us.nlayer.net [69.31.
63.38]
14 85 ms 100 ms 94 ms 68.232.166.143

Trace complete.

C:\Users\Rooch>

[Ruci]

then to a 32-player server hosted by art of war central in dallas

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Rooch>tracert 207.210.252.156

Tracing route to 207.210.252.156 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms gateway.cca2-arc.reshsg.uci.edu [169.234.64.121]

2 1 ms 1 ms 1 ms kazad-dum-vl123.ucinet.uci.edu [128.200.2.222]
3 5 ms 5 ms 3 ms dc-tus-dc--uci-ge.cenic.net [137.164.24.33]
4 3 ms 2 ms 3 ms dc-lax-core2--tus-agg1-10ge.cenic.net [137.164.4
6.6]
5 4 ms 4 ms 3 ms dc-lax-peer1--lax-core2-ge.cenic.net [137.164.46
.118]
6 3 ms 2 ms 3 ms gi1-1--46.tr01-lsanca01.transitrail.net [137.164
.131.245]
7 4 ms 3 ms 2 ms eqix.lsan.twtelecom.net [206.223.123.36]
8 69 ms 70 ms 69 ms hagg-03-ge-0-0-0-460.dlfw.twtelecom.net [64.129.
234.4]
9 37 ms 41 ms 45 ms 206.123.64.34
10 36 ms 36 ms 37 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]

11 37 ms 38 ms 39 ms dallas.colocrossing.com [207.210.239.250]
12 35 ms 37 ms 39 ms 207.210.252.156

Trace complete.

C:\Users\Rooch>

[SnaKe]

I've asked Gs to check the server & it's network connection.

ruci, your route to our dallas server compared to that other dallas server is obviously not as good because it's a couple more hops and has much higher latency. There isnt anything GS can do about that. Those 'Request timed out's are routers that dont respond to pings for security reasons. If it wasnt you wouldnt go any further.

Sometimes ISP's peer with other companies to make routing more efficient. That maybe the case of the Art of war central server.

i ran a trace:
Tracing route to 68.232.166.143 over a maximum of 30 hops

1 1 ms <1 ms 2 ms home [192.168.1.254]
2 21 ms 21 ms 21 ms 76-240-203.lightspeed.tukrga.sbcglobal.net [76.240.20.3]
3 20 ms 36 ms 22 ms 76.201.204.2
4 22 ms 20 ms 20 ms 76.201.208.20
5 21 ms 21 ms 20 ms 76.201.208.8
6 22 ms 21 ms 24 ms 70.159.177.248
7 24 ms 23 ms 22 ms 12.83.2.166
8 21 ms 23 ms 21 ms 12.83.2.137
9 45 ms 47 ms 22 ms 74.175.192.66
10 24 ms 23 ms 22 ms cr1.attga.ip.att.net [12.122.141.186]
11 73 ms 22 ms 22 ms attga01jt.ip.att.net [12.122.80.185]
12 41 ms 40 ms 40 ms 192.205.36.210
13 55 ms 54 ms 56 ms as3549.xe-5-1-0.cr1.dfw1.us.nlayer.net [69.31.63.214]
14 57 ms 56 ms 55 ms po3-30g.ar1.dfw1.us.nlayer.net [69.31.63.154]
15 56 ms 56 ms 56 ms as20473.te5-2-106.ar1.dfw1.us.nlayer.net [69.31.63.38]
16 56 ms 55 ms 56 ms 68.232.166.143

Trace complete.

[Ruci]

I'll get my other buddy to tracert to WiH as well tomorrow, but I'm curious to see what the server provider says. Because it's about a 50/50 coin flip whether or not a shotgun shot at less than 10m hits a guy it just confuses the hell outta me.

[JustMeBF2]

PingPlotter Standard free for 30days then still usable.

http://www.pingplotter.com/download.html

http://img535.imageshack.us/img535/6362/pingm.jpg

[Rajun Cajun]

Because it's about a 50/50 coin flip whether or not a shotgun shot at less than 10m hits a guy it just confuses the hell outta me.

Same thing happened to me last night with a shotgun. Guy was crouched, not moving or looking at me and it took three shots to get him point blank. The first two didn't register a thing.

[Rigs]

Was having alot of trouble on certain servers as well. What's strange is medium to long range sometimes shots seem to register better, but close range...forget it. Someone can run in a straight line towards me from 15m away while i'm firing and just knife me in the face and walk away with 60% health.

[Crotch-Rot]

I don't remember BF2 having this bad of a problem with hit detection/registration. Lots of people are reporting this problem on the EA UK's site as well.

[Rajun Cajun]

Same thing happened to me last night with a shotgun. Guy was crouched, not moving or looking at me and it took three shots to get him point blank. The first two didn't register a thing.

And again...on two other (non WiH) servers as well. Had to knife the guy to get anything to register.

[Drayu]

I don't think it is WiH specific. I think there are a variety of issues that cause it at this point. :(

[Crotch-Rot]

I don't know if it was today's update or what, but my hit detection/lag is gone. The only other thing I changed was this setting

RenderAheadLimit=0

originally, it was set to 2. I am not seeing the lag any more. Hits are hitting as expected and feels right. I'm not sure if it's this setting or the patch, but I thought I'll post here to see if you guys have experimented with this before and what your results are.

[Ruci]

http://forums.electronicarts.co.uk/battlefield-bad-company-2-pc-beta/895745-renderaheadlimit-0-20-extra-fps.html

Theres a thread on it in the uk forums. No real conclusion there except the dice guy said it was a fix for laggy input in the beta. I may have to try this later.

[Ruci]

Hit detection was much better tonight. Not sure why but it definitely was on the conquest server.

[Bonez]

better for you, BS for me, every time i saw you actually shoot me it was through a building, and less of my hits actually hit then normal.

[Crotch-Rot]

Hit detection was much better tonight. Not sure why but it definitely was on the conquest server.

I played on both Conq and Rush, both were good last nite with hit detection. I'm willing to live with the fact that Bonez' has shitty hit detection. =)

[SnaKe]

Thanks for the info.

[FiLTHY_SNiPER]

Maybe it's my connection, but I played 2 rounds today where even if the guy was standing still, 20 ft away and I'm blasting him in the chest with an XM8, nothing is registering (I'm talking controlled bursts, too).

Maybe I'm lagging like hell, but all through those 2 rounds, I was pumping guys with bullets and not killing them.
The first couple rounds I played I did very well because my shots were actually registering, but as time went on I noticed I was playing the exact same but could not kill anyone.

Is there some kind of latency log with information about spikes I can look up on my PC or is there one associated with the server, even?

[JustMeBF2]

I don't know if it was today's update or what, but my hit detection/lag is gone. The only other thing I changed was this setting

RenderAheadLimit=0

originally, it was set to 2. I am not seeing the lag any more. Hits are hitting as expected and feels right. I'm not sure if it's this setting or the patch, but I thought I'll post here to see if you guys have experimented with this before and what your results are.

The thing to do would be to set it back to 2 and see if you still have your performance increase.

[SoupyC]

Maybe it's my connection, but I played 2 rounds today where even if the guy was standing still, 20 ft away and I'm blasting him in the chest with an XM8, nothing is registering (I'm talking controlled bursts, too).

Maybe I'm lagging like hell, but all through those 2 rounds, I was pumping guys with bullets and not killing them.
The first couple rounds I played I did very well because my shots were actually registering, but as time went on I noticed I was playing the exact same but could not kill anyone.

Is there some kind of latency log with information about spikes I can look up on my PC or is there one associated with the server, even?


I've been getting that a lot lately since they 'fixed' hit detection with the latest rev...

[SnaKe]

Let's see how it is with today's new update for the client. It removes the network debugging that may have been cause hit detect problems.

There is no ping/latency logs on the server. You can run PingPlotter from your PC if you want client side monitoring.

[Ruci]

Last night again I was getting crap hit detection. Ugh. Lets see how it is today.

[FiLTHY_SNiPER]

Pretty good tonight until a bunch of laggers came on and played Matrix for a bit.

[Bonez]

it didn't get any better after you left, had 2 guys basically carry their entire team.