Author Topic: [ff7pc] Hidden AA modes in ForceWare 52.16 (Read 14015 times)

halohalo · « **on:** 2003-11-25 14:52:25 »

52.16 has poor compatibility with fx5600. However, with correct AA mode, 52.16 works well with gf4mx and gf4ti.

Install RivaTuner v2.0 RC 14.1, then use MS's NOTEPAD to edit RivaTuner.cfg.

Open RivaTuner.cfg, then find out:

[ForceWareFSAAModes]
FSAAMode0E=2x
FSAAMode0F=Quincunx
Required0F=170h,18Fh,200h,
FSAAMode10=4x
FSAAMode13=4xS
Required13=170h,18Fh,200h,
FSAAMode17=6x
Required17=200h,
FSAAMode19=8x
Required19=200h,
FSAAMode1A=16x
Required1A=308h,30Fh,338h,33Fh

There are 7 AA modes in 52.16 by default. Unfortunately, they are not compatible with FF7pc. So I have to add new AA modes. According to my test, there are four AA modes compatible with FF7pc. They are:

FSAAMode05=ff7_5
FSAAMode06=ff7_6
FSAAMode0C=ff7_c
FSAAMode0D=ff7_d

("ff7_?" is the name I make up for new AA mode)

Copy these command lines to RivaTuner.cfg and save it. Just like:

[ForceWareFSAAModes]
FSAAMode05=ff7_5
FSAAMode06=ff7_6
FSAAMode0C=ff7_c
FSAAMode0D=ff7_d
FSAAMode0E=2x
FSAAMode0F=Quincunx
Required0F=170h,18Fh,200h,
FSAAMode10=4x
FSAAMode13=4xS
Required13=170h,18Fh,200h,
FSAAMode17=6x
Required17=200h,
FSAAMode19=8x
Required19=200h,
FSAAMode1A=16x
Required1A=308h,30Fh,338h,33Fh

Then choose new AA mode with RivaTuner. And enjoy the game

Bluetank · « **Reply #1 on:** 2003-12-04 01:35:26 »

Does it look good on Final Fantasy VIII too?

halohalo · « **Reply #2 on:** 2003-12-04 11:01:20 »

It also looks good on FF8pc. Besides, I think it should work well on Resident Evil 1~3.

Bluetank · « **Reply #3 on:** 2003-12-04 13:53:34 »

Hmm.... is it that when i change the settings i need to restart the computer?

halohalo · « **Reply #4 on:** 2003-12-04 15:13:24 »

You don't have to restart the computer. If you changed important settings, RivaTuner will remind you.

Bluetank · « **Reply #5 on:** 2003-12-11 17:29:57 »

forceware 53.03 is out... XD

halohalo · « **Reply #6 on:** 2003-12-11 19:23:31 »

Quote from: Bluetank

forceware 53.03 is out... XD

Well... these hidden AA modes still work in 53.04.

But 53.04 doesn't solve the transparency problem on fx5600.
(I guess we have to wait for 6x.xx

)

Bluetank · « **Reply #7 on:** 2003-12-12 00:36:43 »

yea lets just have to wait...

but have rivatuner update for 53.03? Because after i installed the drivers rivatuner tells me that rivatuner has not upgraded for the available forceware or something near it... :isee:

halohalo · « **Reply #8 on:** 2003-12-12 11:01:53 »

Although 53.04 is unsupported, hidden AA modes still work without problem. So it is not necessary worrying about unsupported drivers.
--------------------

new RivaTuner v2.0 rc14.2 is out (53.04 is supported). And it adds 4 AA modes: 2x1, 1x2, 2x2, 4x 9-tap

[ForceWareFSAAModes]
FSAAMode01=2 x 1
Required01=170h,18Fh,200h,
FSAAMode02=1 x 2
Required02=170h,18Fh,200h,
FSAAMode05=2 x 2
Required05=200h,
FSAAMode0E=2x
FSAAMode0F=Quincunx
Required0F=170h,18Fh,200h,
FSAAMode10=4x
FSAAMode12=4x 9-tap
Required12=170h,18Fh,200h,
FSAAMode13=4xS
Required13=170h,18Fh,200h,
FSAAMode17=6x
Required17=200h,
FSAAMode19=8x
Required19=200h,
FSAAMode1A=16x
Required1A=308h,30Fh,338h,33Fh

I think nv20 (or above) should be ok with new RivaTuner. But I need to test nv18 with new RT and 53.04. The problem is:

FSAAMode05=2 x 2
Required05=200h,

"200h" means nv20 (or above), so nv17 or nv18 may not be able to use mode05.

ragnarok13 · « **Reply #9 on:** 2003-12-14 09:28:13 »

I've a question about ALL of these AA modes in FF7: does any of them NOT screw up the backgrounds?

halohalo · « **Reply #10 on:** 2003-12-14 10:47:07 »

If you use nv17 (or above), fsaamode05/06/0C/0D should be ok with FF7pc.

Keseph · « **Reply #11 on:** 2004-01-01 06:41:57 »

Hmmm... when I pop those lines in and use rivatuner to force any of them, I get really weird effects (see pictures) but the text looks clean, unlike any of the other AA modes.
Picture 1
Picture 2
Picture 3

Bluetank · « **Reply #12 on:** 2004-01-01 08:34:06 »

sorry don't know whats ur problem, cause i never had any problem with those AA modes.

Unless is the problem of ur drivers or u r not using a NVIDIA driver...

Skillster/RedSarg99 · « **Reply #13 on:** 2004-01-01 10:44:10 »

your palleted texture settings are wrong
check your have 8bit palleted textures enabled

Keseph · « **Reply #14 on:** 2004-01-01 14:19:23 »

Ah, it looks much better now, except for this. It only has this in a few spots, though...

I'm noticing that the 5 and 6 AA options seem to cause the game to crunch the hard drive during scene transitions much more than before...
The C and D options seem to cause the game to run at a lower fps...
(In case it matters, I'm running a 2g Athlon XP, GeF FX 5200U, and 1gb DDR)

PS.
Looking at cosmo canyon, can someone do me the favor of a quick couple-minute play-through of Boog's astronomy event, as my game crashes during the first movie, where Aerith comments on the shooting star...

Skillster/RedSarg99 · « **Reply #15 on:** 2004-01-01 22:36:40 »

haha, ur gfc is quite low speed for doing that much FSAA mate

Bluetank · « **Reply #16 on:** 2004-01-02 15:12:45 »

anyway halohalo,

i added this

Code: [Select]

ForceWareFSAAModes] 
FSAAMode05=ff7_5 
FSAAMode06=ff7_6 
FSAAMode0C=ff7_c 
FSAAMode0D=ff7_d 
FSAAMode0E=2x 
FSAAMode0F=Quincunx 
Required0F=170h,18Fh,200h, 
FSAAMode10=4x 
FSAAMode13=4xS 
Required13=170h,18Fh,200h, 
FSAAMode17=6x 
Required17=200h, 
FSAAMode19=8x 
Required19=200h, 
FSAAMode1A=16x 
Required1A=308h,30Fh,338h,33Fh

to the new RivaTuner, but i was not able to use ff7_5 which previously i can. This is my code in RivaTuner

Code: [Select]

ForceWareFSAAModes] 

FSAAMode01=2 x 1 
Required01=170h,18Fh,200h, 
FSAAMode02=1 x 2 
Required02=170h,18Fh,200h, 
FSAAMode05=2 x 2 
Required05=200h, 
FSAAMode05=ff7_5 
FSAAMode06=ff7_6 
FSAAMode0C=ff7_c 
FSAAMode0D=ff7_d
FSAAMode0E=2x 
FSAAMode0F=Quincunx 
Required0F=170h,18Fh,200h, 
FSAAMode10=4x 
FSAAMode12=4x 9-tap 
Required12=170h,18Fh,200h, 
FSAAMode13=4xS 
Required13=170h,18Fh,200h, 
FSAAMode17=6x 
Required17=200h, 
FSAAMode19=8x 
Required19=200h, 
FSAAMode1A=16x 
Required1A=308h,30Fh,338h,33Fh

can u tell me if there is anything wrong?

halohalo · « **Reply #17 on:** 2004-01-13 15:57:01 »

The command line "Required05=200h" will set a limit. That means you will need nv20 (gf3) or above to run mode05. And nv17/18 will be blocked by the command line. Therefore, you need to remove the command line, and nv17/18 should be able to run mode05 without problem.

Besides, RivaTuner RC 14.2 (or above) already supports mode05. (FSAAMode05=2 x 2)

So you can edit RivaTuner.cfg like this way:

[ForceWareFSAAModes]
FSAAMode01=2 x 1
Required01=170h,18Fh,200h,
FSAAMode02=1 x 2
Required02=170h,18Fh,200h,
FSAAMode05=2 x 2
FSAAMode06=ff06
FSAAMode0C=ff0c
FSAAMode0D=ff0d
FSAAMode0E=2x
FSAAMode0F=Quincunx
Required0F=170h,18Fh,200h,
FSAAMode10=4x
FSAAMode12=4x 9-tap
Required12=170h,18Fh,200h,
FSAAMode13=4xS
Required13=170h,18Fh,200h,
FSAAMode17=6x
Required17=200h,
FSAAMode19=8x
Required19=200h,
FSAAMode1A=16x
Required1A=308h,30Fh,338h,33Fh

halohalo · « **Reply #18 on:** 2004-01-15 07:21:58 »

Quote from: Keseph

Ah, it looks much better now, except for this. It only has this in a few spots, though...

ForceWare 5x.xx has poor compatibility with fx series (I've tesed fx5600 and fx5900xt) in ff7pc. So you may want to use old Detonator 4x.xx. It should solve the problem.