Obi

I was not on the server when I did this. Says "packet loss" here and there. I take it thats not normal?

On a related note, is it normal for download speed to go from 100 KB/sec to 10KB/sec depending on the time of day? This drop is a general drop in download speed from downloading from a bunch of different places.

Lorian

Damn that's a lot of packet loss, not good. Wait for some of the more experienced guys come along know, they will tell you what to do.

__________________

PanzerHans

Packet loss is hard to determine by ping. A lot of hightrafficed routers will not answer ping request when they work under heavy load. This means that a normal datapacket will go through but a ping request will be skipped. The jitter parts looks pretty heavy.

Now all uncertanties aside I would say that the routers on your way that displays the worst jitter(variations in delay on the respone) is not doing your gaming experience any good.

You should set up the pingtool to run for more than the 10 minutes you did in order to check if the jitter improves over time. If it stays bad you might be able to contact your ISP to have them do a similar analysis. Unfortunately much of the time you will get no answer on that kind of requests.

A note on RAM, BF2 is a RAMhog. I used to run my rig with 1GB ram. I got myself one of those small LCD displays and installed LCDStudio to monitor my RAM usage whan playing. I was quite perplexed when I noticed that BF2(or POE2) ate all my RAM. THis means swapping for the system services that are seldom used and this has negative effects on game smoothness. I got another GB of ram(total of 2GB) and now my total ram utilization stops at about 1.3GB(leaving 700MB free). I have noticed improvements in gameplay.

Good luck

Why Ping is not Good for Network Measurements

__________________
--
VI VI VI - the number of the beast

Lekdevil.NL

No, the packet loss at the intermediate hops is nothing to be worried about, when there is no packet loss shown at the final destination (which there isn't). Nor is the intermediate hop jitter: it merely indicates the variation in ICMP TTL expired response messages, which are handled by the routers' CPUs (as opposed to the routed traffic, which is usually swiched in hardware). You can see that the jitter at the destination is actually quite low. Translation: the graph looks okay.

However, the "AOL" bit is a tad worrisome. So is the "download speeds going down to 10 KBps". This would suggest you're on a shared-bandwidth cable connection, where the capacity available to you is dependent on what others in your neighbourhood are doing. This would badly impact the quality of your BF2 connection. I'd suggest letting PingPlotter run during peak hours and when you're actually connected to the server. Then see if there's a correlation between the connection problems in-game and the graph (either high latency or visible last-hop packet loss). Post the graph here if you like.

HTH.

RedTalon

ok I am having this same exact problem...and I am running a dual channeled gig of ram...and back before I reinstalled BF2 the game ran fine. so I know it is not a ram problem.

The ping I usually show on servers is like 40. But then it will jump up to 900 and give connection error....and alll sorts of laggyness.

I remember having similar problems to this like a year back when the game first came out...it was similar to this but not nearly as bad at all.