Battlefield 3 Running Smoothly in FPS but lagging behind other players

glassesmcgee

Honorable
Dec 15, 2012
10
0
10,510
Hopefully someone has experienced this.

When I play BF3 lately I have been noticing that while it runs smoothly (80-110 FPS), I am experiencing what I call loss of frames, where someone jumping around a corner is suddenly beside me rather than in front of me, or where when shooting at someone I am dead as I begin (we both see eachother at the same time) to shoot. I am not a bad player, not the best but not the worst. http://battlelog.battlefield.com/bf3/soldier/glassesmcgee/stats/352169632/. I would say it is most like I am behind other players in time.

I have an ADSL2+ connection, which does currently have issues (there is a fault in the line that causes random dropouts, which my telco is looking into), however, despite this I get around 30 ping in any server.

Hopefully someone out there has experienced this problem as well, or has ideas as to what may be causing it.

p.s. I have turned UPNP off both on my router and in windows 7 but to no avail.

My computer setup:I have two gigabyte 560ti's in SLI, a 2600 I7, ASRock Z77 Extreme 4 motherboard, a kingston 120gb SSD running windows 7 and a caviar black 1TB running BF3. Plus deathadder mouse and blackwidow keyboard.
 
Solution
It is 100% your network connection. Given the response times of 360ms+ (over a third of a second) to each 32 byte packet you can imagine what a full 1500 byte packet will respond like. Try this from a command prompt to any of the IP addresses in your reply, for example:

C:\Ping 31.222.133.87 -l 1472 -t

if you want to know the parameters just type ping into the command prompt, but basically:

H:\>ping

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] target_name

Options:
-t Ping the specified host until stopped.
To see statistics and continue - type Control-Break;
To stop...
not the HDD's.

its more likely to be bad ping on either your part or the person that it suddenly appearing, essentially if they have bad ping then their update to the server and hence to you is delayed, so the server doesn't know where they are and then suddenly does.

some servers ban players with higher pings for this type of reason.

of course given your adsl problem it could be you, you temporarily stop receiving updates and then people suddenly 'appear' when you do get an update.
 

TuffLittleUnit

Distinguished
Jun 7, 2009
35
0
18,540
Can't see it being hardware related given your rig. The problem you describe sounds like it's latency related. I occasionally get the same problem and I have a super fast, super reliable connection. The thing is that other players don't - BF3 definitely seems to favor players with pings over 100ms as it seems to compensate unfairly. Still, if your problem is persistent and across different servers then it sounds like your broadband connection to me. Have you done any quality of service tests to see how consistent your connection is?
 

DragonClaw

Honorable
Nov 9, 2012
141
0
10,710


It is most probably the Internet. Or the server you play in. Try servers with lower ping.

Also, see if this helps. Just to give it a try. Looking at your rigs mostly it will not work, but what'st he harm in trying?
Open up Nvidia Control Panel (Download it if you do not have it already).
Then go to Manage 3D Settigns, and make sure Battlefield 3 exe is added to the list.
Change Maximum Pre-Rendered Frames to "1".

I had same issue with my GTX 550 Ti, and this fixed things I think.
 

glassesmcgee

Honorable
Dec 15, 2012
10
0
10,510



Ok I used HRPING and I've got to say it was the most helpful of the lot. Looking at the results which I will post below, it appears that my connection is the problem. I am still struggling to understand the results HRPING posted but from previous experience, when I had cable internet at another house, these are not great results.

D:\>Downloads\hrping-v504\hrping www.cfos.de
This is hrPING v5.04 by cFos Software GmbH -- http://www.cfos.de
Source address is 192.168.1.96; using ICMP echo-request, ID=d411
Pinging www.cfos.de [194.95.249.23]
with 32 bytes data (60 bytes IP):
From 194.95.249.23: bytes=60 seq=0001 TTL=47 ID=75c3 time=383.840ms
From 194.95.249.23: bytes=60 seq=0002 TTL=47 ID=75c4 time=382.679ms
From 194.95.249.23: bytes=60 seq=0003 TTL=47 ID=75c5 time=383.131ms
From 194.95.249.23: bytes=60 seq=0004 TTL=47 ID=75c6 time=383.224ms
Packets: sent=4, rcvd=4, error=0, lost=0 (0.0% loss) in 1.883475 sec
RTTs in ms: min/avg/max/dev: 382.679 / 383.218 / 383.840 / 0.413
Bandwidth in kbytes/sec: sent=0.127, rcvd=0.127

D:\>Downloads\hrping-v504\hrping www.abc.net.au
This is hrPING v5.04 by cFos Software GmbH -- http://www.cfos.de
Source address is 192.168.1.96; using ICMP echo-request, ID=5c1b
Pinging www.abc.net.au [125.252.225.174]
with 32 bytes data (60 bytes IP):
From 125.252.225.174: bytes=60 seq=0001 TTL=53 ID=cbf5 time=309.305ms
From 125.252.225.174: bytes=60 seq=0002 TTL=53 ID=cbf6 time=310.586ms
From 125.252.225.174: bytes=60 seq=0003 TTL=53 ID=cbf7 time=307.248ms
From 125.252.225.174: bytes=60 seq=0004 TTL=53 ID=cbf8 time=321.213ms
Packets: sent=4, rcvd=4, error=0, lost=0 (0.0% loss) in 1.821517 sec
RTTs in ms: min/avg/max/dev: 307.248 / 312.088 / 321.213 / 5.401
Bandwidth in kbytes/sec: sent=0.131, rcvd=0.131


D:\>Downloads\hrping-v504\hrping www.google.com
This is hrPING v5.04 by cFos Software GmbH -- http://www.cfos.de
Source address is 192.168.1.96; using ICMP echo-request, ID=8c15
Pinging www.google.com [173.194.38.176]
with 32 bytes data (60 bytes IP):
From 173.194.38.176: bytes=60 seq=0001 TTL=53 ID=c386 time=189.843ms
From 173.194.38.176: bytes=60 seq=0002 TTL=55 ID=c386 time=192.987ms
From 173.194.38.176: bytes=60 seq=0003 TTL=53 ID=c386 time=190.186ms
From 173.194.38.176: bytes=60 seq=0004 TTL=55 ID=c386 time=192.534ms
Packets: sent=4, rcvd=4, error=0, lost=0 (0.0% loss) in 1.693176 sec
RTTs in ms: min/avg/max/dev: 189.843 / 191.387 / 192.987 / 1.387
Bandwidth in kbytes/sec: sent=0.141, rcvd=0.141

D:\>Downloads\hrping-v504\hrping battlelog.battlefield.com
This is hrPING v5.04 by cFos Software GmbH -- http://www.cfos.de
Source address is 192.168.1.96; using ICMP echo-request, ID=c41a
Pinging battlelog.battlefield.com [31.222.133.87]
with 32 bytes data (60 bytes IP):
From 31.222.133.87: bytes=60 seq=0001 TTL=232 ID=7947 time=362.683ms
From 31.222.133.87: bytes=60 seq=0002 TTL=232 ID=8803 time=367.495ms
From 31.222.133.87: bytes=60 seq=0003 TTL=232 ID=918e time=367.129ms
From 31.222.133.87: bytes=60 seq=0004 TTL=232 ID=9adf time=362.988ms
Packets: sent=4, rcvd=4, error=0, lost=0 (0.0% loss) in 1.863789 sec
RTTs in ms: min/avg/max/dev: 362.683 / 365.073 / 367.495 / 2.244
Bandwidth in kbytes/sec: sent=0.128, rcvd=0.128
 

Sinistercr0c

Honorable
Dec 16, 2012
718
0
11,360
It is 100% your network connection. Given the response times of 360ms+ (over a third of a second) to each 32 byte packet you can imagine what a full 1500 byte packet will respond like. Try this from a command prompt to any of the IP addresses in your reply, for example:

C:\Ping 31.222.133.87 -l 1472 -t

if you want to know the parameters just type ping into the command prompt, but basically:

H:\>ping

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] target_name

Options:
-t Ping the specified host until stopped.
To see statistics and continue - type Control-Break;
To stop - type Control-C.
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-l size Send buffer size.
-f Set Don't Fragment flag in packet.
-i TTL Time To Live.
-v TOS Type Of Service.
-r count Record route for count hops.
-s count Timestamp for count hops.
-j host-list Loose source route along host-list.
-k host-list Strict source route along host-list.
-w timeout Timeout in milliseconds to wait for each reply.

An ethernet packets maximum data portion is 1472 bytes, packet sizes beyond this point are fragmented into 1472 byte chunks. The -l parameter allows you to specify the data portion size of the packet. The -t parameter runs the ping constantly so you can see realtime variations in latency.

As I say its your network connection. Run some ping captures (copy/paste them into a text file and mail them to your ISP demanding they take action.) A decent 10mb pipe should have latencies around 20-30ms to any other IP within your own country. For example I get anything up to 50ms in UK/Europe and 100ms+ if I join an American BF3 server.

Hope this helps
:\>
 
Solution

glassesmcgee

Honorable
Dec 15, 2012
10
0
10,510
Thanks, i used that command and I did get even worse (up to 400ms and then request timed out) responses. I will be sending some screenshots to my isp and hopefully getting some kind of response, otherwise will just change provider.

Thanks for the help guys, especially Sinistercr0c and Scott_D_Bowen