Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: nimble on October 10, 2009, 01:55:43 AM
-
Not getting shadows anymore since the update that I have noticed. Everytime I takeoff I get the error in the title.
------------------
System Information
------------------
Time of this report: 10/10/2009, 02:47:11
Machine name: MADHATTER
Operating System: Windows Vista™ Home Premium (6.0, Build 6001) Service Pack 1 (6001.vistasp1_gdr.090302-1506)
Language: English (Regional Setting: English)
System Manufacturer: alienware
System Model: Aurora R5
BIOS: BIOS Date: 03/24/09 Ver: 08.00.14
Processor: AMD Phenom(tm) 9950 Quad-Core Processor (4 CPUs), ~2.6GHz
Memory: 3070MB RAM
Page File: 3625MB used, 2753MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 10
DX Setup Parameters: Not found
DxDiag Version: 6.00.6001.18000 32bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Sound Tab 4: No problems found.
Sound Tab 5: 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 4850
Manufacturer: ATI Technologies Inc.
Chip type: ATI Radeon Graphics Processor (0x9442)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_9442&SUBSYS_05021002&REV_00
Display Memory: 1786 MB
Dedicated Memory: 506 MB
Shared Memory: 1279 MB
Current Mode: 1440 x 900 (32 bit) (60Hz)
Monitor: Generic PnP Monitor
Driver Name: atidxx32.dll,atidxx64,atiumdag.dll,atiumdva.dat,atiumd64,atiumd6a,atitmm64
Driver Version: 7.15.0010.0127 (English)
DDI Version: 10.1
Driver Attributes: Final Retail
Driver Date/Size: 6/10/2008 22:02:42, 1626624 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-D702-11CF-E771-0825A1C2CA35}
Vendor ID: 0x1002
Device ID: 0x9442
SubSys ID: 0x05021002
Revision ID: 0x0000
Revision ID: 0x0000
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
{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
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
-
Anyone? A tight rolling scissor low can suck without shadows :(
-
Hey Nimble,
What shadow map resolution do you have your shadows set to?
I noticed on my video card, if I set my shadow map resolution to 8192, I get that same error message every time. If I set to 4096 I get that error after a few sorties or a lot of flying (and very low framerates). If I set to 2048 I get lowish framerates but never the error, and at 1024 get good framerates and no error. I've suspected this particular error message comes when your video card runs out of memory for shadows.
I have 320MB of memory on my video card. Yours appears to be a 4850 512MB card (nice BTW), but depending on your AA and Antistropic filtering, you may be running out of video memory (yes, even with 512MB), and hitting limit. Try turning your smooth shadows down 1 notch and see how it works.
-
Yep, what Knite said.
-
Dunno if I am running out of vid men or not. I set the shadow to the max setting. As for the graphics card, I have 2 of those 4850s 512mb in sli(crossfire for ati?) working together. Does AH2 take advantage of multiple gpus?
I'll try tinkering with the shadow settings to see if that fixes it!
-
Hey Nimble,
Even if AH takes advantage of 2 video cards in SLI (aka Crossfire if ATI cards), the amount of MEMORY used is still only what is on a card individually. Running 2 512MB video cards in SLI or Crossfire does NOT act as if you had a 1GB card. It acts more like 1 very fast 512MB card (if the game in question doesn't have any conflicts).
Therefore, your video cards are probably beating the crap out of AH from a calculation standpoint, but still running out of memory. Set that Shadow setting to 4096 or 2048 and the error should go away. OR, if you want to make sure to keep that high shadow setting, try running with NO Anti-Aliasing, as AA also takes from that same memory pool (so does Antistropic Filtering, as well as higher resolutions).
-
Ah gotcha, thanks for the info, I'll lower it tonight! Much appreciated!