Why will HTC never back out of a release?

[Crash Orange]

Why will HTC never back out of a release when has enough problems to make the game unplayable to many? Revert to 2.18, then fix all the known bugs in 2.19 without everyone having massive problems while they work on it, then release 2.19 again when it's ready for prime time?

Apart from the disabled vox, my mouse cursor freezes and stutters - I used to be able to stop that by clicking on "Video Options" right after opening the game, but that no longer works - everything takes forever to load, I still get stutters and I haven't been able to stay online long enough to see if they stop after a while because I keep getting discoed. PingPlotter gives me a round trip of 81 ms and my CPU usage for everything else stays below 2%.

I know these things can't be fixed in an instant, and I'm sure they're working very hard to fix them; all I ask is to be able to play a workable version in the meantime.

DXDIAG:

------------------
System Information
------------------
Time of this report: 5/13/2010, 00:41:44
       Machine name: DOKTORAVALANCHE
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.100216-1514)
           Language: English (Regional Setting: English)
System Manufacturer: HP Pavilion 061
       System Model: EX265AA-ABA a1510n
               BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: AMD Athlon(tm) 64 Processor 3800+,  MMX,  3DNow, ~2.4GHz
             Memory: 2046MB RAM
          Page File: 419MB used, 2912MB available
        Windows Dir: C:\WINDOWS
    DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
     DxDiag Version: 5.03.2600.5512 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: NVIDIA GeForce 9500 GT
     Manufacturer: NVIDIA
        Chip type: GeForce 9500 GT
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0640&SUBSYS_C9583842&REV_A1
   Display Memory: 1024.0 MB
     Current Mode: 1920 x 1080 (32 bit) (60Hz)
          Monitor: HP w2338h Wide LCD Monitor
  Monitor Max Res: 1920,1080
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0011.8120 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 12/25/2008 12:08:00, 6168960 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 12/25/2008 12:08:00, 6301344 bytes
Device Identifier: {D7B71E3E-4500-11CF-4A44-53E900C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0640
        SubSys ID: 0xC9583842
      Revision ID: 0x00A1
      Revision ID: 0x00A1
      Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
 Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {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
                   {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
                   {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {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
         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: Realtek HD Audio rear output
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_103C2A3E&REV_1000
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RtkHDAud.sys
         Driver Version: 5.10.0000.5229 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 3/8/2006 09:27:12, 4246016 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Standard
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 8000, 192000
Static/Strm HW Mix Bufs: 33, 32
 Static/Strm HW 3D Bufs: 33, 32
              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: Line in/Mic in
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: RtkHDAud.sys
         Driver Version: 5.10.0000.5229 (English)
      Driver Attributes: Final Retail
          Date and Size: 3/8/2006 09:27:12, 4246016 bytes
              Cap Flags: 0x41
           Format Flags: 0xFFF


-------------------
DirectInput Devices
-------------------
      Device Name: Mouse
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Keyboard
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Saitek X52 Flight Controller
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x075C
        FF Driver: n/a

Poll w/ Interrupt: No
         Registry: OK

 8/17/2001 14:48:00, 12160 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ Enhanced Mulmedia PS/2 Keyboard
| Matching Device ID: acpi\pnp0303
| Upper Filters: PS2
| Service: i8042prt
| Driver: i8042prt.sys, 4/13/2008 15:18:00, 52480 bytes
| Driver: kbdclass.sys, 4/13/2008 14:39:47, 24576 bytes
| Driver: PS2.sys, 12/12/2005 17:27:00, 19072 bytes
|
+ HID Keyboard Device
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/13/2008 14:39:48, 14592 bytes
| Driver: kbdclass.sys, 4/13/2008 14:39:47, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 4/13/2008 20:13:20, 40840 bytes
| Driver: kbdclass.sys, 4/13/2008 14:39:47, 24576 bytes
|
+ HID-compliant mouse
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 4/13/2008 14:39:47, 23040 bytes
| Driver: mouhid.sys, 8/17/2001 14:48:00, 12160 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 4/13/2008 20:13:20, 40840 bytes
| Driver: mouclass.sys, 4/13/2008 14:39:47, 23040 bytes


(the rest deleted because it exceeds max post length)

[Dr_Death8]

Because not everybody has those issues.  Yes, VOX is disabled and if you read the update information page you would have went into the game knowing about the issues, as they are changing the sound set-up. Personally I thought the sounds were outstanding. I could pinpoint nme GVs by sound.
Although I am not a computer wiz, I would try updating your drivers (12/25/2008 ) and maybe different resolution (Current Mode: 1920 x 1080).

[TequilaChaser]

Page File: 419MB used, 2912MB available

also for Windows XP SP3 your page file used is showing you have prob around 40+ processes running........

a good clean WinXP SP3 install will be around 24 processes max runing at idle....... a more thorough cleaned and tuned winXP system would be around 20 processes down to 18 processes running at idle......

you might want to tune-up your Windows XP OS, a lil bit ... them processes running in the background needlessly can be causing some of your problems possibly.......

hope this helps

[Superfly]

You can't put the genie back in the bottle.

[Tigger29]

Or close Pandora's box!  Maybe cut a hole in it, but that's a different subject altogether...

[gyrene81]

Your paging file is way too big (as TequilaChaser pointed out)...and if you're playing with that big of a paging file you're going to have problems.

Your video card driver is slightly old and your video card is not capable of running the game smoothly at native resolution...I had one, same problems...best results were 1440x900 or 1280x768, 256 textures, detailed terrain, bump map terrain, sliders set for performance not detail, and that is it. I'd be interested in seeing what settings you have in your Nvidia control panel as well...probably not optimal.

Your sound card driver is pretty old too...that will cause some of the issues you are seeing.

[guncrasher]

also for Windows XP SP3 your page file used is showing you have prob around 40+ processes running........

a good clean WinXP SP3 install will be around 24 processes max runing at idle....... a more thorough cleaned and tuned winXP system would be around 20 processes down to 18 processes running at idle......

you might want to tune-up your Windows XP OS, a lil bit ... them processes running in the background needlessly can be causing some of your problems possibly.......

hope this helps

I had a computer similar to his, had no problems running game with 40 processes and a bigger page file.  18-20 processes is not that easy to do unless you really have a detailed knowledge of windows and programs you are running.  most of us mortals are stuck with the 35-45 processes and if we try to get it any lower it will probably screw up our systems so bad we wont be able to reboot.

his main concerned was that he was playing ok 2 days ago, but he's having problems now.  my answer to him will be to have patience.  ah will have most of the bugs worked out within a couple of days.  also be aware that not everybody is having as big as problem as you.  most of us are playing the game "fine" and consider some of the bugs some of those annoying things that happen everyday, like ho'ers and rammers .  But i have no doubts that ah is working hard and we will be back to our regular whining in now time .




semp

[bustr]

Get a copy of Game Booster.

It's free and will shut down all unneeded processes in XP before you launch the game. It has a lookup file of XP processes that can be shut down by default and still allow you to run an Internet based game. It has a secondary window that shows you running programs that can be shut down or allowed to keep running. When you exit the game, Game Booster will start everything back up for you. Game Booster is not an OS performance booster application. It just takes the guess work out of shutting down services, processes and applications not needed for running your game. Then lets you turn them back on.

I have heard players say the Game Booster application causes problems with their OS and interfers with game performance. Others say it just shuts down unneccessary services and processes. I've never had any performance problems with it. As for the first group of players with problems, I'm not sure what the overall state of their OS and machines are to begin with. The observations about your video drivers are correct. Your sound drivers are old also. Onboard audio chipsets cause performance hits to the game. Try borrowing a USB head set with the audio chip in the USB plug. Disable your onboard audio in the bios then see if the USB head set helps your performance.

I run XP sp3 with only 18 processes at idle.

[Ghosth]

As today's patch shows, they will if they have to, but only if they truly have to.

Genies are just not that easy to get back in the bottle.

[thndregg]

You can't put the genie back in the bottle.

That's what she says.

[Crash Orange]

Thanks for all the advice.  

I'll start with the drivers and then try Game Booster. Guncrasher is right, I'm at the point where I don't know which additional processes I could shut down without causing problems. And I was running fine at that resolution before with frame rates running around 55-60, but I'll try lowering it if I still have problems.

[guncrasher]

try this website. just remember every process you terminate can affect something that you normally would use, but wont necessarily need.  best thing i like about the website is that it offers what should be the standard settings in case something doesnt work and you need to go back.  I used the tweaked conf and had it around 30-35 processes. just be aware that things like auto updated wont work or your help search.

semp

http://www.blackviper.com/

[Krusty]

The page file itself isn't going to be an issue. In fact that's a perfectly reasonable sized page file. Keep in mind he's ONLY using 419MB of it. Hell WinXP is happy to use up more with less impact.

He could thin out some processes, I agree. Overall, his system may be a bit on the low side to be running 40+ processes. I run comfortably around 30, but that's because I indulge in a few that I want running for various programs. Anything around 28 is good.


As for why your system is having the issues it does, I don't know for sure. I do note, however, that they mentioned some mouse fixes in the 2.19 patch 1 readme. Download that and see if your problems have been fixed or not.

[The Fugitive]

That's the nice thing about Alacrity. You can set it to turn off anything you want and if you made a mistake and turn the wrong thing off all you do is hard boot your computer and it will restart your computer as it was BEFORE you made any changes. It doesn't make any permanent changes. Use vipers site with Alacrity and you should be able to get it down to 20 ith ease..... Even for a NON geek

[Skuzzy]

To answer the original question.  There is always an inherent risk when moving forward.  However, it is better than the alternative, which is to stagnate and die.

No matter how much we can do, internally, to test a new release, we cannot possibly hope to match all the hardware and software configurations of thousands of other computer systems.