QuoteOriginally posted by ps47

..and what about warcraft3? the game runs way more stable with mesafx and looks better as well,but there are still some small texture problems..

yes, i know... i still have to determine if this is driver-related or application-related.

unfortunately, many games provide dual d3d and opengl paths, and the gl path is usually poorly written, or not tested enough. ohwell... this is an old issue:
1) users tend to think d3d is trendy
2) and god forbid game developers create non-trendy applications
3) then, driver developers have to invest more in d3d than in opengl, because it's needed by game developers
4) so, because d3d is usually better, average user thinks d3d is trendy. now we're back to step 1!

quod erat demonstrandum the vicious circle is compete now!

ps: i love carmack for having the balls of doing opengl! carmack rules. and he was "criticized" at beyond3d for being stubborn. oh, and btw, in opengl area, nVidia rulez!

pps: i remember i found this a long time ago...
http://www.azillionmonkeys.com/windoze/OpenGLvsDirect3D.html

QuoteOriginally posted by perer

Did you use the standard Voodoo3 setting in Serious Sam 2? Or did you use your own MesaFX. Because I got blinking wrong sun flares etc, with the Voodoo2 compatibility but with MesaFX there was no problem, and the game ran smooth.

this has little to no relevance. first rule of testing: never change two things at the same time. so basically i changed only one thing: glide3x. the 667 works ok, while the other (sf) doesn't.

and, yes, i was using mesafx, of course. i also tried deleting the entire voodoo section from glsettings and ran in "unknown mode".

QuoteOriginally posted by perer

Well the voodoo2 quality is dreadfull sometimes, thank god I have a monitor wich had the ability brighten up the screen. This really helps.

i doubt it.  methinks the voodoo2 lacks the post-dithering circuitry that was available in voodoo3.  dunno why, as this technique is used in some other ancient cards (like the venerable Matrox Millennium I).

now, onto business... i tested voodoo2 glide3x that is available at sourceforge.  under the same conditions of SWAPPENDINGCOUNT and SWAPINTERVAL it does not perform that bad at all (about 98% of Glide3x 667 in GLExcess).  however, it seems to be buggy, at least in SeriousSam2 (technology test, hi-q mode): the sun's flares are missing or blinking, some of the torches are visible through temple inner walls, etc.

so, perer, since you were so eager-beaver to start voodoo2 development, try and have a look at that.  the most advanced glide3x that i (we) have is in sourceforge now.  i know it would be better to start tweaking 667, but look at napalm d3d section: it started with an older version and now is better than latest official release.  here's your chance to show us what you're made of.

hint: i'd disassemble the 667 dll, isolate the triangle rendering routines and compare them against assembler sources we have in sourceforge. that might or might not be of any help

might be a virus, but i would bet on malware.  either way, no good.  therefore... locked

QuoteOriginally posted by Garth

Hey we're a comunity, you help us with drivers, and we all know where they come from, and we make sure we know who to thank. The day I have to pay, plead, or anything of the sort, to get a single driver i'll change cards and thats it.
If these ppl want to take credit for your work let them be, you get our thanks, not them

thanks for sharing these great ideas with us, genius. now SHUT UP!

QuoteOriginally posted by perer

Yup it does, to bad it doesn't give you more speed.

it suffers from the same defficiency of all SLI-ed Voodoos: TCL.
but in theory, should be more scalable, although i wouldn't know...

QuoteOriginally posted by secretfj

Daniel,
Thanks for your work and i'm looking forward to ur result..

damn, that texture is really big for V2, blurry, too... ok, i need some sleep before i start mixing things again... like nitrite and glycerin (yeah, whatever)! sorry for the unnecessary hassle. anyways, the new extension is there, on the latest RC at my situ.

QuoteP.S. is X24 the one which have a lot of V2 Chips in it and it can use 4X AA?

eheh, close, but no! X24 is simply a V2 SLI in one board. you are talking about the Mercury system, composed of 4(four) X24 boards, coupled with an external moniker to obtain the FSAA effect. in fact i think it was composed of 4(four) X24 derivatives, called 200SBi
http://www.quantum3d.com/press/HTMLarchive/12-4-98b.html
http://digilander.libero.it/F1Land/3dfxarchive/download/media/gallery/quantum3D-mercury-16x3dfxvoodoo2pci-96mb-3.jpg
8-way SLI looks awesome for goold-old voodoo2, eh?

QuoteOriginally posted by secretfj

(the only thing that will fade in under the GL Excess Logo can only be the credit of producer...they just look the same for 6.1.0.9 or pre-release..)

my, that's odd... perhaps it's time to plug back teh X24, then

nope, no idea. mainly because i have no idea how the textures should look like. and yes, the grating stuff may be because of texture compression (although i believe the textures are precompressed, so it's not mesa compression quality to be blamed).

QuoteOriginally posted by FreddyM84

x3dfxgamers.de brought out a new driver yesterday. And they are saying

ahaha... sebastian, you should know better than that

you see people, is THIS attitude that makes good guys go away. i somehow feel there won't be future amigamerlin releases, and mesafx may reach its final public release soon.

@toony5
stencil_wrap was added a while back. the new extension is not present yet, unless i make sure the 6.3 prerelease does not introduce new bugs.
about UT2004, you may be right. i changed the way small textures are processed.

@SHARPSHARK
i used to play Doom3 on Athlon XP 1800+, Voodoo5 6000 2xFSAA. this is roughly equivalent to a 5k5. you should be okay with that cfg... well, not great, but...

QuoteOriginally posted by secretfj

too bad that i still can't find out what's the different by running GLExcess for more than 10 times (i just have time today to do some quick searching, no luck..)

hehe, keep up the good work

QuoteP.S. u've said it's in the last scene, u mean the scene"outro" or "citylight"? i investigated them both but my blurry eye still can't see a thing differnet...

last scene, this means outro. is about the last thing you ever see, before exit. the thing it's rather small and fades in below the big GLEXCESS logo...

QuoteOriginally posted by vykupitel

That is really good to hear that. Will it be available as binary package?

yes, namely tdfx_dri.so! i might release the patch, too... i dunno...

umm.. sorry, haven't got the time to toy with it...

some other news (might or might not be of any interest): the doom3 is tested and works with the TDFX driver, but only with shadows disabled. the build will be out in a few days.

QuoteOriginally posted by TM30

did you see something like this before? are there any infos on a "budget voodoo2"

i am not aware of any...
go here, for starters: http://www.idhw.com/textual/chip/3dfx/chippicture.html