Author Topic: Clouds not displaying correctly. (Read 676 times)

Swoop · « **on:** August 31, 2007, 07:25:47 PM »

My clouds look like this:

Read that enabling hardware vertex wossnaming cure's it. Trouble is with that enabled I get random freezes that require a cold reboot to resolve.

system:

AMD 64 dual core 4200
2Gb RAM
Radeon X1950 w/ catalyst 6.14

P.S. Ello Skuzzy, long time no see.

Swoop · « **Reply #1 on:** September 03, 2007, 10:15:24 AM »

Auger · « **Reply #2 on:** September 03, 2007, 11:33:07 AM »

Swoop, have you tried newer drivers? There are about 8 newer versions of the driver for that video card. Perhaps one of them will fix it. Just make sure you keep the installer for your current version.

Swoop · « **Reply #3 on:** September 04, 2007, 04:12:22 AM »

The curious thing is......I downloaded and installed the latest drivers for the 1950 about 3 weeks ago. But the driver version as shown in control panel never changes.

Bruv119 · « **Reply #4 on:** September 04, 2007, 04:19:37 AM »

if the driver number doesn't change it isn't uninstalling them correctly.

Swoop do a search for driver cleaner. This program helps clear out some of the leftover files when swapping between different drivers.

Speed55 · « **Reply #5 on:** September 04, 2007, 07:18:02 AM »

http://www.tweakguides.com/ATICAT_3.html

Read the entire page, then follow the steps 1 by 1 and you should have no problem.

Swoop · « **Reply #6 on:** September 07, 2007, 01:12:45 PM »

Got around to cleaning driver completely as described and reinstalling.

Most def now have catalyst 7.6 installed.

nuthin has changed.

Swoop · « **Reply #7 on:** September 07, 2007, 01:21:05 PM »

With hardward vertex wossname enabled the following appears in event viewer:

Event Type:   Error
Event Source:   Application Hang
Event Category:   (101)
Event ID:   1002
Date:      07/09/2007
Time:      18:34:27
User:      N/A
Computer:   *****
Description:
Hanging application aceshigh.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 61 63 65 73 68 69 aceshi
0018: 67 68 2e 65 78 65 20 30 gh.exe 0
0020: 2e 30 2e 30 2e 30 20 69 .0.0.0 i
0028: 6e 20 68 75 6e 67 61 70 n hungap
0030: 70 20 30 2e 30 2e 30 2e p 0.0.0.
0038: 30 20 61 74 20 6f 66 66 0 at off
0040: 73 65 74 20 30 30 30 30 set 0000
0048: 30 30 30 30 0000

Swoop · « **Reply #8 on:** September 10, 2007, 02:37:09 AM »

Ok, more PD:

Ive found that now if I set hardware vertex wossname on I can fly in the session that's active. If I then quit AH and run it again later I get hard freezes as described. Seems if I open video settings, turn off hardware wossname, log in and fly a sortie....then quit back out to the main screen, back to video settings and turn hardware wossname back on.....everything is fine.

Skuzzy?

Swoop · « **Reply #9 on:** September 11, 2007, 05:56:40 AM »

Ello?

Skuzzy · « **Reply #10 on:** September 11, 2007, 06:10:11 AM »

Swoop, I need to see the output of DXDIAG.

Swoop · « **Reply #11 on:** September 11, 2007, 11:53:42 AM »

no worries. Emailed cos it was huge.

Appreciate the assistance.

scottydawg · « **Reply #12 on:** September 11, 2007, 01:17:44 PM »

Swoop,

A lot of the times video drivers don't uninstall gracefully when you update and you get stuck with mixed versions. I would say go to guru3d and get their driver cleaner http://downloads.guru3d.com/download.php?det=1275
and reinstall the catalyst drivers... not sure I would use the latest ones, I've had mixed results with NVidia drivers and am using some older ones.

odin3 · « **Reply #13 on:** September 13, 2007, 06:11:06 AM »

man thats trippy.. is your pilot on acid or something cuz i think they have strict rules on pilots being on drugs or something...

Denholm · « **Reply #14 on:** September 13, 2007, 10:48:13 AM »

I noticed you have a dual core processor Swoop. Can't remember but wasn't it the dual or quad core that was required to be restricted to one core to correctly run Aces High?