SFFT alpha drivers - V3/4/5 - Join to Testing

[SuperFurryFurryThing]

FBS One thing that did occur to me, the changes in memory architecture when you switch from Single Chip or Fastest to 2 Smaple AA or 4 Sample AA only take effect when the screen resolution changes. This is also true of the changes caused by running Set3Tile.exe and Set4Tile.exe. If your desktop resolution is the same as the game resolution i.e. 1024 * 768 * 32 in both cases, then you need to reboot before the changes will take effect. You may need to reboot the PC before testing a particular configuration setting.

SFFT

[FBS]

Ok I set up 3 tile and rebooted. I can now load the plane textures in 2 sample AA. The problem is that I loose the terrain textures, they become blured. I also feel a good speed increase. As for the kneeboard no change. I don't have much time left but tomorow I will check how it reacts in fast and single chip mode,
FBS

[FBS]

I ran the 3tile and in all modes the aircraft textures show corectly except that it causes the terrain and or scenery to become blury. The kneeboard only functions (opens correctly) when I am in single chip. as for 2AA and fast I get a black window and a heavy reduction in FPS.

[LogicalMadness]

SFFT, is there any chance of adding the same Voodoo5 6000 code to your drivers as those in the Amigamerlin D3D drivers?

-LM

[Amigamerlin]

Originally posted by LogicalMadness

SFFT, is there any chance of adding the same Voodoo5 6000 code to your drivers as those in the Amigamerlin D3D drivers?

-LM

Ciao Logical,
I can answers you .
Thanks to Hank, SFFT asap will receive a voodoo5 6000 for developing purpose, then He can start coding for 6k too having a better voodoo5 6k compatibility.

Anyway he said me that he added to his code all good thing of Amigamerlin 3.0 code (he has our source code )then is really strange that actually the "new code" is not able to support voodoo5 6k.

Anyway As I said, He will be able to code for 6k too asap then he can fix all the problems.

Kudos must go to Hank for this..

Bye to all

[Voodoo5]

Great to hear about Hank as he has not posted here for quite some time now

[SuperFurryFurryThing]

FPS have you tried running the game in 1024 * 768 * 16 instead of 32 bit, 16 bit textures take up half the memory of 32 bit ones. It might be worth a go to see what difference it makes.

SFFT

[FBS]

No I have not tried at 16 bit, I will give it a try later on tonight.

[ggab]

really good news!

SFFT, are u european / country?

again, thanks to all 3'zone community (in special, the coders )

[FBS]

Here is what I have so far. With 3tile at 16 bit all the texture display correctly, that is to say aircraft and terrain/scenery. This has been tried in Fast, 2 Sample and single chip. I have some coruption in my virtual cockpit view. (see piture below)

Download Attachment: VC.jpg
53.96 KB

I did not have time to check more conditions out but I did quickly try  setting it back to 4 tile and the terrain textures are blury in 2 sample AA. Of course these test are all done at 16 bit.
FBS

[FBS]

I have checked out 4tile 16bit with fast ans single chip. The aircraft textures allways show up correctly. The terrain/scenery textures turn blurry. There is a slight delay in 2AA and single chip before the texture blurr out (about 5 seconds when playing with different views). In fast pref. the textures blurr instantly.

[SuperFurryFurryThing]

It seems like the more texture memory that you have available the better the game runs, have you tried changing some of the configuration options. if compressed textures are not being used enabling them should reduce the amount of texture memory being used. I susect that you would be able to find out the meaning of the configuration setting on a microsoft site somewhere.

SFFT

[chatocl]

SFFT, I check the Alpha13 vs 12 on my voodoo3 in UnrealTournament (D3D mode) and the fps remains almost the same.

I also try Halo with the modified config, first some warnings (one of them about my video ram 16MB vs 32MB required) and at the end says a "problem ocurred initializing d3d... hardware aceleration maybe disabled....." I think that no hope for 16MB with Halo....

Anyway congratualtions SFFT your driver is far away the fastest .

Chatocl

[zandro]

chatocl try to set the desktop resolution to 640x480 16bit
and then run the try run the game, it might just work

[napalm3dfx]

About UT2003 & Voodoo3,

I have tried this game under D3D (Alpha SFFT 13 Driver V3), and It works perfectly, but I have seen that the aim point or bead is blurred and almost imperceptible at first sight!

ps. Excellent Driver, SFFT!
(sorry for my bad English)

Take Care,
napalm3Dfx