MesaFX

[Flash]

I'll try with V5 6K and Opteron 248 tomorrow but i think it will be the same.
BTW here's the log from Doom 3:

Voodoo Using Glide 3.10.00.0658
Voodoo Board: 1/1, Voodoo5 (tm), 2 GPU
Voodoo Memory: FB = 3694592, TM = 2 x 28717056
Voodoo Screen: 640x480:32 RGB, no vertex snapping
Voodoo TMU0 configuration:
Voodoo   00000000-28717040
Mesa: User error: GL_INVALID_VALUE in glTexParameter(param)
Mesa: User error: GL_INVALID_VALUE in glTexParameter(param)
Misc Stats:
 # swap buffer: 5164
Textures Stats:
 Free texture memory on TMU0: 28717040
 Free texture memory on TMU1: 0
 # request to TMM to upload a texture objects: 1246
 # request to TMM to upload a texture objects per swapbuffer: 0.24
 # texture objects uploaded: 1246
 # texture objects uploaded per swapbuffer: 0.24
 # MBs uploaded to texture memory: 14.43
 # MBs uploaded to texture memory per swapbuffer: 0.00
Pixels Stats:
 # pixels processed (minus buffer clears): 7640420
 # pixels not drawn due to chroma key test failure: 0
 # pixels not drawn due to depth test failure: 14314445
 # pixels not drawn due to alpha test failure: 14420947
 # pixels drawn (including buffer clears and LFB writes): 9891105

Looks similar but doom3 is definitely not software rendered - it's too fast for that - 7-30 fps

And Worms - it took about two minutes just to move mouse and close game

[dborca]

Originally posted by Flash

here's the log

Voodoo Using Glide 3.10.00.40404
Voodoo Board: 1/1, Voodoo5 5500 (tm), 2 GPU
Voodoo Memory: FB = 9445376, TM = 2 x 11483136
Voodoo Screen: 1024x768:32 RGB, no vertex snapping

32bpp, that also means 24bits depth and 8bit stencil

cpu vendor: GenuineIntel
MMX cpu detected.
Not testing OS support for SSE, leaving enabled.
SSE cpu detected.
Voodoo TMU0 configuration:
Voodoo   00000000-22966256
Mesa: User error: GL_INVALID_ENUM in glDisable(0x1802)
Mesa: User error: GL_INVALID_ENUM in glDisable(0x1802)

oh boy! now that's nasty. 0x1802 is GL_STENCIL, but it seems you have stencil enabled...

well, i'll try the demo again...

one more thing... can Worms3D run in 16bpp? if so, force MesaFX into 16bpp with MESA_FX_IGNORE_PIXEXT=y, then check the log.

[secretfj]

i just tried the new Glide for my V2 (the one inside "CVG" folder)
and used it with comparison on GLExcess (coz i discovered that i don't have any OpenGL game..)

MAXLOD=11 (actually different value don't give any different)

here is the result:


Image Insert:

192.96 KB

seems the old one is faster than new one..but i know it's just an alpha release, so no need to afraid.

P.S. why in the documentary file, there is no V2 but only Voodoo^2(voodoo square)?
is it mean that i used the wrong Glide file to test so the result is no good?
thanks for your wonderful work Daniel, thanks a lot~~

[dborca]

Originally posted by secretfj

seems the old one is faster than new one..but i know it's just an alpha release, so no need to afraid.

damn, it's not faster, it's WAAAAY faster well, i'll see what i can do to speed it up

P.S. why in the documentary file, there is no V2 but only Voodoo^2(voodoo square)?
is it mean that i used the wrong Glide file to test so the result is no good?
thanks for your wonderful work Daniel, thanks a lot~~

hehe, no, I like Voodoo^2 over Voodoo2. i think i saw that in some 3dfx advertisers. just a matter of taste...

[Flash]

Originally posted by dborcaone more thing... can Worms3D run in 16bpp? if so, force MesaFX into 16bpp with MESA_FX_IGNORE_PIXEXT=y, then check the log.

Nope. Can't. It crashes and it's in the log:
fxMesaCreateContext: ERROR: grSstWinOpen

[JLj]

Some more benchmarks (with a bit more modest hardware)
K6-2 500 mhz, 1 x Voodoo2 8mb, 144mb ram, MesaFX-6.2.0.1.

Open-GL Stars 0.5.0.0520, 800x600, default.

New Glide
Benchmark results:
- Frames rendered : 2000
- Time            : 73.918s
- Average fps     : 27.06


Glide 3.03.00.0670
Benchmark results:
- Frames rendered : 2000
- Time            : 68.652s
- Average fps     : 29.13

[ps47]

@secretfj:
what versions of glide3x did you compare?

[secretfj]

what versions of glide3x did you compare?

for the old Glide it's 3.03.00.0670
SHOULD be 3.03.00.0667
the new one is from dborca

just discovered that, sorry

[ps47]

@secretfj:
can you test the 3.03.00.0667 version as well (you can find it in any mesafx full package)? my voodoo2's arent up and running yet..

[dborca]

i've been thinking about those glide3x dlls...  the difference is way too big, something's fishy there...  can't be the code, perhaps some envvars are interpreted differently (FX_GLIDE_SWAPINTERVAL / FX_GLIDE_SWAPPENDINGCOUNT).  i'll investigate. thanks!

[secretfj]

can you test the 3.03.00.0667 version as well (you can find it in any mesafx full package)?

I am sorry but i discovered that the previous test was done using 3.03.00.0667 instead of 3.03.00.0670

P.S. I tested 3 Glide3x.dlls today
3.03.00.0670 one (included in FV 4.6) just refuse to run and makes the system halt, while the other two do the job.

P.S. some Glide specific results are posted (just some simple findings) into the Voodoo 2 discussion area as i don't want to be off-topic so much

[perer]

What is the difference with the 667 and the Dborca version?
Dborca have you added more compatibility? And because I stil don't have the sources of the FV drivers I want to invest my time in working with glide3x. Maybe I can help you?

[dborca]

Originally posted by perer

What is the difference with the 667 and the Dborca version?
Dborca have you added more compatibility? And because I stil don't have the sources of the FV drivers I want to invest my time in working with glide3x. Maybe I can help you?

the diff? hard to tell...
if you wanna help me, go to
http://sourceforge/projects/glide/
and checkout the "glide-devel-branch"
(exactly, the branch name is "glide-devel-branch").
good luck!

[perer]

If I took the right one, I must now have this glide-devel-branch. I must say the source is quite small. At least al lot smaller than I had expected.

Edit. Is this the one you mean?
$Header: /cvsroot/glide/glide3x/cvg/glide3/src/distate.c,v 1.1.1.1.8.3 2004/03/08 07:42:21 dborca Exp $
** $Log: distate.c,v $
** Revision 1.1.1.1.8.3  2004/03/08 07:42:21  dborca
** Voodoo Rush fixes

[dborca]

it looks like, doesn't it?

small tip: you must checkout TWO modules from "glide-devel-branch". the first module is "glide3x", the second is "swlibs". move swlibs INSIDE the glide3x directory and start compiling.

the complete glide3x+swlibs sourcecode should be at around 40MB (but that's because the demo textures are well over 20MB).

all the branches are buildable, tested and run ok. you get the status in README.2 (readme-too). take your time and do something good with the source. if your patches are worthy and if you make them public, i will make you Glide developer, with read-write CVS access.