For a start, CTDs most likely have little to do with your network connection. CTDs seem to be a bug possibly related to buff formations. Last week I managed to film a situation where something was causing many people to repeatedly CTD at a field that was under attack. Hopefully it will help HTC figure out the bug.
Ping times can be quite irrelevant at a certain level. Obviously a ping time in 1000's means things are bad. But as they get lower connection quality becomes the issue you have to look at.
What you are describing is most likely your ISP or something in the circuit between you and HTC dropping packets. Ahh you say I ran pingplotter and got no packet loss! But did you run pingplotter or your tracert with larger packet sizes? Most tracerts run with 128byte packets, and I can assure you AH furballs do not use 128byte packet sizes.
Trying running a trace with incremental sizes, 128 bytes, 512 bytes, 1024 bytes, 2048 bytes etc. Watch how your 'once virgin and perfect' network connection suddenly starts getting 50% packet loss ratios as the size creeps up.
What can you do? Not much on the internet side of things, but as far as AH goes try and avoid fights with loads of planes (ie 20-50's) or GVs or ships. These increase the trafficload to you and increase the likelyhood that some router along the way is going to discard your traffic.
What you are probably finding is a less crowded CT = smaller packets = less packet loss = better gameplay.
Lastly, Hazed, what has changed with AH in the last 2 years? Think back, how big were fights before the AW boatpeople started unloading?
Originally posted by hazed-
Vulcan thats nonsense mate. Ive been playing AH for over 2 years with no problems up until the latest patches.I have adsl and a very good connection but im still getting lost udp's and CTDs regularly.
also for me last night was so laggy that i switched to CT.
all the symptoms mentioned above went away in CT and as you know the ping times to CT are higher than the MA.It has nothing to do with poor connections per say, its the routers that seem to be at fault and MA routers last night SUCKED EGGS!