PDA

View Full Version : FSAA Not Working Anymore with Catalyst 7.4?


cherbert
04-20-07, 11:05 AM
I just installed 7.4 over 7.2. Before I had no problems forcing FSAA and AF. Now with 7.4 It appears to not be working.

Is anyone else experiencing this?

SteamWake
04-20-07, 11:30 AM
Fortunaly I decided to wait a few days to update to see what the fallout would be.

Wish I could help you.

Did you check the settings with the console ?

Chances are the update forced everything back to their defaults.

cherbert
04-20-07, 11:39 AM
Fortunaly I decided to wait a few days to update to see what the fallout would be.

Wish I could help you.

Did you check the settings with the console ?

Chances are the update forced everything back to their defaults.

Yes I checked all that. Tried turning off AF and reducing FSAA but no joy.

I am currently downloading the Omega Drivers to give them a go.

Next time I'll stick with your way of thinking and wait for the fallout ! ;-)

basilio
04-20-07, 12:15 PM
OOOOHHHHHH!!!!
I was planning to install the new drivers this evening....will wait.
Please keep up posted about this issue.

clayman
04-20-07, 12:33 PM
cherbert ... I loaded SH4 patched to my ATI (X850XT) box and AA and AF not working here. Let us know if the Omega's work or I'll load the 7.2. I had been running the 6.8's before.

cherbert
04-20-07, 12:40 PM
Latest Omegas (based on 7.1) working great!

6 x FSAA and 4 x AF


Beware the Catalyst 7.4 drivers! Not sure if this is now a problem for Ubi to sort or an ATI problem?


P.S using Radeon X1950pro 512mb (AGP)

Snowman999
04-20-07, 03:13 PM
Beware the Catalyst 7.4 drivers! Not sure if this is now a problem for Ubi to sort or an ATI problem?


It's physically impossible for Ubi to have coded to drivers just released this week. Right?

Fish40
04-20-07, 04:22 PM
FSAA and AF both working useing Cat. 7.3. Don't know what happened with 7.4. At this point the 7.3's work fine with all my other sims, so until ATI decides to release a driver that cures the Sun bloom (or lack of) issue, I'll stick with them.

cherbert
04-20-07, 08:11 PM
Beware the Catalyst 7.4 drivers! Not sure if this is now a problem for Ubi to sort or an ATI problem?


It's physically impossible for Ubi to have coded to drivers just released this week. Right?

And your point is?

Do you think we should expect to have to wait for them to release a new patch to fix FSAA overide everytime ATI releases a new driver set?

I just don't understand why the devs can't give us an FSAA and AF setting in the options like the most other game do!

bunkerratt
04-20-07, 08:30 PM
efore we start, few things:

1. DO NOT use the automatic clocking things in ATT and ATi Tool, they do NOT work with X1k series cards.

2a. Disabling the services put the card fully into your hands, fan speeds, voltages, etc, so you must watch what is happening and read the guide carefully and ask if your not sure (that will help me to improve the guide).
2b. Automatic clock changes are also removed when the services are disabled, both programs have options so they can detect when a 3D app starts and closes, and then loads the selected profile by you when they detect it. Or you can set them yourself.

3. With X1k series cards, even with the services disabled there can be clock changes without your input, like starting a game or a video which can lead to crashes when the drivers force standard 2D clock speeds, there is no fix as of yet. (New ATi Tray Tools fixes this issue)

4. You MUST set clocks before starting the client or a game or something 3D, as the clock change corrupts the data and of course it crashes http://forums.ubi.com/groupee_common/emoticons/icon_wink.gif

5. On X1900 cards I think that mem bandwidth is more helpful than GPU mhz at during points. 625-650mhz core needs about 800-825mhz of mem speed to not have a big bottleneck, but thats only in 3D work, in this it may be different.

6. These programs do NOT relax timings, the only time they are relaxed is when using the CCC method when the ATi services are running. How I do it does not use CCC or the services. (Now, using the new way of overclocking it does when using driver level overclocking in ATi Tray Tools - If the machine is on 24.7 without you using it use low level overclocking.)



Software
ATi Tool - Over clocking tool - although now not the one i’d use.
ATi Tray Tools - Over clocking tool. But has profiles for each program so you can have different clocks, quality settings etc on each one. Only install if your not using CCC.

Disclaimer: Do so at your OWN RISK blah blah.

First you must disable the two ATi services.

Start --> Run --> Type "services.msc" then disable both ATi services, the restart. Note this will stop the automatic change of clocks in 3D apps, but the programs below can do it for you.

ATi Tray Tools 3D
So here we go. First in the settings page make ATT start at Windows start. Plus bare in mind this part of the guide is based on a HiS IceQ X1900XT-X.

Then go to the Hardware panel and select over clocking settings.

You should be confronted with 3 tabs, ‘Over clocking’, ‘Fan’ and ‘Voltages’.

From the drop down menu on the 'Overclocking' tab, select "Driver level" over clocking, this will stop any clock changes when a video is started.

First we first want to make a 2D profile, so that when your not running the client you can set 2D clocks (like that will ever happen http://forums.ubi.com/groupee_common/emoticons/icon_razz.gif).

I have them set at the lowest the two sliders will go. So do that and then apply. Then press save as and save it as 2D. Tick load profile at start-up.
Next onto the ‘Fan’ tab, here you can set whatever you like but be reasonable. Don’t expect it to survive if you put it at 0 or 10% because sometimes 3D mode doesn’t kick in and it still can get very very hot even with a slow fan speed. Tick ‘Include In Profile’. Once you have set fan speeds, Apply and save as to the 2D profile. Now go to the ‘Voltage’ tab, here I have it set at 1.000V Core and 1.950V memory. But work your way down from the settings you find there. Most X1900s will do the same voltages as mine. Tick ‘Include In Profile’, apply and save as to the 2D profile.

Now, here you can test if you so wish, few loops of 3D Mark or just leave it. If the screen locks and the PC is still going, E.g. sounds then core voltage is too low. If you get artifacts/tears on the screen then memory voltage is too low. This applies to all clocking.


Now, Stock 3D!!

We have to work our way back from Voltages to clocks now, because if you set clocks with low voltage it will crash http://forums.ubi.com/groupee_common/emoticons/icon_wink.gif. So, set:

X1800 series: 1.425/2.089V
X1900 series: 1.4/2.089V
X1950 series: 1.4/2.089V

Apply and save as to a new profile called ‘Stock 3D’. Now, back to fan speeds, set your 3D fan speeds, apply and save to the ‘3D stock’ profile. Then onto the clocks page. Set them as follows:

X1800XL: 500/500
X1800XT: 625/750
X1800 GTO: 500/500
X1800 Crossfire Master Card: 625/750
X1900XT 512Mb: 625/725
X1900XT Crossfire Master Card: 625/725
X1900XTX: 650/775
X1950XT-X: 650/1000 (X1950 support is not yet avalible)

Apply and save to the 3D profile. Testing is tricky, 99% of the time it should be fine, but if you would like to test it by playing a game for a few hours then you may.


Over clocking 3D:

I don't think while the software is being BETA tested that you should over clock, but X1900XTs will do X1900XTX speeds easily in most cases. If you wish to over clock here is what you do:

I would work on core first, as the X1900 and possibly the X1800 series have a problem going over the CCC max of 690mhz on the core. Even with the services disabled. So work your way up to 690mhz, 10 mzh at a time. Most cards will do 690 on stock volts.

Once that is stable for 1 hour of gaming/2005/whatever. You can start on memory. Same principal as before, 10mhz at a time increasing mem voltage if required. Don’t go passed 2.15V atm as it crashes with the current version.

Finally, go to the Overdrive 3 page from the hardware menu and make sure the "apply at startup" box is NOT checked



ATi Tool is the same, new profile, set clocks, then fan then voltages when setting 2D and then volts, fan then clocks when setting 3D. X1950 users can use ATi Tool to over clock/

USE THE LATEST VERSION OF THE OMEGADRIVERS ...

OS1Mac
04-22-07, 08:57 AM
Nice tutorial, Bunkerratt. Thanks. :up:

And there's no FSAA for me, either, with ATI Catalyst 7.4. I also have the same problem in IL-2. ATT solved this problem in both games, but I decided to revert back to Catatyst 7.3 (it was working fine anyway).

JSF
04-24-07, 01:01 PM
What is FSAA?

Seaman_Hornsby
04-24-07, 01:41 PM
What is FSAA?

FSAA is Full-Screen Anti-Aliasing. It's a function of your graphics card that smooths out "jaggies" or jagged lines formed by edges in a 3D image. An antenna wire on a ship, for example, may look jagged with no FSAA applied, but with it, it will appear to be a smooth line. Makes a game look better, but can make framerate suffer on less-than-top-notch computers.

Soviet_Warlord
04-24-07, 03:23 PM
What is FSAA?
FSAA is Full-Screen Anti-Aliasing. It's a function of your graphics card that smooths out "jaggies" or jagged lines formed by edges in a 3D image. An antenna wire on a ship, for example, may look jagged with no FSAA applied, but with it, it will appear to be a smooth line. Makes a game look better, but can make framerate suffer on less-than-top-notch computers.
FSAA is more commonly reffered to as AA (Anti-Aliasing), since its full-screenyness is implied. However, in SH4 AA can also be interpreted as being "Anti-Aircraft".