I've been having some warping issues...

[Fianna]

...so I'm posting the pingplot thing.

[Max]

You're hosed from the gitgo. Call Comcast and bark your way up a tier or two until you get an upper level tech agent.

[Skuzzy]

This is the same routing problem that has been going on now for weeks.

Look at that mess in that ping plot.

From Fresno to
Sacremento to
Oakland to
Sacremento to
San Jose to
Chicago to
San Francisco to
Los Angeles to
Dallas

Like Max said, you need to get a hold of Comcast, and get passed the first level of support.  Once you get to Tier two support, point them at this thread.  If they cannot see what the problem is, get another ISP.

This problem has been ongoing for over a month now.  One day it works fine, the next day it is exactly what you see Fianna.  Almost as though someone, somewhere has stored a bad backup of the BGP tables and they keep reloading that bad copy.  This is reaching levels of incompetence I cannot comprehend.

[Fianna]

Ok, so, I did like you said to do, Skuzzy, and switched my ISP (from comcast to att dsl).

However, I'm still warping all over the place.



Since this is obviously not an ISP issue, do you still want me to post the pingplot?

[Skuzzy]

Warps can be caused by many things.  A Pingplot is always the first place to start, but if it does not show a problem, then we move to resource issues with the computer, which requires a DXDIAG output.

I'd like to see that Pingplot, regardless.

[Fianna]

[Skuzzy]

I traced back and it looks good going back, at this particular time.

traceroute 151.164.186.203
traceroute to 151.164.186.203 (151.164.186.203), 30 hops max, 40 byte packets
 1  206.16.60.33 (206.16.60.33)  0.687 ms  0.546 ms  0.470 ms
 2  mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205)  0.301 ms  0.400 ms  0.266 ms
 3  gar26.dlstx.ip.att.net (12.122.254.29)  1.667 ms  1.086 ms  1.022 ms
 4  cr2.dlstx.ip.att.net (12.122.138.186)  1.699 ms  1.607 ms  1.227 ms
 5  gar6.dlstx.ip.att.net (12.122.138.29)  1.177 ms  1.295 ms  1.072 ms
 6  12.122.79.66 (12.122.79.66)  1.680 ms  1.517 ms  1.436 ms
 7  151.164.38.70 (151.164.38.70)  52.265 ms  52.541 ms  52.185 ms
 8  151.164.189.15 (151.164.189.15)  51.903 ms  51.899 ms  51.884 ms
 9  bras1-l0.frs2ca.sbcglobal.net (151.164.186.203)  53.781 ms  53.931 ms  54.097 ms

Just on hop counts alone, your connection looks a lot better.

What does the process list (task manager, Processes tab) of the computer look like?  Are you using a local wireless router?  Watching the CPU usage in the process list, what does it do?

How about a DXDIAG output?

[Fianna]

I traced back and it looks good going back, at this particular time.

traceroute 151.164.186.203
traceroute to 151.164.186.203 (151.164.186.203), 30 hops max, 40 byte packets
 1  206.16.60.33 (206.16.60.33)  0.687 ms  0.546 ms  0.470 ms
 2  mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205)  0.301 ms  0.400 ms  0.266 ms
 3  gar26.dlstx.ip.att.net (12.122.254.29)  1.667 ms  1.086 ms  1.022 ms
 4  cr2.dlstx.ip.att.net (12.122.138.186)  1.699 ms  1.607 ms  1.227 ms
 5  gar6.dlstx.ip.att.net (12.122.138.29)  1.177 ms  1.295 ms  1.072 ms
 6  12.122.79.66 (12.122.79.66)  1.680 ms  1.517 ms  1.436 ms
 7  151.164.38.70 (151.164.38.70)  52.265 ms  52.541 ms  52.185 ms
 8  151.164.189.15 (151.164.189.15)  51.903 ms  51.899 ms  51.884 ms
 9  bras1-l0.frs2ca.sbcglobal.net (151.164.186.203)  53.781 ms  53.931 ms  54.097 ms

Just on hop counts alone, your connection looks a lot better.

What does the process list (task manager, Processes tab) of the computer look like?  Are you using a local wireless router?  Watching the CPU usage in the process list, what does it do?

How about a DXDIAG output?

I use a wireless router. I get warps whether or not I'm connecting through the router, so the router can't be the problem. I'm not sure how I would describe the process list, other than it's a list of processes, but the total CPU usage hovers between 4 and 7%.

Here's what the in-game net status tab looks like, if it'll help.





I've emailed the DXDIAG.



Thanks.

[Skuzzy]

That net status variance says something is firing off in the background taking the CPU away from running the game.

[Fianna]

Is there any way I can pinpoint what is doing it?

[Skuzzy]

Look at the process list in Windows.  How many are running?  For Windows XP, a clean system will run between 19 and 21 processes.

Sort the list by process time and see what pops up.  Shutdown everything you can until the problem goes away.

Every computer is different.  Every computer has a different set of processes.

[Fianna]

Are there any that I absolutely shouldn't shut down?

[Skuzzy]

Sure there is.  Unfortunately, as every computer is different, I would not trust a list handed to you.

The safest way to do it, is to Google the name of each process when you are not sure what it is.

[Fianna]

I made it through 7 or 8 processes before I blue-screened myself. 

Looks like I'll be doing a lot of googling. 

[TwinBoom]

fianna read this page
Black Viper