Crazy warping problem

[stockli]

I am running on a cable modem and have never had a warping issue until I reinstalled Windows XP on my system.

I basicly wiped my drive and reinstalled it.

I have gone and disabled the things Skuzzy said I could and am still having this issue.

I am super frustrated at this point! HELP! lol

[NCLawman]

Just a question.....

You essentially wiped the harddrive clean, and reinstalled the OS (Windows XP) if I read your post correctly.  Did you then reinstall all your drivers with the latest versions?  Also, you may want to consider that when you reinstalled XP, you might HAVE put in all the latest drivers and updated drivers that worked better with older driver versions (sometimes the case with certain video cards).   The fix to your problem MIGHT be a roll back to earlier drivers... or it could be an update to current drivers all depending on your video card.

[StarOfAfrica2]

Without more information I'm just making a stab in the dark here, but if this isnt caused by net issues, then more than likely there is just too much going on for the CPU and/or video card to handle.  First thing I'd do is run a route trace or a ping plot to the HTC server and make sure its not net related.  Once you clear that out of the way, I'd start turning down settings ingame and on my video card until I reach minimum eye candy settings all the way around and see if the problem dissapears.  Then you can start adding back in a little bit at a time until you have reached a balance you can live with.

[stockli]

how do you run a ping plot or route trace?

NC i installed the drivers from the proper site and am running the same upated drivers i used to.  

LOL, now see why this is so aggrevating? Lol

[TinmanX]

Originally posted by stockli
how do you run a ping plot or route trace?

Goto your DOS command prompt; Start/All Programs/Accessories/Command Prompt.

Type TELNET  206.16.60.39 and press ENTER

[Schatzi]

Or get Ping Plotter  and install it. The free version will give you test output as well as graphical (pics).

[stockli]

ran ping plotter what is the test supposed to look like and how do I post it for yall to look at it?

Im just supposed to put the ip address liseted in tnmanx post right?

[Schatzi]

From Tech Support stickies:

First, the server IP addresses, to be used for traces/ping plots.

Main Arena Server Address: 206.16.60.39
All other arenas: 206.16.60.38

Trace both IPs in ping plotter (Copy paste them into the "Adress to trace" field). Set the "Samples to include" to at least ten and let it run for a bit. Click on Edit - Copy as text and then CTRL_V to paste it into your post.

If you save as Image, you need to paste it into a graphic editing software (like photoshop or paint), save it as a file, host it on the web somewhere and post the link here.



What youre looking for is stable connect (ie no big differences between the single traces (best seen in the graphic to the right - the black bars are variance). Also, you do not want to see packet loss (PL, on the left) - some hops will always show 100% PL though, thats normal.

[StarOfAfrica2]

You put the IP address in you want to run the ping to, then look in the column that says Packet Loss and see if anything is listed.  Then look at your numbers on the far right, and the graph.  The smaller the number the better, thats your Ping.  Ping is the speed at which a packet of information can get a response from each point along your route to HTC's server.  If anyone on the route has a problem with their equipment causing large ping times or lost packets,  that could be the source of your trouble.  Send Skuzzy a copy of it and maybe he can help notify the company responsible and get it fixed.  Dont hold your breath.  Most companies fix problems that pop up fairly quickly, but some can linger for awhile.

*edit

I think the command TM wanted to pass on to you is "tracert", not "telnet".  TELNET is a protocol for logging in to another computer, not tracing a route to another computer.

[Auger]

Hi Stockli,

From my experience, warps are caused either by net suckage or CPU overload.  You can check out network problems with the net monitor in AH2.  It's a button on the screen where you select an arena.  Fire it up and go get a drink, walk the dog, whatever.  When you get back, look at the plot and the packets sent/lost.  The plot should be fairly flat, and the packet loss should be zero.  A few packets lost are tolerable, but it's a sign of some network problems.  If the plot has lots of peaks and valleys that's also a sign of network issues.

To check on CPU overload, click Start/Run, type in 'taskmgr' and click OK.  Select the Performance tab.  With no applications running the CPU Usage History graph should be pretty flat and under 5%.  The physical memory available should be at least half of your total memory, but more is better.

Now click on the Processes tab.  Depending on how much is running in the tray and other background services, there should be less than 30 or so processes running.  If there is more, you might want to see if you can get by with less junk running.  Turn off Google Earth, AIM and other chat programs, and any other widgets not essential to keeping Windows up.  

If you don't have a CPU column, click on View/Select Columns... and check CPU Usage.  Click on the CPU column heading twice to sort by most CPU Usage.  System Idle Process should be using about 99% of your CPU.  If anytihing else is constantly using CPU percentages of more than 2 you should see about getting rid of it.

This is not for the faint of heart, or for those with no hardware firewall, but killing real-time antivirus can also help.  Real-time antivrus scans network traffic and files as they are accessed and can really spike the CPU.  If you have a hardware firewall, turn off antivirus software before you play AH.

Standard disclaimer: YMMV, IANAL, IMHO, TANSTAAFL

[stockli]

it seems i dont have a ping problem 0 packets lost after 300

i dont know what to do

[stockli]

I know its a laptop, but i never had any problem running the game before




------------------
System Information
------------------
Time of this report: 8/12/2006, 16:12:51
       Machine name: IMPG-108965DFFD
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_rtm.040803-2158)
           Language: English (Regional Setting: English)
System Manufacturer: FUJITSU
       System Model: LifeBook S Series
               BIOS: Phoenix FirstBIOS(tm) Notebook Pro Version 2.0    
          Processor: Intel(R) Pentium(R) M processor 1600MHz
             Memory: 502MB RAM
          Page File: 293MB used, 936MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.2180 32bit Unicode

------------
DxDiag Notes
------------
  DirectX Files Tab: No problems found.
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
          Music Tab: No problems found.
          Input Tab: No problems found.
        Network Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (n/a)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
        Card name: Intel(R) 82852/82855 GM/GME Graphics Controller
     Manufacturer: Intel Corporation
        Chip type: Intel(R) 82852/82855 Graphics Controller
         DAC type: Internal
       Device Key: Enum\PCI\VEN_8086&DEV_3582&SUBSYS_120E10CF&REV_02
   Display Memory: 64.0 MB
     Current Mode: 1024 x 768 (32 bit) (60Hz)
          Monitor: Plug and Play Monitor
  Monitor Max Res: 1600,1200
      Driver Name: ialmrnt5.dll
   Driver Version: 6.13.0001.3460 (English)
      DDI Version: 8
Driver Attributes: Final Retail
 Driver Date/Size: 4/15/2003 12:36:48, 33792 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: ialmnt5.sys
    Mini VDD Date: 4/15/2003 12:36:48, 89371 bytes
Device Identifier: {D7B78E66-76C2-11CF-FB7E-0F32A0C2CB35}
        Vendor ID: 0x8086
        Device ID: 0x3582
        SubSys ID: 0x120E10CF
      Revision ID: 0x0002
      Revision ID: 0x0002
      Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D
 Deinterlace Caps: {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
         Registry: OK
     DDraw Status: Enabled
       D3D Status: Enabled
       AGP Status: Enabled
DDraw Test Result: Not run
 D3D7 Test Result: Not run
 D3D8 Test Result: Not run
 D3D9 Test Result: Not run

-------------
Sound Devices
-------------
            Description: SigmaTel Audio
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_8086&DEV_24C5&SUBSYS_11C310CF&REV_03
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: STAC97.sys
         Driver Version: 5.10.3743.0000 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 1/16/2003 21:01:52, 202480 bytes
            Other Files:
        Driver Provider: SigmaTel
         HW Accel Level: Basic
              Cap Flags: 0xB5B
    Min/Max Sample Rate: 32000, 48000
Static/Strm HW Mix Bufs: 0, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
               Registry: OK
      Sound Test Result: Not run

---------------------
Sound Capture Devices
---------------------
            Description: SigmaTel Audio
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: STAC97.sys
         Driver Version: 5.10.3743.0000 (English)
      Driver Attributes: Final Retail
          Date and Size: 1/16/2003 21:01:52, 202480 bytes
              Cap Flags: 0x41
           Format Flags: 0xCC0

-----------

[StarOfAfrica2]

Main problem is that your graphics controller is not the best for 3D applications, and also you have almost no video memory.  Turn all of your ingame sliders to the absolute far right, set your max texture size no higher than 256, and preload NOTHING.

[Schatzi]

Like SOA said... your pretty low end with memory and graphic device. The last patch just might have broken your neck.

It also might be that you installed a driver with the new OS that slows you down a bit (the well known straw). Im no expert on that, maybe Skuzzy or someone else knows better.


I dont think its your connect...

[StarOfAfrica2]

Nah, his connection is fine.  He's just overworking the system.  More than likely when everything was reinstalled, whatever the "default" is on things is too much when running AH.  There's barely enough memory on that system to run Windows XP without stutters, let alone run games.  Not saying it WONT work, becuase obviously it has.  But its never going to work well.  The more things are updated and upgraded, the more the minimum requirements will go up too, and the less likely a computer like this will continue to run AH.  Just a fact of the modern world.