CATALYST™ v3.8 available! Feedbacks here please!

[Kombatant]

Originally posted by Kruno
Red Dog I'm also using XP.
Like I said before, if the beta team didn't pick up the bug and report it the reason would most likely be because they didn't experience the bug.

When a bug exist in the driver, it doesn't mean that the beta team hasn't picked it up. It might as well mean that the beta team reported it but the fix didn't make the timeframe for the release candidate build and will be incorporated in a future release. That's how it usually happens.

[Sammy123]

Originally posted by saturnotaku
2xAA works just fine, it's just that the control panel doesn't display that fact. It's a bug in the control panel, not in the driver itself.

No....it does not work PERIOD. Have you tested any of this yourself or are you going by what other people are saying?

I cannot set to 2x mode whatsoever. When setting to 2x on the control panel, the true AA settting would be the last applied AA setting regardless of what's said in the control panel. For example, if I set it to 4x AA, and then switch over to 2x AA in the control panel, the panel will say Application preference but it will STILL be in 4x mode. Likewise, if I set it to 6x AA and switch back to 2x, it will STILL be in 6x mode even though it says Application preference in the control panel.

2x FSAA seems to be unattainable. It appears it requires some kind of combination I haven't tried yet to get to that mode, but I didn't download these drivers just to play a friggin' puzzle. Hell I even tried applying 2x twice in a row....still 4x or 6x or whatever I had before.

Funny there's only one game I use 2x FSAA with, Flight Simulator 2004, and it's driving me off the wall since its one of the games I play the most. 4x and 6x FSAA is virtually unplayable in FS2004 (and I don't mean flying through spartan terrain with very little 3d clouds like some people claim they can play 6x AA and 16x AF with), and since 16x AF uses an extra cycle I bump that down to 8x as well.

Someone mentioned Rtool so I'll give that a try.

-Sammy
Athlon XP 3000 (Barton), Radeon 9800 Pro, Gigabyte LN-400 (nforce 2)

[Kombatant]

Originally posted by Sammy123
No....it does not work PERIOD. Have you tested any of this yourself or are you going by what other people are saying?

Yes it does. Period. :rolleyes:

[Sotos]

Originally posted by Sammy123
No....it does not work PERIOD. Have you tested any of this yourself or are you going by what other people are saying?

I cannot set to 2x mode whatsoever. When setting to 2x on the control panel, the true AA settting would be the last applied AA setting regardless of what's said in the control panel. For example, if I set it to 4x AA, and then switch over to 2x AA in the control panel, the panel will say Application preference but it will STILL be in 4x mode. Likewise, if I set it to 6x AA and switch back to 2x, it will STILL be in 6x mode even though it says Application preference in the control panel.

2x FSAA seems to be unattainable. It appears it requires some kind of combination I haven't tried yet to get to that mode, but I didn't download these drivers just to play a friggin' puzzle. Hell I even tried applying 2x twice in a row....still 4x or 6x or whatever I had before.

Funny there's only one game I use 2x FSAA with, Flight Simulator 2004, and it's driving me off the wall since its one of the games I play the most. 4x and 6x FSAA is virtually unplayable in FS2004 (and I don't mean flying through spartan terrain with very little 3d clouds like some people claim they can play 6x AA and 16x AF with), and since 16x AF uses an extra cycle I bump that down to 8x as well.

Someone mentioned Rtool so I'll give that a try.

-Sammy
Athlon XP 3000 (Barton), Radeon 9800 Pro, Gigabyte LN-400 (nforce 2)

The others are right...

I am sure that you are wrong..

I have just tested these in my 9800pro system and i have not these kind of problem...

I am sure either you have not installed the drivers right or something else is wrong but it is sure that it is not the drivers prorblem

Reinstall the drivers and try again
-------------
Note (make a clean Install remove any previous driver files before installing the Catal 3.8 again)

[bkswaney]

Well, I like the way the AA/AF is layed out now. :)

[Sammy123]

Yes it does. Period.

I guess all those countless posts from users sharing my same problem posted on that worthless website of yours are false propaganda eh? I guess the workaround to make 2x stick by rebooting (and later setting different refresh rates) was some folk story posted up by users who have 0 2x FSAA issues eh?

And you were a beta tester? :angel2:

We don't need idiots like you supposedly "testing" these drivers and allowing them for release. I've moved back down to 3.6 until a more competent driver release is made available.

[Sotos]

Originally posted by Sammy123
I guess all those countless posts from users sharing my same problem posted on that worthless website of yours are false propaganda eh? I guess the workaround to make 2x stick by rebooting (and later setting different refresh rates) was some folk story posted up by users who have 0 2x FSAA issues eh?

And you were a beta tester? :angel2:

We don't need idiots like you supposedly "testing" these drivers and allowing them for release I've moved back down to 3.6 until a more competent driver release is made available.


SAMMY

REMEMBER
ACCORDING NVNEWS REGISTER LAW

<<<INSULTING IN FORBIDDEN>>>

Kombatand did not insult you so please WATCH YOUR LANGUAGE...

Note:
By the way because YOU have problems with 3.8 does not mean that they SUCK or we have it too

As i told you i do not have these problem so these has to do with something with your system or something you do wrong

I suggest you reinstall the 3.8 as i already told you...Now if you are to stubborn to understand and you start INSULTING people then i suggest you go somewhere else...

[saturnotaku]

Originally posted by Sammy123
No....it does not work PERIOD. Have you tested any of this yourself or are you going by what other people are saying?


Oh my God, you've figured me out and exposed my evil plan. :eek:

It might not work for you, but it works perfectly fine for me. All AA modes in D3D and OpenGL are 100% functional regardless of how often I switch among them. I ain't gonna say you did anything wrong with the installation, but it looks like you were smart enough to figure out that you can roll back to a previous driver set so I at least have to give you a smidge of credit.

Just cause it works for me and not for you don't mean you gotta ***** at me. That's just weak.

[CATALYST MAKER]

Originally posted by Sammy123
I guess all those countless posts from users sharing my same problem posted on that worthless website of yours are false propaganda eh? I guess the workaround to make 2x stick by rebooting (and later setting different refresh rates) was some folk story posted up by users who have 0 2x FSAA issues eh?

And you were a beta tester? :angel2:

We don't need idiots like you supposedly "testing" these drivers and allowing them for release. I've moved back down to 3.6 until a more competent driver release is made available.

Sammy,
Kombatant volunteers lots of his free time to help the ATI community. Please keep that in mind when you call him an idiot.

If you have a problem with CATALYST please do not blame him or other beta testers for it. Blame me and ATI for not catching it.

Now back to the topic at hand.
Can you give me a detailed step by step way of reproducing this bug so I can see for myself if it is a driver bug or your system configuration?

[Sotos]

Originally posted by saturnotaku
Oh my God, you've figured me out and exposed my evil plan. :eek:

It might not work for you, but it works perfectly fine for me. All AA modes in D3D and OpenGL are 100% functional regardless of how often I switch among them. I ain't gonna say you did anything wrong with the installation, but it looks like you were smart enough to figure out that you can roll back to a previous driver set so I at least have to give you a smidge of credit.

Just cause it works for me and not for you don't mean you gotta ***** at me. That's just weak.

He\she didn't talk about you but about Kombatant

[Sotos]

CATALYST MAKER

there is a serious bug report about Catalysts 3.8 making 9800\pro raising heat by 10 degrees more from older drivers...

Have you checked it out???

[CATALYST MAKER]

Originally posted by Sotos
CATALYST MAKER

there is a serious bug report about Catalysts 3.8 making 9800\pro raising heat by 10 degrees more from older drivers...

Have you checked it out???

Yes we have and we do not see a 10 degree increase.

We are analyzing in full detail but so far we do not see the problem.

[Sammy123]

It might not work for you, but it works perfectly fine for me. All AA modes in D3D and OpenGL are 100% functional regardless of how often I switch among them. I ain't gonna say you did anything wrong with the installation, but it looks like you were smart enough to figure out that you can roll back to a previous driver set so I at least have to give you a smidge of credit.


What does it say in the control panel after you set it to 2x and apply it? Does it say application preference, 2x, 4x, or what?

As I said before, in my case I cannot set to 2x whatsoever regardless of what's set in the panel.....until someone pointed out in a rage3d thread (not just MY problem as you now know) to do a reboot after setting. Bingo 2X FSAA works. Later someone found out a way to avoid rebooting my applying a different game refresh, or something of the sort....but by then I had already rolled back to 3.6

I'd link that thread here but rage3d seems to be in the crapper. Point I'm trying to make I was not alone with this problem.

Maybe when I uninstalled 3.5 something was still left behind, or maybe its finicky ATI drivers. Replies like this "Yes it does. Period. " followed by a rolled eye from a supposed beta tester, ignoring posts from users on their own website reporting quite the opposite, don't give me much faith in ATI's driver progression.

[CATALYST MAKER]

Originally posted by Sammy123
What does it say in the control panel after you set it to 2x and apply it? Does it say application preference, 2x, 4x, or what?

As I said before, in my case I cannot set to 2x whatsoever regardless of what's set in the panel.....until someone pointed out in a rage3d thread (not just MY problem as you now know) to do a reboot after setting. Bingo 2X FSAA works. Later someone found out a way to avoid rebooting my applying a different game refresh, or something of the sort....but by then I had already rolled back to 3.6

I'd link that thread here but rage3d seems to be in the crapper. Point I'm trying to make I was not alone with this problem.

Maybe when I uninstalled 3.5 something was still left behind, or maybe its finicky ATI drivers. Replies like this "Yes it does. Period. " followed by a rolled eye from a supposed beta tester, ignoring posts from users on their own website reporting quite the opposite, don't give me much faith in ATI's driver progression.

Sammy I see the bug. Thank you for reporting this to me. I have been able to reproduce and will file a bug report into our system.

Now everyone just be friends.

PS. Hope I give you some faith in our driver progression.

[Sammy123]

Now back to the topic at hand.
Can you give me a detailed step by step way of reproducing this bug so I can see for myself if it is a driver bug or your system configuration?

Hi there,

Thanks for you help. I am going to:

1. Uninstall 3.6
2. Install 3.8
3. Pull complete system information using Sandrasoft, and post it for you
4. Set AA slider settings to 2x, 4x, and 6x FSAA and post what control panel reports
5. Post screenshots of FS2004 in 2x, 4x, and 6x FSAA

[Sammy123]

Sammy I see the bug. Thank you for reporting this to me. I have been able to reproduce and will file a bug report into our system.

Now everyone just be friends.

PS. Hope I give you some faith in our driver progression.

Wow, thanks. So I guess I shouldn't go through all that trouble? ;)

[CATALYST MAKER]

No you dont need to do any more. I see the problem and will get it fixed for you.

[Kombatant]

Originally posted by Sammy123
Maybe when I uninstalled 3.5 something was still left behind, or maybe its finicky ATI drivers. Replies like this "Yes it does. Period. " followed by a rolled eye from a supposed beta tester, ignoring posts from users on their own website reporting quite the opposite, don't give me much faith in ATI's driver progression.

Well, the rolleyes were to show you how absolute you were in your previous post. I was just repeating what you said, it was your phrase, not mine. So what you said really takes aim back at you.

The point is this. Just because you have a problem does not mean it is universal. I do not have it, so I did not report anything. Many others do not have it as well. Some people apparently do. Over at Rage3D (that worthless website of mine) we ignore noone's problem. We don't tolerate personal attacks, rude posts and trolling though. And as far as I know, neither do the mods here or anywhere.

Bottom line. It would be nice if you apologized for that uncalled-for attack earlier. I never called you anything.

[saturnotaku]

Originally posted by Sotos
He\she didn't talk about you but about Kombatant

Actually, he was quoting me else I wouldn't have bothered.

Back on-topic - thanks for the report CM. In what way are we going to see a fix? Completely new driver set or are we looking at a hotfix here?

[Sammy123]

Well, the rolleyes were to show you how absolute you were in your previous post. I was just repeating what you said, it was your phrase, not mine. So what you said really takes aim back at you.

The point is this. Just because you have a problem does not mean it is universal. I do not have it, so I did not report anything. Many others do not have it as well. Some people apparently do. Over at Rage3D (that worthless website of mine) we ignore noone's problem. We don't tolerate personal attacks, rude posts and trolling though. And as far as I know, neither do the mods here or anywhere.

Bottom line. It would be nice if you apologized for that uncalled-for attack earlier. I never called you anything.

Apologize for calling you an idiot? OK....you're not an idiot. I take that back. What about my retribution......you know where everybody here basically crucified and faulted everything on me, until it happened to be reproduced by CAT maker?

What prompted me to make such a remark was your reply, considering you beta tested the drivers. Even after I described my problem in detail, you offered no help other than a coy remark. It works for you, so therefore nothing must be wrong. Imagine if every game and software developer had that same mentality? It works for them on their computers.....the hell with what everyone else says. There would be no patches or updates!

Anyways, thanks for any help I received here. No hard feelings!

[The Baron]

hmmm, I'm more curious as to whether it's a bug in the control panel or the drivers...

[Sotos]

Originally posted by The Baron
hmmm, I'm more curious as to whether it's a bug in the control panel or the drivers...

It seems to do with the new Control panel (another reason that i prefered the old one which except of it's simplicity it seems that was more stable from the new one)

OR
maybe is the drivers and the panels problem

[slickfloater]

I just got a AIW RAdeon 9800 SE and it crashed big time with the drivers
that came with the CD, my computer wouldn't boot into windows. I downloaded the catalyst 3.8 drivers and the reference drivers and the reference drivers crashed out with a "cannot find device" "and install default VGA driver" even when I had the most basic microsoft VGA driver loaded. I had to go into safe mode and kill any reference to ATI drivers in the registry and delete all ATI drivers in the windows/system directory (although in retrospect probably not necessary) and delete temp folders and installation directories and then reinstall the catalyst 3.8 drivers and finally my computer would boot into windows after shutdown after about 7 hrs of trying to figure out what went wrong and contacting ATI support who thoughtfully suggested I delete the all temp and install directories.

I'm not very happy that the ATI drivers are so finicky in the install process and no driver just cause my machine to hang like this and require me to go into safe mode.

But anyway, now that I got it to work properly it's a very high performing card. Nice technology ATI, not so good drivers.

I also noticed that the ATI image quality is substantially improved from my
Geforce 3 and I have a question. Do the RAdeon 9800/Cat 3.8 force FSAA 2x mode in all applications or can it be turned off? Honestly, it seems that FSAA 2x mode seems to be on even when I set it to application in the control panel, either that or ATI's image quality is just that much better than the old Geforce 3. :D Btw, I'm ex-nvidia now, I've gone over to the other side after having used a Geforce SDR and Geforce 3 so I'm new to this ATI scene.

[Rogozhin]

The AIWs are more difficult to setup but not anymore so that nvidia's vivo-remote box cards (i've run a g4 with their tvbox and it was also a biitch), but I now run the tv wonder PRO with my 9800pro and it's golden ;)

rogo

[ChrisW]

Originally posted by StealthHawk
Something missing from that OGL Radlinker screenshot is the ability to force tripple buffer! (Long live tripple buffering)
Yep, that setting was released after I stopped developing RadLinker. Maybe I'll continue developing it after I break down and buy a new card as my old AIW Radeon 7200 makes it very difficult/impossible to test the settings on the latest 9xxx cards. I'm surprised I've been able to support so many cards to date as most of the code is just theoretical from my point of view.