Sezero just realized a mistake in the code and as such I have reuploaded a new 3dfx package. Same link as before, so if anyone out there tried this, please redownload and try it again.

Uploaded an all-in-one package: https://bitbucket.org/neozeed/q2dos/downloads … 20150821_ALL.7z
Please test: Feedback from Voodoo Rush users is appreciated.

edit: new error
Sys_error: unresolved symbol(s) in ref_gl.dxe

inside log is: clock: unresolved symbol

Putas wrote:

Sys_error: Couldn't load pics/16to8.dat

You should install guake2 game for q2dos to work. E.g. put baseq2\*.* from quake2 cdrom into <your_q2_dir>\baseq2\

Putas wrote:

edit: new error
inside log is: clock: unresolved symbol

Thanks! Updated package with a fix applied is here: https://bitbucket.org/neozeed/q2dos/downloads … 150821r1_ALL.7z

It works now. When 320x240 is chosen the screen is split horizontally and rendered twice.

Does rush support 320x240?

Maraakate wrote:

Does rush support 320x240?

Yes.

That's pretty incredible that it works at all, considering the code was always broken!

Putas wrote:

It works now.

Great. Thank you very much for testing. Can you tell us exactly what model of Voodoo Rush you are using?

When 320x240 is chosen the screen is split horizontally and rendered twice.

Arghh.. We should revise our menus. Lowest resolution for a voodoo should practically start from 512x384.

Yeah, and I noticed no matter if it was the v3 or v5; p2 or p3 the speed impact from 320x240 to 640x480 is minimal there's no reason to keep it around.

Just posting that I tried that in software mode on my 233mmx/riva128zx build, it's amazing! Sure it's sub-30fps most of the time (12~31fps as far as I can see) at 320x240 but hats off for the port!

Oh, run MTRRLFBE.EXE or fastvid.exe if your chipset supports modifying the LFB writes. If it does, you will get a nice speed boost by using the VESA 320x240 instead of Mode-X version.

I also noticed that using MTRRLFBE.EXE instead of fastvid on my voodoo 3 and 5 cards makes a drastic difference in speed compared to fastvid. Since the rush has it's own 2d accelerator as well I'd imagine it makes a difference also.

szo wrote:

Putas wrote:

It works now.

Great. Thank you very much for testing. Can you tell us exactly what model of Voodoo Rush you are using?

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

szo wrote:

Putas wrote:

When 320x240 is chosen the screen is split horizontally and rendered twice.

Arghh.. We should revise our menus. Lowest resolution for a voodoo should practically start from 512x384.

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?

If software z-buffering is used it must be something in the rush driver as we are using the actual ref_gl from id software with some special performance enhancements by knightmare.

Also what is the cpu? I noticed all this 3dfx stuff seems to be dependant on the CPU.

Duron 650, worst are outer areas.

Wow. That's pretty slow. Have you tried using http://rayer.g6.cz/programm/mtrrlfbe.exe ? just do MTRRLFBE.EXE LFB WC. Should increase your speeds if your chipset supports it.

Also, I forgot. Is gl_ext_multitexture and gl_ext_pointparameters set to 0? If they were enabled and you disable them you will need a vid_restart or restart quake 2.

Another thing to try is gl_ztrick 1. And finally, if you're getting a little desperate you can disable the dlights entirely with gl_dynamic 0 which should give a decent boost.