Patch 2 Frame Rate issues.

[The Fugitive]

yep becuase last pacth it was fine. over working yep. one pacth makes a machine useless.

Just the ground clutter can have a huge impact on how your computer handles the game. And yes, one update is all it takes to push you over the edge. Before an update it's working fine, after your pushing it too hard and you get stutters. You turn down some of the eye candy and the stutter "may" go away.

Of course, you know everything and us "old guys" couldn't possible know what we are talking about. On the other hand, my computer runs the game fine. Good Luck!

[OOZ662]

I'm thinking the issue is related to ground objects not included in the clutter system, specifically near airfields (perhaps even more specifically near towns). The CTD issue USRanger was having while building his map may be related. I say this because the only times I have out-of-VRAM errors or heavy stuttering occur when I'm on final approach to land or I enter the bomb sight on approach to bomb an airfield. The issue has been mostly fixed by halving my ground draw distance slider.

I've run with 80% sliders, 512 textures, the middle setting for antialiasing, other players' skins and effects enabled, and detailed water and terrain enabled since the detailed options were added. No shadows, no bump maps. With this last patch, I suffered constant out-of-VRAM errors and turned my detailed terr/water off. The problem stayed away for a while, but still happened once, at which point I lowered my sliders to about 40%, turned off AA, and disabled other players' skins. I was then able to turn the detailed terr/water options back on. Since, I have very rare stutters and no out-of-VRAM issues. I haven't tried to see if I can re-enable others' skins.

DXDiag here. Yes, peanut gallery, it's a dinosaur. I can't afford a whole new machine. And, as stated, it worked fine before.

[wil3ur]

Last night I had my video memory go into a huge spike again.  I'd played the same map the night before with no problems, but had stuck to the edges and coastline.  Once I got over the middle of the map with the 4-6k hills it started up again.  I've had the same problems in areas with really fjordy coastlines with advanced water turned on.  The only thing I can think is that it's loading undisplayed layers, and when you have a lot of hills, or a lot of changing water terrain, there's a lot of excess graphics being loaded that aren't actually displayed.  *shrug*

[Chalenge]

I did the same as Wil3ur after Hitech suggested it. Changing views rapidly will result in seeing sticky views and frame freezes.

[BrockS]

I have the same issues as Wil3er. In addition I have been getting spikes and out of VRAM crashes since the last patch. My system ran pretty smoothly prior to patch 2. I use detailed terrain, detailed water and bump mapping and all other boxes unchecked (shadow texture size 512). My distance sliders are set around halfway. After the patch I added bump mapping on my plane and ground clutter off when airbourne. I get micro stutters frequently and out of VRAM usually around the 30 to 45 minute mark of flying. I also get a crash about every second time I window out of AH then back in.

Additionally I run a very "clean" system with most background services and processes disabled, even explorer.exe when I will only be gaming. Aces is even on it's own HDD. I have really never had the graphics performance I thought I should have for my GPU and RAM but I attribute that to my proccessor.

Anyway, I digress. Bottom line, same issues as Wil3er here.

-----------------
System Information
------------------
Time of this report: 2/9/2012, 10:20:21
       Machine name: ARTVANDALAY-PC
   Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
           Language: English (Regional Setting: English)
System Manufacturer: Gateway
       System Model: DX4200-09
               BIOS: Default System BIOS
          Processor: AMD Phenom(tm) 9150e Quad-Core Processor (4 CPUs), ~1.8GHz
             Memory: 8192MB RAM
Available OS Memory: 7936MB RAM
          Page File: 2897MB used, 15035MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: 120 DPI (125 percent)
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
      Display Tab 2: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: 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 HD 5570
       Manufacturer: Advanced Micro Devices, Inc.
          Chip type: ATI display adapter (0x68D9)
           DAC type: Internal DAC(400MHz)
         Device Key: Enum\PCI\VEN_1002&DEV_68D9&SUBSYS_30501682&REV_00
     Display Memory: 626 MB
   Dedicated Memory: 1010 MB
      Shared Memory: 3711 MB
       Current Mode: 1920 x 1080 (32 bit) (30Hz)
       Monitor Name: Generic PnP Monitor
      Monitor Model: SONY TV
         Monitor Id: SNY01F8
        Native Mode: 1920 x 1080(i) (60.053Hz)
        Output Type: HDMI
        Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1114 (English)
     Driver Version: 8.930.0.0
        DDI Version: 11
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 12/5/2011 22:16:00, 933888 bytes
        WHQL Logo'd: Yes
    WHQL Date Stamp:
  Device Identifier: {D7B71EE2-2B99-11CF-6871-5A10BEC2C535}
          Vendor ID: 0x1002
          Device ID: 0x68D9
          SubSys ID: 0x30501682
        Revision ID: 0x0000
 Driver Strong Name: oem20.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Evergreen:8.930.0.0:pci\ven_1002&dev_68d9
     Rank Of Driver: 00E62001
        Video Accel: ModeMPEG2_A ModeMPEG2_C

[YamaRaja]

I found a big difference in frame rates with different ATI drivers.
I tried 11.8, 11.9, 11.10, 11.12, 12.1 and 12.2 beta preview.

In my system 11.8 and 11.9 had fairly poor performance.
12.1 and 12.2 both had stutters (a known driver problem on some systems and not AH related)

11.10 had decent performance.

11.12 worked the best.

I7 2600K, HD6950 2gb crossfire

[Kazan_HB]

before last patch, was all ok. Now i have 14 frame rate
 


System Information
------------------
Time of this report: 2/13/2012, 01:18:26
       Machine name: TOMASZ-PC
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
           Language: German (Regional Setting: German)
System Manufacturer: System manufacturer
       System Model: System Product Name
               BIOS: BIOS Date: 01/26/11 18:07:46 Ver: 08.00.14
          Processor: AMD Phenom(tm) II X6 1055T Processor (6 CPUs), ~2.8GHz
             Memory: 8192MB RAM
Available OS Memory: 8192MB RAM
          Page File: 2230MB used, 14149MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7601.17514 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 HD 5800 Series
       Manufacturer: Advanced Micro Devices, Inc.
          Chip type: ATI display adapter (0x689E)
           DAC type: Internal DAC(400MHz)
         Device Key: Enum\PCI\VEN_1002&DEV_689E&SUBSYS_30701682&REV_00
     Display Memory: 754 MB
   Dedicated Memory: 1010 MB
      Shared Memory: 3839 MB
       Current Mode: 1680 x 1050 (32 bit) (60Hz)
       Monitor Name: PnP-Monitor (Standard)
      Monitor Model: VW225
         Monitor Id: ACI22A0
        Native Mode: 1680 x 1050(p) (59.954Hz)
        Output Type: DVI
        Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1114 (English)
     Driver Version: 8.930.0.0
        DDI Version: 11
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 12/6/2011 04:16:00, 933888 bytes
        WHQL Logo'd: Yes
    WHQL Date Stamp:
  Device Identifier: {D7B71EE2-2BDE-11CF-6871-7A10BEC2C535}
          Vendor ID: 0x1002
          Device ID: 0x689E
          SubSys ID: 0x30701682
        Revision ID: 0x0000
 Driver Strong Name: oem17.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Evergreen:8.930.0.0:pci\ven_1002&dev_689e
     Rank Of Driver: 00E62001
        Video Accel: ModeMPEG2_A ModeMPEG2_C
   Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) 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
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {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
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                     {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) 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
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
       D3D9 Overlay: Not Supported
            DXVA-HD: Not Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled

[stickpig]

Same here...Stable 75 fps for years, update after update never a problem. Got online to check out the latest and WOW .... down to 22 23 fps. Same setting I always use never change a thing in the vid settings and now its like...  really?

How do I post the dxDiag information?

[stickpig]

On a side note ...even if I disable shadows and bump mapping and turn down textures to 512 from 1024 it doesn't really seem to affect things either way. Not sure what else to try.

It took a long time to configure setting on my vid card to get it just perfect. Maybe I'll start changing things one at a time and see what happens.

Really big change between the last two patches I really dont think its my system.

[The Fugitive]

Same here...Stable 75 fps for years, update after update never a problem. Got online to check out the latest and WOW .... down to 22 23 fps. Same setting I always use never change a thing in the vid settings and now its like...  really?

How do I post the dxDiag information?

Run the dxdiag. When it is done, on the bottom there is a button to save the info as a text file. Save it someplace you can find it and close out the dxdiag window. Double click the text file you just saved and open it with "notepad". Copy and paste the top third, up to and including "sound devices" here on the message board.

...or you could email the whole thing to Skuzzy.

[stickpig]

Where do I run it from? Seriously I've never done it before, so I'm not sure how or where.

Any help would be appreciated

Thanks

[OOZ662]

How do I post the dxDiag information?

Run the dxdiag.

My...how detailed.
Instructions on how to generate a DxDiag report can be found in the sticky at the top of this forum.

[The Fugitive]

He asked how to "post" it, not how to run it, so ya I think it was more than detailed enough for what he asked.   

[doc1kelley]

My...how detailed.
Instructions on how to generate a DxDiag report can be found in the sticky at the top of this forum.

Take a chill pill Dude!  Fugi was just trying to be helpful.  You should buy a clue rake and try and help out here.


All the Best...

   Jay

[OOZ662]

Take a chill pill Dude!  Fugi was just trying to be helpful.  You should buy a clue rake and try and help out here.

Telling someone who's calm and being helpful to "take a chill pill" while directly insulting them (especially when one hasn't even posted in the thread yet) is slightly contradictory, for future reference.

Since the trolling has begun, it appears this thread has neared the end of its useful lifetime. Unfortunate, too, since there still doesn't seem to be a consensus on what's causing the problem, other than something having to do with the ground.