Lag while in Wirble

[RotBaron]

I searched forum for suggestions here, but didn't find what I'm looking for.

For the most part I don't experience much to complain about regarding lag in the game. That is up until I'm in a Wirblewind and zoom in on the nme. I don't always get lag in this situation, but it happens often enough to be frustrating...It does seem to occur more often when the amount of nme's/friendlies increases. 

Suggestions please.

TIA,
Rot

[The Fugitive]

don't zoom in so much?   

The more guys around you the computer power you need to run it. If you have all your "eye candy" turned up you might just be on the edge of pushing it too hard, and when you get a lot of guys with the extra detail of the zoom it tips you over the edge.

Turning down some of the eye candy a bit might solve the problem for you. Post your computers specs and in game settings for a more definite answer on whether or not your pushing your computer to hard.

[RotBaron]

My system:

AMD Phenom II X4 830 Processor 2.80 GHz
6.0 GB Ram (5.75 GB usable)
64-bit

Graphics card:

ATI Radeon 3000
Tot available graphics memory = 2943MB



As far as my eye candy, I think I have an idea what you mean, but could you be more specific.

Thanks,
Rot


P.S. I should also note, I turn off all programs that aren't essential to keeping my computer running. This also includes the catalyst control program that I believe is associated with the graphics card. Sometimes I get lag in the wirble, sometimes I don't, so I'm skeptical it has much to do with that. Catalyst Control Center = MOM.exe and CCC.exe

[OOZ662]

Though it has nothing to do with zoom, a number of players (including myself) experience lag upon firing the Wirble due to the sudden looping of four copies of the 20mm firing sound, which often overlap each other and cause a mess for the sound card; this used to happen with some aircraft in the early stages of Aces High II as well. Having a lot of objects producing sound nearby would exacerbate the issue. You can try the usual sound-related fix of reducing your sound acceleration to 3/4, but if that doesn't work I haven't found a fix due to preferring the Ostwind anyway.

[texasfighter]

So how do you reduce your sound acceleration to 3/4s?

You can try the usual sound-related fix of reducing your sound acceleration to 3/4, but if that doesn't work I haven't found a fix due to preferring the Ostwind anyway.

[morfiend]

So how do you reduce your sound acceleration to 3/4s?

  You cant do that in vista or win7,they handle sound differently from how XP did.



   

[Babalonian]

Your settup looks to be capable, anything running in your background?  Try reducing your visual settings.  My old computer could barely handle the wirblewind with moderately sized furballs flying above.  My new rig has no problem.

[RotBaron]

It only happens when I fire and zoomed in. I see the point relating it to sound and not actually graphics. I'll post up my settings, however being fairly new to the game I have not changed a lot of default settings, some yes and I don't remember everything I played with in the beginning. 

TIA,

Rot

[OOZ662]

The only thing you can adjust in terms of sound output settings from Aces High is the volume. If it really is the issue you're experiencing, the one thing I can think of to try is using a shorter or dummy sound for the 20mms and hope that it bogs the sound card down less.

[RotBaron]

Also, it only happens when other friendlies are involved. I don't think I can recall an instance where this happens when there are anything less than 3+ friendlies around. Sound still the issue?

I'll keep track from now on, but I don't believe I ever encounter this lag when I'm mono y mono.

[Owlblink]

Also, it only happens when other friendlies are involved. I don't think I can recall an instance where this happens when there are anything less than 3+ friendlies around. Sound still the issue?

I'll keep track from now on, but I don't believe I ever encounter this lag when I'm mono y mono.

Do a search in the tech section of the BB and see if anything comes up. It still could be a sound issue, but you can try a few experiments. First, go into the Aces High options sound tab and click on advanced. Go through the lists of sounds and see if there is one for ground vehicle 20mms or something that would suggest it would work for the wirble. Turn that sound all the way off and go out and fire the guns around a bunch of friendliest and see if the lag still happens. Next, try turning barrel flashes off or the tracers, maybe all those gun effects in one area may be causing the problem.

Are the friendliest near by other ground vehicles or does that include planes? Do you hear a lot of vehicle engines running, those could also be a contribution with too many sounds fighting for processing power.

[RotBaron]

Sorry for the slow reply and thanks for the responses. I'll try all of these suggestions out and see what I come up with.

Rot

[RotBaron]

I looked in the advanced sound settings and did not find anything specific to the 4 20's of the wirb.

Also in a large furball to take a V-base, I encountered this same lag in a fighter when over the base and in zoom. Haven't noticed that before now in similar situations when in a fighter. Starting to think this isn't limited to the wirb necessarily, but maybe processor power in specific situations.

However, I'm noticing the lag more frequently in the wirb, even in engagements that involve as little as 3 enemies and 3 friendlies.

[The Fugitive]

Post the first third of your dxdiag here. The whole thing won't fit in a single post nor is it all needed. It looks like a resource issue. As you add more enemies, friendlys or sounds your computer is stumbling to keep up.

[RotBaron]

Post the first third of your dxdiag here. The whole thing won't fit in a single post nor is it all needed. It looks like a resource issue. As you add more enemies, friendlys or sounds your computer is stumbling to keep up.

Approximately the first 1/3 of the txt file:

perating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.120830-0334)
           Language: English (Regional Setting: English)
System Manufacturer: Hewlett-Packard
       System Model: p6537c
               BIOS: BIOS Date: 04/22/10 21:35:46 Ver: 6.04
          Processor: AMD Phenom(tm) II X4 830 Processor (4 CPUs), ~2.8GHz
             Memory: 6144MB RAM
Available OS Memory: 5888MB RAM
          Page File: 1642MB used, 10130MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: 144 DPI (150 percent)
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Enabled
     DxDiag Version: 6.01.7600.16385 32bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
          Input Tab: No problems found.

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

---------------
Display Devices
---------------
          Card name: ATI Radeon 3000 Graphics
       Manufacturer: ATI Technologies Inc.
          Chip type: ATI display adapter (0x9616)
           DAC type: Internal DAC(400MHz)
         Device Key: Enum\PCI\VEN_1002&DEV_9616&SUBSYS_2AA9103C&REV_00
     Display Memory: 2940 MB
   Dedicated Memory: 252 MB
      Shared Memory: 2687 MB
       Current Mode: 1920 x 1080 (32 bit) (59Hz)
       Monitor Name: HP 2310 Series Wide LCD Monitor
      Monitor Model: HP 2310
         Monitor Id: HWP288E
        Native Mode: 1920 x 1080(p) (60.000Hz)
        Output Type: DVI
        Driver Name: aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atiumdag,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.0024 (English)
     Driver Version: 8.733.0.0
        DDI Version: 10
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 5/12/2010 02:19:40, 584704 bytes
        WHQL Logo'd: Yes
    WHQL Date Stamp:
  Device Identifier: {D7B71EE2-D556-11CF-9473-A30ABEC2C535}
          Vendor ID: 0x1002
          Device ID: 0x9616
          SubSys ID: 0x2AA9103C
        Revision ID: 0x0000
 Driver Strong Name: oem61.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_RS780:8.733.0.0:pci\ven_1002&dev_9616&subsys_2aa9103c
     Rank Of Driver: 00E60001

Is that enough of dxdiag?

Thanks,
Rot