Aces High Bulletin Board
Help and Support Forums => Aces High Bug Reports => Topic started by: Ninthmessiah on February 17, 2013, 08:40:05 PM
-
I get the following graphic issues when I'm low level and near the coast.
(http://imageshack.us/a/img690/4299/bug3d.png)
(http://imageshack.us/a/img607/3552/bug2um.png)
(http://imageshack.us/a/img266/5574/bug1u.png)
I can't remember what map these shots were taken on, but the problem isn't unique to a particular map. It also happens in planes too.
-
------------------
System Information
------------------
Time of this report: 2/17/2013, 20:40:57
Machine name: ERIC-PC
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130104-1431)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 04/02/11 15:43:11 Ver: 02.15
Processor: AMD Phenom(tm) II X4 955 Processor (4 CPUs), ~3.2GHz
Memory: 8192MB RAM
Available OS Memory: 8192MB RAM
Page File: 2006MB used, 14374MB 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: AMD Radeon Graphics Processor (0x689E)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_689E&SUBSYS_E177174B&REV_00
Display Memory: 756 MB
Dedicated Memory: 1012 MB
Shared Memory: 3839 MB
Current Mode: 1680 x 1050 (32 bit) (60Hz)
Monitor Name: X193HQL (Analog)
Monitor Model: V223W
Monitor Id: ACR001B
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.1191 (English)
Driver Version: 12.100.17.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 1/28/2013 23:54:46, 1150328 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71EE2-2BDE-11CF-5C70-7DC1BEC2C535}
Vendor ID: 0x1002
Device ID: 0x689E
SubSys ID: 0xE177174B
Revision ID: 0x0000
Driver Strong Name: oem39.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Evergreen:12.100.17.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
-
I noticed that the other night in the TA when I flew low over shallow water.
-
What are your graphic settings in game? What eye candy do you have on, and off? Is the fan running on your video card?
Either you have some of the graphic settings turned down low, or you may have an issue with your video card not running up to speed and over heating.
-
That strange shading is actually the water.
Turn on detailed water and you can enjoy a more accurately defined coast with a minimal frame rate hit.
I leave detailed terrain off for frame rate.
-
Here are my settings...
(http://imageshack.us/a/img822/930/vidcardsetings.png)
(http://imageshack.us/a/img248/1059/vidcardsetings2.png)
The card is not too hot.
(http://imageshack.us/a/img842/160/vidcardsetings3.png)
-
There's something about the detailed water. Compare the two pics...
(http://imageshack.us/a/img145/5481/vidcardsetings4.png)
As opposed to...
(http://imageshack.us/a/img209/5848/vidcardsetings5.png)
-
With detailed water and detailed terrain turned on, try disabling "local water relfections" and see what happens.
-
Since the last update, have started to see exactly the same effect, although I had changed nothing. Ive been through every setting both ingame and video card and cant seem to fix it. Only happens when flying very low on the water.
-
With detailed water and detailed terrain turned on, try disabling "local water relfections" and see what happens.
I tried this. Disabling local water reflections did not have any effect.
-
I see the same effect (and it only began recently).
-
Odd as this sounds, try "bump map terrain"...
-
I get the same thing, but only if I'm in a LVT or PT boat. If I'm in a plane just above the water, it's fine.
It started a couple of patches ago for me.
I'm also using an ATI card (5850) and have the same AA settings as Messiah.
-
Odd as this sounds, try "bump map terrain"...
Tried that too. All that does is make the sand glitch look prettier. Instead of plain sand creeping into my shallow water, I get bump mapped sand creeping into my shallow water.
Maybe it's an AMD thing?
-
Did you update the drivers recently?
-
Did you update the drivers recently?
I did not. I was using version 12.10 for months, until this post. I just updated to the latest non-beta, 13.1.
I'm not sure of Messiah. I believe he's on the latest version.
Just tried the new drivers: same results as the original problem.
If I uncheck Detailed Water it goes away.
If I uncheck Detailed Terrain it goes away.
With both on, it looks just like Messiah's screenshots.
However, when I was in a PT Boat, it was fine. It was only happening in a LVT.
-
Maybe it's an AMD thing?
I get this same effect ever since I installed the latest drivers,13.1 IIRC. Skuzzy recommended it if you had issues with texture rebuilding and I was. It seemed to resolve that issue but then I saw the same issue as the OP when I had detailed water enabled.
I disabled detailed water and it seems to resolve the issue for now but would prefer to use detailed water.
It seems as if this only happens with the ATI cards as I've heard others complain of the same thing and when asked they always have an ATI card.
:salute
-
I have the same problem, am using an AMD Radeon HD 6670.
-
Mine is Radeon also (7870 on 12.8 drivers).
-
I'm using the beta driver that Skuzzy mentioned in http://bbs.hitechcreations.com/smf/index.php/topic,344807.0.html
I can't remember at which patch the anomoly started to occur. I just remember that one day I was on an NOE mission and noticed wierd graphics on the water.
-
Thats what it is starting to look like to me, a driver issue with the AMD cards. It might be one of those "which can I live with things" now. Newer drivers give you shore line issues, old driver texture building issues.
-
If you have to choose detailed water vs detailed terrain and can only run one, choose detailed water.
-
If you have to choose detailed water vs detailed terrain and can only run one, choose detailed water.
Or in my case (perhaps others), just deal with the effect if in a LVT... :)
The game can sure get ugly quick when you start unchecking the detail boxes. hehe
-
I have not had this problem with the HD 7750 but I did not load the Beta drivers.
-
I have this problem since the last major update.
Before the major update i noticed this same problem with the towns concrete, tho at that time i had no problem with the nearshore water. I seems to me the problem in town went back two more major updates prior to the major update that currently caused the water issue. Im not sure if the problem in town persists today.
-
I have not had this problem with the HD 7750 but I did not load the Beta drivers.
It seems it's various ATI cards, and at least a few versions of drivers. I have confidence that it will be fixed in an upcoming patch or release. :)
-
It seems it's various ATI cards, and at least a few versions of drivers. I have confidence that it will be fixed in an upcoming patch or release. :)
...of the ATI drivers. ;)
I don't think it's an issue for HTC to solve, as not everyone is experiencing this. If they can, more power to 'em, but it is really sounding like a driver issue with ATI.
-
i run ati radeon HD 2600 XT
-
ATI 6770
I only became aware I had this issue of flickering white lines near the coast line when I was on an NOE after 2.29 was released. With 2.29 the game also started changing me from UDP to TCP and kicking me out a few minutes after making it into the main arena. Along with that the game would disable all of my advanced video settings. After being discoed out I could log back in, reenable my advanced settings, and play on with no problems. Getting tired of this process every night along with none of the subsiquent updates addressing it. In the catalyst control panel I set everything to "application settings" or performance. Then I disabled all bumpmapping in the game. This stopped the discos but, not the flashing white lines.
Skuzzy mentioned the 13.2 beta drivers addressing a DX9 issue with textures. So I installed those. I've been able to increase some of my catalyst settings from performance back to quality. I still get a more ghost like version of the flickering white lines but, not as starkly pronounced now. And about where the disco would happen my game will freeze for up to 10 seconds sometimes just after I get logged on and at a feild with lot's of action and VOX. Then carry on with no problems.
With the release of 2.29 p5 my startup screen and the processing screen just after choosing an arena can take twice as long as normal to finaly produce the tower. Sometimes when I first launch Aces High, the startup screen will sit white 20-30 seconds. When I choose offline or online it will sit the same amount of time with a blank window. After that if I have to close out the game then restart it for any reason the expected startup process and time is in force.
---------------------------------------------------------------------------------------------------------------------------
Current video drivers: AMD_Catalyst_13.2_Beta5
-----------------
System Information
------------------
Time of this report: 2/19/2013, 15:08:31
Machine name: BUSTR-PC
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130104-1431)
Language: English (Regional Setting: English)
System Manufacturer: System Manufacturer
System Model: ASUS P5Q Pro
BIOS: BIOS Date: 02/23/09 21:14:18 Ver: 08.00.14
Processor: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz (2 CPUs), ~3.2GHz
Memory: 8192MB RAM
Available OS Memory: 8192MB RAM
Page File: 1544MB used, 14835MB 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.
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: AMD Radeon HD 6700 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x68BA)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_68BA&SUBSYS_C0131092&REV_00
Display Memory: 756 MB
Dedicated Memory: 1012 MB
Shared Memory: 3839 MB
Current Mode: 1680 x 1050 (32 bit) (60Hz)
Monitor Name: SyncMaster 2253BW/2253LW,SyncMaster Magic CX2253BW(Digital)
Monitor Model: SyncMaster
Monitor Id: SAM037C
Native Mode: 1680 x 1050(p) (59.883Hz)
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.1191 (English)
Driver Version: 12.100.17.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 2/2/2013 13:00:38, 1150328 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71EE2-2BFA-11CF-8577-19E0BEC2C535}
Vendor ID: 0x1002
Device ID: 0x68BA
SubSys ID: 0xC0131092
Revision ID: 0x0000
Driver Strong Name: oem36.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Evergreen:12.100.17.0:pci\ven_1002&dev_68ba
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 (Plantronics GameCom 780)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: USB\VID_047F&PID_C010&REV_0100&MI_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: PLTGC.sys
Driver Version: 7.00.0008.2157 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 11/4/2011 16:47:58, 1327104 bytes
Other Files:
Driver Provider: C-Media Inc.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 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
---------------------
Sound Capture Devices
---------------------
Description: Microphone (Plantronics GameCom 780)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: PLTGC.sys
Driver Version: 7.00.0008.2157 (English)
Driver Attributes: Final Retail
Date and Size: 11/4/2011 16:47:58, 1327104 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF
-
I just tried it, at home, on my 7950 (3GB of video RAM). I get Z fighting issues at the water edge, but not what the original poster is seeing at all.
The Z fighting is there as long as 'Detailed Water' is enabled, regardless of any other option.
I believe I am running the 64 bit Catalyst 12.6 or 12.8 drivers (DXDIAG ATI Version shows 8.982.0.0), without the Catalyst Control Center and sound driver installed.
bustr, most of what you are describing sounds like resource and Internet connection issues. See me in the Tech Support forum about it.
-
I get the following graphic issues when I'm low level and near the coast.
(http://imageshack.us/a/img690/4299/bug3d.png)
(http://imageshack.us/a/img607/3552/bug2um.png)
(http://imageshack.us/a/img266/5574/bug1u.png)
I can't remember what map these shots were taken on, but the problem isn't unique to a particular map. It also happens in planes too.
I get the same.
ATi Radeon HD5770
I updated the driver to try and clear it... Didn't work.
It's really irritating in LVTs, flickering etc.
-
I just tried it, at home, on my 7950 (3GB of video RAM). I get Z fighting issues at the water edge, but not what the original poster is seeing at all.
The Z fighting is there as long as 'Detailed Water' is enabled, regardless of any other option.
I believe I am running the 64 bit Catalyst 12.6 or 12.8 drivers (DXDIAG ATI Version shows 8.982.0.0), without the Catalyst Control Center and sound driver installed.
bustr, most of what you are describing sounds like resource and Internet connection issues. See me in the Tech Support forum about it.
Skuzzy,
Did you test it in a plane, or in a LVT? I only see it when in a LVT. Low planes, even PT boats, are fine.
Thanks.
-
I was in a Jeep. I'll try an LVT tonight.
-
have the same issue started two updates ago, just turn off detail water woorks see this near shore in noe run and in lvts
Display Devices
---------------
Card name: AMD Radeon HD 6670
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x6758)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_6758&SUBSYS_318C1682&REV_00
Display Memory: 3818 MB
Dedicated Memory: 2030 MB
Shared Memory: 1787 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: T27B350
Monitor Id: SAM0945
Native Mode: 1920 x 1080(p) (60.000Hz)
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.1172 (English)
Driver Version: 9.12.0.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 12/19/2012 15:08:04, 1151488 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-2418-11CF-A671-8611BEC2C535}
Vendor ID: 0x1002
Device ID: 0x6758
SubSys ID: 0x318C1682
Revision ID: 0x0000
Driver Strong Name: oem21.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_NI:9.12.0.0:pci\ven_1002&dev_6758
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C
dhawk
-
I see it mostly in LVTs but I also see it when flying very low noe over the water near the coastline in, say, a C47. Also, it looks very much like the OPs pics and it flickers in and out like Z-fighting.
-
I too am having the same issues along to coast line while in an lvt. By turning off the detailed water eliminates this glitch. I noticed this, (sand to water), effect since the last patch. I merely leave detailed water off to solve this issue.
-
Something I noticed last night,the shadows under the trees give an odd flickering effect. The strange thing is I have shadows turned off,sef shadows,shadows on buildings,etc.
I wonder if this is related to the Z fighting,as I have no idea what that is or does.
:salute
-
bustr, most of what you are describing sounds like resource and Internet connection issues. See me in the Tech Support forum about it.
I fixed all of that by uninstalling both my Plantronics 780 and the game. First reinstalling the plantronics then a full install of the game. The game dosen't like the Dolby option with the 780 at all. If anything the less speakers I virtulise the better the game likes it in terms of resource problems. I'm getting VOX or occasional texture stutter hangs with the default video settings. I disabled grass and bumpmapping buildings. I still see the Z-fighting low on shores in the water or sitting in a GV looking at bomb craters in the concrete.
I'm doing the new sound beta. It detects the plantronics sources correctly and sources the speakers through the windows configuration. I'm getting a much better game experience with it.
-
I posted before I had not had the problem. Last night I bailed and came down on the beach. Just as others posted, the graphics went wonky and my guy was laying on his side after landing.
-
I'm glad its not just me, I thought my HIS readeon 6870 was failing.
-
I posted before I had not had the problem. Last night I bailed and came down on the beach. Just as others posted, the graphics went wonky and my guy was laying on his side after landing.
I installed the beta drivers and the problem is much worse. I did not see it from the plane before the beta drivers but now I do when I get near any water.
HD 7750
-
after reinstalling drivers, did you directx the machine again or at least run dxdiag to check for issues?
-
I get the same thing. I get a lot of "sand" lines in the water regardless if I am in an aircraft or LVT.
-
Here is what worked for me. I turned off detailed water and turned on bump map terrain. I actually like the water better that way anyway. It may not work for y'all but it is worth a try.
I went offline practice set the plane at 200 feet and auto level and started playing with the graphic detail setting until I got it to go away.
I have a HD 7750 using the beta drivers.
-
Was having this problem, I5 Hd5770, 12 gb ram.
Tried all settings and driver options with no luck, then by serendipity, I seem to have fixed the problem.
I believe what actually worked, and also helped with smoothing out micro stutters, was to uncheck enable ground clutter. I assumed that disable ground clutter in flight would have been enough but disabling it all together really makes a huge difference. More of a hit than than detailed water or reflections or bump mapping anything. Not sure if its a bug or the fact that ground clutter causes a huge drain on cpu/ graphics.
-
On my machine disabling Ground Clutter has no effect on the artifact. The only thing that gets rid of the artifact is turning off detailed water.
-
Needs to be worked on, quick sharp.
Makes depth perception impossible at speed, I have a disintegrated 262 to show for it. :old:
-
It's fixed for the next version.
-
It's fixed for the next version.
YAAAAAAYYYEEEE!!! :banana:
-
It's fixed for the next version.
Awesome, thanks chaps :salute