Extreme frame rate loss when wounded/loosing oil

[SirNuke]

Hey there,

My game runs a solid 60fps whatever the situation is but whenever I'm wounded or loosing oil I drop to a stable 30/40fps whatever is going on around me. Any idea why? My hypothesis is that my videocard's memory overloads but its still weird that it only happens when there is a texture on my cockpit. Thanks.

[SirNuke]

------------------
System Information
------------------
Time of this report: 7/11/2013, 23:28:10
       Machine name: XPOWA
   Operating System: Windows 7 Professionnel 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
           Language: French (Regional Setting: French)
System Manufacturer: MSI
       System Model: MS-7752
               BIOS: BIOS Date: 10/24/12 16:32:48 Ver: 04.06.05
          Processor: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (4 CPUs), ~3.4GHz
             Memory: 8192MB RAM
Available OS Memory: 8136MB RAM
          Page File: 2396MB used, 13873MB 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: AMD Radeon HD 6800 Series
       Manufacturer: Advanced Micro Devices, Inc.
          Chip type: AMD Radeon Graphics Processor (0x6738)
           DAC type: Internal DAC(400MHz)
         Device Key: Enum\PCI\VEN_1002&DEV_6738&SUBSYS_03C61043&REV_00
     Display Memory: 4095 MB
   Dedicated Memory: 1011 MB
      Shared Memory: 3084 MB
       Current Mode: 5904 x 1200 (32 bit) (60Hz)
       Monitor Name: Moniteur Plug-and-Play générique
      Monitor Model: PLE2607WS
         Monitor Id: IVM5608
        Native Mode: 1920 x 1200(p) (59.950Hz)
        Output Type: HDMI
       Monitor Name: Moniteur Plug-and-Play générique
      Monitor Model: SyncMaster
         Monitor Id: SAM01E7
        Native Mode: 1920 x 1200(p) (59.950Hz)
        Output Type: DVI
       Monitor Name: Moniteur Plug-and-Play générique
      Monitor Model: SyncMaster
         Monitor Id: SAM01E6
        Native Mode: 1920 x 1200(p) (59.950Hz)
        Output Type: Displayport External
        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.1191 (English)
     Driver Version: 12.104.0.0
        DDI Version: 11
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 3/29/2013 04:37:02, 1155264 bytes
        WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
  Device Identifier: {D7B71EE2-2478-11CF-5477-CC23BEC2C535}
          Vendor ID: 0x1002
          Device ID: 0x6738
          SubSys ID: 0x03C61043
        Revision ID: 0x0000
 Driver Strong Name: oem8.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_NI:12.104.0.0:pci\ven_1002&dev_6738
     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

-------------
Sound Devices
-------------
            Description: Haut-parleurs (ASUS Xonar DGX Audio Device)
 Default Sound Playback: Yes
 Default Voice Playback: No
            Hardware ID: PCI\VEN_13F6&DEV_8788&SUBSYS_85211043&REV_00
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: cmudaxp.sys
         Driver Version: 5.12.0001.0008 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 4/11/2013 19:21:06, 2734080 bytes
            Other Files:
        Driver Provider: ASUSTeK
         HW Accel Level: Basic
              Cap Flags: 0x0
    Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: Yes
 EAX(tm) 2.0 Listen/Src: Yes, Yes
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

            Description: Haut-parleurs (Logitech G35 Headset)
 Default Sound Playback: No
 Default Voice Playback: Yes
            Hardware ID: USB\VID_046D&PID_0A15&REV_0303&MI_00
        Manufacturer ID: 65535
             Product ID: 65535
                   Type: WDM
            Driver Name: USBAUDIO.sys
         Driver Version: 6.01.7601.17514 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 11/20/2010 12:43:52, 109696 bytes
            Other Files:
        Driver Provider: Logitech, Inc.
         HW Accel Level: Basic
              Cap Flags: 0x0
    Min/Max Sample Rate: 0, 0
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

[ebfd11]

Are you running 3 monitors off one video card.. much less a 6800..wow im surprised it has lasted this long.

What are your video settings in game. Try going to the bare minimum and work your way up from there..

LawnDart

[SirNuke]

Are you running 3 monitors off one video card.. much less a 6800..wow im surprised it has lasted this long.

What are your video settings in game. Try going to the bare minimum and work your way up from there..

LawnDart

its a slightly OCed ASUS DirectCU 6870, why would it not last 'this long'?

My ingame settings are the following:



I ran the game offline with vsync off for the test, and I'm doing ~130FPS in V2 tower of ndisles map:



Like I said the game runs just fine, except when I'm loosing oil  

[SirNuke]

Even if I was borderline 60fps, why would I loose 20+ fps over some smoke and a bitmap displayed on my canopy?

[Skuzzy]

Turn the anti-aliasing to 0 and set the "Maximum Texture Size" to 1024 and see what it does.  What "Shadow Texture Size" are you using?

[SirNuke]

Turn the anti-aliasing to 0 and set the "Maximum Texture Size" to 1024 and see what it does.  What "Shadow Texture Size" are you using?

1024 with smooth enabled

I like my antialiasing   Is the texture applied to the canopy in 2048?

I could try all sorts of things, but would have to wait until I'm oiled to see the resut  

[gyrene81]

Nuke, even though the 6870 is a really good card and is capable of running triple monitors like that but, ah is really cranking on it...and with your settings, the card is on the edge. you are going to have to dial something back if you want to stop the framerate loss.

[olds442]

1024 with smooth enabled

I like my antialiasing   Is the texture applied to the canopy in 2048?

I could try all sorts of things, but would have to wait until I'm oiled to see the resut  

Hence my wish a while back for when in the TA allow . commands to damage yourself but it was shot down because its "stupid"

[LCAMerciful]

Just turn shadows off altogether.  Trust me you won't miss them.

[SirNuke]

Nuke, even though the 6870 is a really good card and is capable of running triple monitors like that but, ah is really cranking on it...and with your settings, the card is on the edge. you are going to have to dial something back if you want to stop the framerate loss.

AH is not even using it at 100%

[Skuzzy]

AH is not even using it at 100%

You have no idea what the actual percentage of use is. The percentage of video card use is determinant on the CPU usage as well as how much Windows has reserved for its own use.

Simplistically stated, the amount of work the video card is doing is based on how fast the CPU can get the data to the CPU card and how many times DirectX will block the application when it has to do its own processing.

Those simplistic utilities that "measure" video card usage do not give anywhere near a complete picture of what is really going on.  Aces High works to balance the load as part of its resource management.

You guys are not helping anyone when you make these statements.

[hitech]

SirNuke, My guess is that your GPU has hit it's fill rate limit.

When Damaged like that, the extra alpha of the oil smear causes the complete screen to be filled an extra time, with blood it adds another.

HiTech

[Krusty]

FSAA doesn't play as much of a role as it once used to. It was innovative when you had to run games at low resolutions, but the video cards and the monitor support have long-since caught up. The smaller the dot pitch of the pixels, the less visible any FSAA will be to your eyes. When you get into high-def it becomes very hard to spot any difference. It also uses geometrically more VRAM for every multple you move that slider up.

Your video card just doesn't have the power, overclocked or not. You just can't get past certain bottlenecks. If you absolutely MUST have FSAA a simple 2x filter will do. You can notice that (I run a similar setup but with slightly lower resolution and more powerful video card), but anything over 2x wastes your card's muscle for no visible results.

[SirNuke]

HT's'answer makes sence as I noticed I get a framerate hits also when zooming througt the prop of the plane sometimes...I've read the wikipedia about fill rate and it says that it is directly proportinnal to the gpu's frequency, so if I manage to get a 10 percent overclock I might see an improvment. It says also that the easy way to test if the problen is fill rate related is to lower the resolution...

Thanks for the input in any case.