graphic-menu problem on ATI

[Raydowe]

hi guis. My brother has problem with menu in DCS. Multiplayer os all okay. but if he can start singleplayer, game starting ok.. but menu is WHITE.. can't see any icon... like too much brightness... if i can klick on invisible icon like quick start.... mision start ok.. i can play... but menu still white... all icons is very very bad visible. Can you help me? i downloaded drivers (Ati x2300) turn of catalyst A.I. reinstal windows (vista, W7)..but problem still here.... I don't understand.. multiplayer menu is OK!!!

 

thx for u help

 

raydowe

[Ramstein]

hi guis. My brother has problem with menu in DCS. Multiplayer os all okay. but if he can start singleplayer, game starting ok.. but menu is WHITE.. can't see any icon... like too much brightness... if i can klick on invisible icon like quick start.... mision start ok.. i can play... but menu still white... all icons is very very bad visible. Can you help me? i downloaded drivers (Ati x2300) turn of catalyst A.I. reinstal windows (vista, W7)..but problem still here.... I don't understand.. multiplayer menu is OK!!!

 

thx for u help

 

raydowe

 

Turn off AI in Catalyst control panel.. or move it to Standard.. if that doesn't completely fix it,, try a diffent Catalyst version.. even if an older version..

[EtherealN]

Multiplayer menu is ok because it resides in the dcs.exe executable, which uses DirectX. Launcher.exe however (from what I've gathered) uses OpenGL, and there are several issues in ATI's OpenGL drivers. Try reverting to version 8.12 if none of the 9.x series driver suites work.

 

Newer drivers are not always better just because they are newer, sometimes they can break things that used to work, and it appears that ATI has hada long time trying to fix the OpenGL routines that launcher.exe uses.

[JG14_Smil]

white menus with ATI are a x-fire problem. Disabling x-fire can help fix it. latest ATI drivers fix the problems, but may not support your card.

[Mustang]

Multiplayer menu is ok because it resides in the dcs.exe executable, which uses DirectX. Launcher.exe however (from what I've gathered) uses OpenGL, and there are several issues in ATI's OpenGL drivers. Try reverting to version 8.12 if none of the 9.x series driver suites work.

 

First i've heard, so DCS is an OpenGL/Direct3D kind of hybrid? learn something new everyday :)

 

And this thing about ATi drivers having OpenGL issues, that was taken care of a long long time ago, infact, the 9.8 is fully 3.1 compliant and very stable, as much as nV drivers are.

 

Newer drivers are not always better just because they are newer, sometimes they can break things that used to work, and it appears that ATI has hada long time trying to fix the OpenGL routines that launcher.exe uses.

 

I think the problems are mainly down to Raydowe's x2300 card (very low end see here http://ati.amd.com/products/mobilityradeonx2300/specs.html) not the drivers being crap, infact the 9.8 happens to be the fastest and most stable yet for DCS :)

Edited August 24, 2009 by Mustang

[Mustang]

white menus with ATI are a x-fire problem. Disabling x-fire can help fix it. latest ATI drivers fix the problems, but may not support your card.

 

Yep, pretty confident that should sort the problem out.

[EtherealN]

First i've heard, so DCS is an OpenGL/Direct3D kind of hybrid? learn something new everyday :)

 

Depends on how you look at it. DCS.exe itself uses only Direct3D. Launcher.exe uses onely OpenGL. (Well, at least, the times when I've been given proper error logs for the whitescreen problem it has been the ATI openGL driver that's gone bananas.)

 

And this thing about ATi drivers having OpenGL issues, that was taken care of a long long time ago, infact, the 9.8 is fully 3.1 compliant and very stable, as much as nV drivers are.

 

Being feature-complete and being compatible with your own hardware are two completely different things sometimes. ;)

 

I think the problems are mainly down to Raydowe's x2300 card (very low end see here http://ati.amd.com/products/mobilityradeonx2300/specs.html) not the drivers being crap, infact the 9.8 happens to be the fastest and most stable yet for DCS :)

 

Well, there's been about 3 million threads in this section with this problem, and with two-three exceptions rolling back to 8.12 has solved it completely. (In some cases disabling AI solved it with newer driver suites.) I remember a few people having good results with 9.6, allowing them to take advantage of the performance aspects of 9.6 compared to 8.12 while still being able to see what's on the launcher.exe. 9.8 I don't know, I haven't seen any reports of it specifically solving issues, but that doesn't mean it doesn't fix the issues either.

 

The fact that slightly older cards like the 1950 and such like seem (I haven't catalogued all cases of this issue with graphics card model, but it's common enough to notice) to be over-represented amongst the people that have this issue reinforce my interpretation that there most likely isn't anything wrong in the driver's support for OpenGL per se - it's just that the driver doesn't support the hardware that ATI claim it to support. Big difference. ;)

[Mustang]

Well, there's been about 3 million threads in this section with this problem, and with two-three exceptions rolling back to 8.12 has solved it completely. (In some cases disabling AI solved it with newer driver suites.) I remember a few people having good results with 9.6, allowing them to take advantage of the performance aspects of 9.6 compared to 8.12 while still being able to see what's on the launcher.exe. 9.8 I don't know, I haven't seen any reports of it specifically solving issues, but that doesn't mean it doesn't fix the issues either.

 

Check here http://forums.eagle.ru/showthread.php?t=44245 you'll see 9.8 is the best driver to date, opengl included (with the exception of Ramstein and his flakey ASRock mobo) :)

 

The fact that slightly older cards like the 1950 and such like seem (I haven't catalogued all cases of this issue with graphics card model, but it's common enough to notice) to be over-represented amongst the people that have this issue reinforce my interpretation that there most likely isn't anything wrong in the driver's support for OpenGL per se - it's just that the driver doesn't support the hardware that ATI claim it to support.

 

Anything below X2xxx series is considered legacy and is no longer supported since Catalyst 9.2, so 1950 or lower will not run with latest driver sets, they should stick to 8.12 or whatever :)

 

Anyways, i'll stop there, have this feeling this thread will go places i don't want it to ;)

[EtherealN]

Well, when I request a driver for the x1950 at the AMD site, it's the 9.3 they give me, and the only one I remember that have reliably fixed the issue for those that see it is the 8.12 (and in some cases of newer hardware the 9.6).

 

Also, it's not the only card that sees the issue and gets it fixed through reverting to older drivers, I just used it as an example since it is (naturally) overrepresented. But saying that it's unsupported only covers 9.4 and later as far as I can see, and 9.1-9.3 didn't work for it either.

 

So basically, in the example of the 1950, the driver you get referred to by AMD does not work reliably in this case. And a lot of people have been encountering the same thing with newer cards as well.

 

But thanks for the link and hopefully we'll be able to send people to the 9.8 instead of the 8.12, but it would be nice with more information on how it performs on the midrange semi-old cards first, since those are usually the first cards to cause problems. Most of the skilled people with performance computers and newer cards will often find solutions to their issues themselves, whereas borderline software is a lot more common amongst the happy amateur type user. This is a problem since a big portion of the sample we have at the Hardware section is hardware enthusiasts, whereas a big portion of the people here are those that have very limited computer experience. (My favourite ever was the person who accused us of telling him to get a "PhD in computers" to "play a game" when we wanted some information about what kind of computer he was using - any kind of information. :P )

 

I make a note to ask people to test the 9.8 if and when they report issues, to see if someone that does encounter issues with f.ex. 9.7 gets it solved. (Given, of course, that I don't find the support to have ceased for their card, in which case I guess it's 8.12 again >.< )

Edited August 24, 2009 by EtherealN

[Mustang]

Well, when I request a driver for the x1950 at the AMD site, it's the 9.3 they give me, and the only one I remember that have reliably fixed the issue for those that see it is the 8.12 (and in some cases of newer hardware the 9.6).

 

Yes, sorry, it's 9.3 my bad :)

 

But thanks for the link and hopefully we'll be able to send people to the 9.8 instead of the 8.12, but it would be nice with more information on how it performs on the midrange semi-old cards first, since those are usually the first cards to cause problems.

 

My card is as "old" as it gets, HD3850 8xAGP on an nForce3 20gb motherboard etc :P

 

Funny isn't it how i can run driver after driver and still have not problems (this is with both WinXP and now Win 7) :D

 

I apprieciate your input mate, alot of what you say is right, it's just that my back gets up if i see posts that are rubbishing ATi kit overall just because a few people have menu issues etc and thats what i thought i saw, obviously you aren't ;)

Edited August 24, 2009 by Mustang

[Mustang24]

Same problem but with GeForce 8500 GT

 

Hello i'm new.

 

I have also only a white screen when i go to the singleplayer menu, but i have a GeForce 8500 GT installed and no X-Fire......

[Panzertard]

Hi, check this thread - we may need to know more; TROUBLESHOOTING - Help us helping you.

You can also quickly test the "Disable Catalyst AI" thingy for the ATI - but having two different GPU vendors active on your computers may cause some interesting issues, indeed ...

[Mustang24]

Sorry but i have no ATI. I have a nVidia........ ????

 

I also tried to load Nvidia Driver 190.62.............. it does not help

Edited September 10, 2009 by Mustang24

[Mustang24]

HERE THE DIAG READOUT:

 

------------------

System Information

------------------

Time of this report: 9/10/2009, 18:48:18

Machine name: WINDOWS-7

Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7100) (7100.winmain_win7rc.090421-1700)

Language: German (Regional Setting: German)

System Manufacturer: FUJITSU SIEMENS

System Model: P35T-FB

BIOS: Default System BIOS

Processor: Intel® Core2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz

Memory: 2048MB RAM

Available OS Memory: 2048MB RAM

Page File: 982MB used, 3111MB 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.7100.0000 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.

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: NVIDIA GeForce 8500 GT (Microsoft Corporation - WDDM v1.1)

Manufacturer: NVIDIA

Chip type: GeForce 8500 GT

DAC type: Integrated RAMDAC

Device Key: Enum\PCI\VEN_10DE&DEV_0421&SUBSYS_09601462&REV_A1

Display Memory: 1013 MB

Dedicated Memory: 245 MB

Shared Memory: 767 MB

Current Mode: 1680 x 1050 (32 bit) (60Hz)

Monitor Name: PnP-Monitor (Standard)

Monitor Model: SyncMaster

Monitor Id: SAM027F

Native Mode: 1680 x 1050(p) (59.883Hz)

Output Type: DVI

Driver Name: nvd3dum.dll,nvwgf2um.dll

Driver File Version: 8.15.0011.8171 (English)

Driver Version: 8.15.11.8171

DDI Version: 10

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 4/22/2009 07:21:37, 6066688 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B71E3E-4761-11CF-3968-6B2901C2C535}

Vendor ID: 0x10DE

Device ID: 0x0421

SubSys ID: 0x09601462

Revision ID: 0x00A1

Driver Strong Name: nv_lh.inf:NVIDIA.Mfg.NTx86...1:nv_G86_0:8.15.11.8171:pci\ven_10de&dev_0421

Rank Of Driver: 00EC2001

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C ModeVC1_B ModeWMV9_B ModeVC1_A ModeWMV9_A

 

Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285} etc..................

 

D3D9 Overlay: Supported

DXVA-HD: Supported

DDraw Status: Enabled

D3D Status: Enabled

AGP Status: Enabled

 

-------------

Sound Devices

-------------

Description: Realtek HD Audio 2nd output (Realtek High Definition Audio)

Default Sound Playback: Yes

Default Voice Playback: Yes

Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10192634&REV_1001

Manufacturer ID: 1

Product ID: 100

Type: WDM

Driver Name: RTKVHDA.sys

Driver Version: 6.00.0001.5919 (English)

Driver Attributes: Final Retail

WHQL Logo'd: Yes

Date and Size: 8/18/2009 17:30:42, 2752352 bytes

Other Files:

Driver Provider: Realtek Semiconductor Corp.

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 2.0 Listen/Src: No, No

I3DL2 Listen/Src: No, No

Sensaura ZoomFX: No

 

Description: Kopfhörer (Realtek High Definition Audio)

Default Sound Playback: No

Default Voice Playback: No

Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10192634&REV_1001

Manufacturer ID: 1

Product ID: 100

Type: WDM

Driver Name: RTKVHDA.sys

Driver Version: 6.00.0001.5919 (English)

Driver Attributes: Final Retail

WHQL Logo'd: Yes

Date and Size: 8/18/2009 17:30:42, 2752352 bytes

Other Files:

Driver Provider: Realtek Semiconductor Corp.

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 2.0 Listen/Src: No, No

I3DL2 Listen/Src: No, No

Sensaura ZoomFX: No

 

Description: Realtek Digital Output (Realtek High Definition Audio)

Default Sound Playback: No

Default Voice Playback: No

Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10192634&REV_1001

Manufacturer ID: 1

Product ID: 100

Type: WDM

Driver Name: RTKVHDA.sys

Driver Version: 6.00.0001.5919 (English)

Driver Attributes: Final Retail

WHQL Logo'd: Yes

Date and Size: 8/18/2009 17:30:42, 2752352 bytes

Other Files:

Driver Provider: Realtek Semiconductor Corp.

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 2.0 Listen/Src: No, No

I3DL2 Listen/Src: No, No

Sensaura ZoomFX: No

 

Description: Realtek HDMI Output (Realtek High Definition Audio)

Default Sound Playback: No

Default Voice Playback: No

Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10192634&REV_1001

Manufacturer ID: 1

Product ID: 100

Type: WDM

Driver Name: RTKVHDA.sys

Driver Version: 6.00.0001.5919 (English)

Driver Attributes: Final Retail

WHQL Logo'd: Yes

Date and Size: 8/18/2009 17:30:42, 2752352 bytes

Other Files:

Driver Provider: Realtek Semiconductor Corp.

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 2.0 Listen/Src: No, No

I3DL2 Listen/Src: No, No

Sensaura ZoomFX: No

 

---------------------

Sound Capture Devices

---------------------

Description: Mikrofon (Realtek High Definition Audio)

Default Sound Capture: Yes

Default Voice Capture: Yes

Driver Name: RTKVHDA.sys

Driver Version: 6.00.0001.5919 (English)

Driver Attributes: Final Retail

Date and Size: 8/18/2009 17:30:42, 2752352 bytes

Cap Flags: 0x1

Format Flags: 0xFFFFF

[TKMR]

Didn't see any posts stating this, so I'll go ahead.

 

I am using an older ATI card, X1650 Pro 512MB (It's Sapphire. P=) and I had A LOT of problems with it and DCS in XP. I recently installed the Windows 7 RC, and didn't install any AMD/ATI drivers, letting Win7 use it's own drivers, and it works great.

 

I don't get the white screen anymore, all of the menus are how they should be, frame rates are excellent (in all my games, unlike when I was using the 8.12 drivers in XP to fix the menu problems in DCS). I also noticed that Win7 downloaded, what I assume to be, the newest ATI drivers for my card and installed them, and I everything still works.

 

For those having problems, either try the 9.x drivers that are stated to work, the 8.12 (assuming you don't play any other games, otherwise you will notice a major performance loss in every other game), making sure to disable Catalyst AI, OR try out the Windows 7 RC. It's also not a resource hog like Vista.

 

My 2 cents. =)

[Ramstein]

I tried Black Shark 1.0 on my Sapphire Radeon x1950 Pro 512mb AGP, WinXP, (not long ago) using ATI Catalyst version 8.8 and it worked fine.

 

 

FYI

[Mustang24]

I'm not using ATI is use nVidia!!! That's my problem i can find no solution.....

[Panzertard]

:music_whistling:oops my bad - I saw "x-fire" and my mind said "ATI CrossFire" ...

Windows 7 - should be okai enough.

German system - what DCS are you using? English? German? Patched? Which patch?

[Mustang24]

No problem

 

German version. Only v. 1.0

 

i will try now patch 1.0.1a

Edited September 10, 2009 by Mustang24

[Mustang24]

Still the same with 1.0.1

[Panzertard]

No problem

 

German version. Only v. 1.0

 

i will try now patch 1.0.1a

 

Careful there - there's no German patch out yet - so if you patched the German patch with English you will get problems. The only way to get rid of the problem again is to uninstall DCS + reinstall v.1.0.

[TKMR]

I'm not using ATI is use nVidia!!! That's my problem i can find no solution.....

 

Ah my bad. Saw everybody elses posts and thought the same thing as Panzer.

 

Make sure your video card isn't blowing transistors, or something?

 

Other than that, update drivers, and I don't know anything else.

[Ramstein]

I'm not using ATI is use nVidia!!! That's my problem i can find no solution.....

 

 

sorry, my comment was for EtherealN....

 

oops,, maybe your thread was 'slightly hijacked'..

:doh:

[Mustang24]

so guy's i throw my graphic card away an both a XFX 250 GTS now it's working fine...................

 

Thanks to all..........