Putas wrote:

Viewtop 3D Vulcan without extra memory and A-Trend Helios 3D 6 MB - strange that the A-Trend seems slower.

Thanks. So both are AT3D models. I wonder if there is someone out there with a Macronix chipset board

But Rush is not such speedster, timedemo framerates with Vulcan: 320x240 - 21.5 400x300 - 19 -rendered into 400x300 space in […]
Show full quote

But Rush is not such speedster, timedemo framerates with Vulcan:
320x240 - 21.5
400x300 - 19 -rendered into 400x300 space inside 640x480?
512x384 - 16.4 - still not whole screen?
640x480 - 12.8 - this should not work with 2 MB, are you using software z-buffer?

What I heard was Rush being a bad performer, so this confirms it. Do you have a chance of comparing to windows numbers?
As for that whole screen issue, I don't know. We are using the open source glide3 and Mesa-5.0.2 libgl. (And I believe windows drivers would behave.)

Regular Quake 2 is about 10% faster at high resolutions, but scales well and can get up to 40 fps at 320x240.
Gl_ext_multitexture ability was detected correctly- disabled. Pointparameters I did not notice, but changing it had no effect, just like ztrick.

Is regular Quake2 using the 3dfx minigl driver or the default opengl?

I chose 3dfx minigl for this.
Tried that MTRRLFBE.EXE LFB WC, gives load error: no DPMI

Are you running this inside windows 9x dos box?! But yes, 3dfx minigl will always be faster, try comapring to regular opengl if your driver allows it (voodoo 1 and 2 won't)

I run yours under DOS. Rush can use both, the minigl is even bit slower than ICD.

That's interesting the minigl driver should be much faster.

but yes, put MTRRLFBE.EXE in the same directory as quake 2 because it needs CWSDPMI.EXE to load.

Maraakate wrote:

That's interesting the minigl driver should be much faster.

It can be with weak computer.

Maraakate wrote:

but yes, put MTRRLFBE.EXE in the same directory as quake 2 because it needs CWSDPMI.EXE to load.

I see, it helped: 29 fps 320x240, 14,2 at 640x480 - you matched windows performance at this resolution.

What did you get at 320x240 in Windows?

I guess we should add a note about using this utility or expect poor performance.

I am trying this on my 200mmx/voodoo1 build, 3DFX is enabled but it's actually slower than software rendering... is that normal?

Probably because of the library overhead. My P1 200 can barely do it on a voodoo 2. A pentium 2 with a voodoo 3 or anything faster will be much better.

I also noticed the card really needs LFB write combing with MTRR's set to get comparable windows speeds and Pentium 1 does not support this but maybe windows has some trick in their drivers to set it up on such a computer.

I see.... well at least there is a DOS port now for PII+ , still really nice!

And for the record... even in windows I only get about 30fps in timedemo of demo1 with a voodoo 2. So it's basically unplayable at that point unless you tweak cvars to severely reduce texture size and everything else, basically making it look like a smeary piece of shit which defeats the whole purpose of the 3d acceleration aspect imo.

And to verify otherwise. with MTRRLFBE.EXE on my Pentium 3 in DOS @ 640x480 on timedemo demo1 I get 112.8fps. In windows it's 119.4fps. So the speeds are relatively close if your chipset allows this to be set.

EDIT: Forgot to mention that was Quake 1, sorry!

Also, I never knew how terrible the rush cards really were, take a look at this old review:

http://vintage3d.org/3dfx2.php

Whatever it was tested on it was slower than a voodoo 1 with Quake 2 and likewise got ~15fps in timedemo demo1! It doesn't mention the CPU setup or anything else, but I'd imagine it was some kind of Pentium 1 setup.

Specs are here. It is not that old, think I started in 2011.

Uploaded builds from latest code:

Software renderer only:
https://bitbucket.org/neozeed/q2dos/downloads … 50824_SWonly.7z

All features including 3dfx/gl:
https://bitbucket.org/neozeed/q2dos/downloads … 20150824_ALL.7z

Awesome work!

Tested the software only version and got...
Dos(exited from Win98) - using "MTRRLFBE LFB -WC"
31.5 fps on timedemo1 @ 1280x1024
and
103.0 fps on timedemo1 @ 640x 480
-in Dos(exited from Win98) - 'mtrrlfbe LFB -WC'.

Win98(Dos'd and -nosound)
57.1 fps on timedemo1 @1280x1024 (~183%)
155.0 fps on timedemo1 @ 640x 480 (~ 150%)