Author Topic: Rendering issue  (Read 611 times)

Offline clerick

  • Silver Member
  • ****
  • Posts: 1742
Rendering issue
« on: October 30, 2011, 12:33:18 AM »
I have this issue, as seen on the map room, often. I don't know what it's called but it affects a number of objects in AHII, I also get a situation often where edges will seem jagged and moving at a distance.


I know my system RAM is very low and that'll be addressed soon. My frame rate is pretty decent with moderate eye candy I just have a few weird things like the picture.

DXDIAG
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
           Language: English (Regional Setting: English)
System Manufacturer: Compaq-Presario
       System Model: BM412AA-ABA CQ5600Y
               BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: AMD Athlon(tm) II 170u Processor, ~2.0GHz
             Memory: 2048MB RAM
Available OS Memory: 2046MB RAM
          Page File: 1907MB used, 3208MB 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 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: 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: 1783 MB
   Dedicated Memory: 1016 MB
      Shared Memory: 767 MB
       Current Mode: 1680 x 1050 (32 bit) (60Hz)
       Monitor Name: HP w2007 Wide LCD Monitor
      Monitor Model: HP w2007
         Monitor Id: HWP26A7
        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.1094 (English)
     Driver Version: 8.892.0.0
        DDI Version: 11
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 9/8/2011 12:32:58, 862720 bytes
        WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
  Device Identifier: {D7B71EE2-2B99-11CF-7471-5A10BEC2C535}
          Vendor ID: 0x1002
          Device ID: 0x68D9
          SubSys ID: 0x30501682
        Revision ID: 0x0000
 Driver Strong Name: oem90.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Evergreen:8.892.0.0:pci\ven_1002&dev_68d9
     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: Speakers (Realtek High Definition Audio)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_103C2A6C&REV_1002
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.6449 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: n/a
          Date and Size: 8/30/2011 17:28:46, 3069032 bytes
            Other Files:
        Driver Provider: Realtek Semiconductor Corp.
         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

Offline gyrene81

  • Plutonium Member
  • *******
  • Posts: 11629
Re: Rendering issue
« Reply #1 on: October 30, 2011, 11:01:23 AM »
what's your paging file size after a fresh boot with anti-virus disabled? and 2048mb of ram is just enough to run win7, if your paging file is 1907mb then you're system is running out of resources before you even start the game.
jarhed  
Build a man a fire and he'll be warm for a day...
Set a man on fire and he'll be warm for the rest of his life. - Terry Pratchett

Offline 715

  • Silver Member
  • ****
  • Posts: 1835
Re: Rendering issue
« Reply #2 on: October 30, 2011, 01:49:56 PM »
I see that sometimes as well and I have plenty of RAM.

Offline MrRiplEy[H]

  • Persona Non Grata
  • Plutonium Member
  • *******
  • Posts: 11633
Re: Rendering issue
« Reply #3 on: October 30, 2011, 03:21:55 PM »
The 5500 graphics card line is a very low end one and there are reported problems with drivers relating to it. I would try updating or rolling back drivers, new ones are not necessarily the best choice for the lower budget cards. So best to try different revisions out first, if you're comfortable with cleaning and installing drivers that is.
Definiteness of purpose is the starting point of all achievement. –W. Clement Stone

Offline clerick

  • Silver Member
  • ****
  • Posts: 1742
Re: Rendering issue
« Reply #4 on: October 30, 2011, 06:36:52 PM »
what's your paging file size after a fresh boot with anti-virus disabled? and 2048mb of ram is just enough to run win7, if your paging file is 1907mb then you're system is running out of resources before you even start the game.

It is, for some reason, set to manual with a minimum of 3 to a max of 7.

Offline gyrene81

  • Plutonium Member
  • *******
  • Posts: 11629
Re: Rendering issue
« Reply #5 on: October 30, 2011, 07:21:49 PM »
It is, for some reason, set to manual with a minimum of 3 to a max of 7.
no, what i'm talking about is the amount of memory being used by programs/processes after a fresh boot, that is the first number on the paging file line.

Page File: 1907MB used, 3208MB available

shut the system down, the power it back up, once windows has finished the full boot process disable your anti-virus then open the task manager and check the memory usage under the performance tab...



you might want to try ripley's advice too...
The 5500 graphics card line is a very low end one and there are reported problems with drivers relating to it. I would try updating or rolling back drivers, new ones are not necessarily the best choice for the lower budget cards. So best to try different revisions out first, if you're comfortable with cleaning and installing drivers that is.



I see that sometimes as well and I have plenty of RAM.
post a dxdiag after you do a fresh boot...it could be your video card.
jarhed  
Build a man a fire and he'll be warm for a day...
Set a man on fire and he'll be warm for the rest of his life. - Terry Pratchett

Offline Chalenge

  • Plutonium Member
  • *******
  • Posts: 15179
Re: Rendering issue
« Reply #6 on: October 30, 2011, 10:53:48 PM »
Clerick it might help also if you turned off all of the Windows visual effects. You can do this in Control Panel under System - Advanced System Settings - Advanced Tab - under Performance click Settings - Visual Effects tab - Select Adjust for best performance.
If you like the Sick Puppy Custom Sound Pack the please consider contributing for future updates by sending a months dues to Hitech Creations for account "Chalenge." Every little bit helps.

Offline clerick

  • Silver Member
  • ****
  • Posts: 1742
Re: Rendering issue
« Reply #7 on: October 31, 2011, 01:44:02 AM »
Clerick it might help also if you turned off all of the Windows visual effects. You can do this in Control Panel under System - Advanced System Settings - Advanced Tab - under Performance click Settings - Visual Effects tab - Select Adjust for best performance.

I have a "booster" program that handles all of the process killing etc before I play.  Without that it would be impossible.  I haven't had a chance to run the other tests that were mentioned yet.

Work>:ahand<me

Offline clerick

  • Silver Member
  • ****
  • Posts: 1742
Re: Rendering issue
« Reply #8 on: October 31, 2011, 05:51:41 AM »
ok. I'm posting 2, count them, 2 DXDIAG's.

First, reboot, AV turned off as much as I know how.

Time of this report: 10/31/2011, 05:39:48
       Machine name: HORNET
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
           Language: English (Regional Setting: English)
System Manufacturer: Compaq-Presario
       System Model: BM412AA-ABA CQ5600Y
               BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: AMD Athlon(tm) II 170u Processor, ~2.0GHz
             Memory: 2048MB RAM
Available OS Memory: 2046MB RAM
          Page File: 1302MB used, 2790MB 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

Second, reboot, AV off AND Game booster... boosting...
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
           Language: English (Regional Setting: English)
System Manufacturer: Compaq-Presario
       System Model: BM412AA-ABA CQ5600Y
               BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: AMD Athlon(tm) II 170u Processor, ~2.0GHz
             Memory: 2048MB RAM
Available OS Memory: 2046MB RAM
          Page File: 1175MB used, 2917MB 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

Offline gyrene81

  • Plutonium Member
  • *******
  • Posts: 11629
Re: Rendering issue
« Reply #9 on: October 31, 2011, 08:38:50 AM »
ok clerick that tells me you need to stop a lot of unnecessary processes, the standard configuration is eating up 50%+ of your available memory. and your game booster program isn't doing a thing for you. start up memory usage shouldn't be any higher than ~850mb.

i'm not going to repost all the processes you can disable because there are several posts with big lists between the hardware/software and tech support sections of the forums. to start with, put at least 2gb more ram in that system then, set the windows automatic update process to disabled or manual, turn off the windows aero interface, then find other discussions where people have been given lists of processes to disable in windows 7.
jarhed  
Build a man a fire and he'll be warm for a day...
Set a man on fire and he'll be warm for the rest of his life. - Terry Pratchett

Offline Chalenge

  • Plutonium Member
  • *******
  • Posts: 15179
Re: Rendering issue
« Reply #10 on: October 31, 2011, 12:32:03 PM »
I have a "booster" program that handles all of the process killing etc before I play.  Without that it would be impossible.  I haven't had a chance to run the other tests that were mentioned yet.

I dont think thats a process. I also dont think that even AlacrityPC could be much help with your limited memory but what your using isnt doint anything for you.

If you like the Sick Puppy Custom Sound Pack the please consider contributing for future updates by sending a months dues to Hitech Creations for account "Chalenge." Every little bit helps.

Offline clerick

  • Silver Member
  • ****
  • Posts: 1742
Re: Rendering issue
« Reply #11 on: October 31, 2011, 03:29:39 PM »
i'm not going to repost all the processes you can disable because there are several posts with big lists between the hardware/software and tech support sections of the forums. to start with, put at least 2gb more ram in that system then, set the windows automatic update process to disabled or manual, turn off the windows aero interface, then find other discussions where people have been given lists of processes to disable in windows 7.

I know I need the RAM, just hasn't affected playability so I haven't made it a huge priority.

As for everything else, processes, auto-update, aero etc... Done and done a long time ago.

My main reason for posting this was to try and find out if it was a lack of resources issue or a harbinger of doom for some piece of hardware.  The latter is bad, the former I can live with, for now :D

 :salute