Anyway, I noticed problems with newer cards like Geforce4MX440 in Unreal Tournament, both in OpenGL and in D3d, although the errors were not quite of the same nature.

I remember watching "Phobos" on a Geforce, maximum details, and what was strange in the overall look, was a flickering of textures (multitexturing didn't work as it should, and the back texture was shown on one half of the texture rectangle (/*), while the other texture was on the other side (*/), when they should be seen one completely over the otherone).

On ATI, this problem is still visible, but a bit more hard. The more noticeable thing is that texture are having placing problems. I remeber seeing one of my colegues trying all the texture placing (origin, through the drivers), but still the result was not satisfactory.

Also, I remeber the fact that on other games (such as NFS), there is an even stranger effect when activating FSAA, since the texture placing problems tend to increase in strength.

Texture placing problems happend on both Nvidia and ATI graphics cards, more or less, depending on the game and drivers.

As a funny thing, I remembered runing a larger number of games on a Banshee (from NFS2SE, to Quake3, Unreal Tournament, Emperor:Battle for Dune.., Max Payne, Serious Sam, and I never noticed texture placing problems on OpenGL, Direct3D, Glide. Also, no multi-texturing problems (I know that the card has one TMU, but errors can still appear if something is not well handled). The only problem s that did appear were that the game was too slow, or didn't start at all, or it showed Z-buffering problems, since it was using 24bit Z-buffer (a Nascar game I think).

Still amazing that the Voodoo cards, even if they are old, are still capable of showing a surprisingly variate number of games very well...

The truth for the majority, is, that the texture placing and the multitexturing problems are harder to notice, and most of the time, why bother or even notice them when you are palying the game you like very much, and it goes as fast as you like...

That's very strange, since I use Win98SE myself (?)

Anyway, as said, I know the 3dfx Drivers are indeed different (Win9x vs. Win2k/XP), but still I reckoned it should be possible.

And for other Cards, I never heard of such a restriction (S3TC and OpenGL work OS independent after all).

If what you said was correct, I shouldn't be seeing S3TC Textures here

I don't have time right now, but I might try to sqeeze a test in next week (I still have a Voodoo4, Radeon 7500 and a Kyro2 I could test under Win98 )

Unfortunately, I don't have WinME

I have windows ME that I could easily set up on something. I haven't read the entire thread, just browsed it, so what are the requirements for the S3TC thing, i.e.  video card and processor (I need to know if I can get away with a PII 350 because I don't want ME back in this box). Also, I have the following cards: Voodoo Rush, V5 5500 AGP, GeForce2 (32mb AGP), and an ATI Xpert 128 (8mb PCI), and of course some stupid integrated Intel video. Will any of these work? If so which one will work best? I am currently in the process of rebuilding the PII, so it's no big deal to switch stuff around a little.

Alright, before swapping or testing any Cards, I first off ran the RealTech OpenGL Extensions Viewer V2.05 .

I ran it on the following Cards :






PS. It was interesting to see that ATI even implemented some proprietary NVidia OpenGL extensions






Otherwise, interesting to see that even with the latest Driver available, the card is not even 100% OpenGL 1.2 compilant.
Looks like they settled with what is most needed for Games here (actually not unlike 3dfx at its time).






While the last 3dfx Driver (using the .0761 Win9x OpenGL ICD, 21 Nov 2000) has S3TC support within its Extensions, absolutely no Texture Compression was listed under Cababilities, indicating that there's something wrong with the implementation.

So if S3TC doesn't work here, it would not surprise me.






As the AmigaMerlin 2.9 Driver is using the 3dfx .0761 Win2k OpenGL ICD (16 Jan 2001), S3TC support seems fully and correctly implemented here, appearing both under Capabilities and Extensions.

That would explain, why (so far) Users with Win2k reported they were able to run UT with S3TC enabled, while Win9x Users (using reference Drivers) were not able to succeed in doing so.

Still, haven't done testing yet, and also haven't swapped the Kyro2 for testing.



But already, I should seem clear that Win9x (including WinME) should not have anything inherent that would block S3TC OpenGL Extensions. If it is present, it should work

well, i suppose it's good that you figured that out, cause I can't find CD 2 

For anyone looking for the UT S3TC 2nd CD: Nightstormer from x3dfx has uploaded it for download...

Get it here...

Hello IG88!

Just some tips for ya'...

1. Check for 'stray' opengl32.dll files in your UT system folder - delete them if you find any (this drove me NUTS for ages)

2. The current OGL renderer works fine with Radeon cards! (see Falcon's ealier post for the link...)

Hey dborca!

Another EVIL DEAD fan!

GROOVY! 8)

(for all those who don't know, the quote dborca used is from the LASERDISC version of Army of Darkness - the same scene is DIFFERENT on the DVD version!)

L8R DUDES! 8)