Which is the better approach: using the drivers provided by the manufacturer (MSI, Gigabyte, etc) or those provided by ATI? The question does not relate laptop users.

What value should I use for useGTF registry key? The latest SFFT driver .inf sets it to 0. Should I leave it at 0 or change it to 1? Is there any difference at all?

Recenlty I have purchased a new CRT monitor and I noticed that Carmagedddon 2 looks extremely bright (the game uses Glide, 640x480 resolution only). This wasn't the case with my previous monitor, and I also didn't increase voodoo gamma settings (actually I lowered it even more). The problem doesn't happen in other games, right now I tested CS 1.6 and it looks great, no problem at all. Non-glide games and desktop look fine as well. Any ideas on why this is happening with Carma 2?

I am using Voodoo3 2000 PCI + SFFT on XP Pro SP2.

QuoteOriginally posted by in3d

QuoteOriginally posted by Ree

...I have found out that Disciples II is unstable in both D3D normal and compatibility mode...

I suppose that you used 3dfxTools 2.6.1.110 with A35,36&37 for this kind of manipulations

No. Disciples 2 can be run in D3D or software mode. The game has actually 2 D3D modes (compatibilty and normal). You choose which one you want by using Disciples 2 config editor.

From my experience both D3D modes are unstable (random hangs) and display random artifacts/glitches/overlappings in-game.

QuoteOriginally posted by in3d

QuoteOriginally posted by Ree

Actually, after some testing, I have found out that Disciples II is unstable in both D3D normal and compatibility mode. It hangs randomly, and there are quite a few graphic glitches in-game. This problem occurs with all latest driver versions (A35, A36, A37).

Have you Tried it with Amigamerlin 3.1 R11

No I have not, but SFFT shoud work as well, it's D3D targeted after all.

Actually, after some testing, I have found out that Disciples II is unstable in both D3D normal and compatibility mode. It hangs randomly, and there are quite a few graphic glitches in-game. This problem occurs with all latest driver versions (A35, A36, A37).

Ok got it, I've always been installing drivers by using the advanced installation and indicating the folder containing the drivers.

There's no such option on Win XP SP2 (or I can't find it). You can only update, uninstall and roll back drivers.

I'd like to report a problem about Disciples 2 (D3D mode). Occasional artifacts appear throughout the game, and the game crashed to me after playing for about 15 mins. This is what windows event log says:

------------
The driver 3dfxvs for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.
------------
Data (Words)
0000: 00000000 004e0003 00000000 c004006c
0010: 00000000 00000000 00000000 00000000
0020: 00000000 00000000
------------

I have a V3 2000 with Alpha 35, and I see A36 is out already. I will probably have to update but somehow I doubt this will solve the problem since it hasn't been reported yet.

EDIT: I tried updating to Alpha 36 through device manager, but Windows tells me it can't find a better driver than currently installed (Alpha 35) and doesn't install Alpha 36 from the dir specified. Any way to fix this?

EDIT2: The crash problem seems to disappear if Disciples 2 'D3D compatibilty mode' is used. However, the random artifacts in-game are still there which is pretty disturbing.

Just tried driver cleaner. Actually it's pretty useless. It only deleted a few dlls that I deleted mysellf when uninstalling Amiga and installing SFFT. It still left lots of 3dfx 'traces' in my registry which I removed myself before, during the manual uninstallation. Btw how useless is that it reports 3dfxvs.dll and 3dfxvsm.sys as deleted files when those CANNOT be deleted, they get loaded immediately after they're deleted. Pretty useless indeed.

And yes, in new hardware found windows still indicates it as Amigasport...

No way to get rid of amiga I guess...

Ah that's how it is. Fine, now I see there's now difference.

Actually, when I got the '3dfxICD.dll not found' during SFFT installation, I also got a few more 'dll  not found' errors. I was suggested to 'fake' 3dfxICD.dll and give windows mesafx opengl32.dll renamed to 3dfxICD.dll. Well I did that, and the other dlls I simply skipped. The installation otherwise went well, also no module register errors while installing 3dfx tools + I got finally the Video gamma controlls in 3dfx tools. So it seems like SFFT installed quite well, even though windows still displays the card as Amigasport 3.0...

Actually I will try once more, this time with driver cleaner the way you suggested, everything from the start, and see how it goes.

Will report soon

Maybe we misunderstood each other...

What I found a bit strange is that you suggest cleaning the junk with driver cleaner BEFORE removing the driver via the device manager. I always thought it was the other way round - first remove the driver, then clean the junk with driver cleaner. Which is the correct order then? Just wanted to confirm.

Mikulaish, are you sure I need to run Driver Cleaner BEFORE removing my voodoo from device manager?

Yeah, I thought so as well. Anyway I tried installing SFFT, and while installing the driver windows says it can't find 3dfxICD.dll. SFFT driver package indeed doesn't contain this file. What do I do?

All right.

Actually I have got into a little problem. Right now I was doing a clean driver reinstall (from Amiga to SFFT). I deleted all relevant registry entries as well as files in Windows directories and then rebooted. However, after reboot (256 color mode, seems normal) windows displays 'found new hardware' dialog box, however it says it's for Amigasport! That's weird because I deleted all relevant .infs. The Amigasport driver install package contains voodoo.inf, but on my system it's not present, yet windows somehow still manages to find Amigasport hardware. How come? I need to remove this. Any ideas?