Dropping off a new V2 driver kit. This kit includes fixes for system hangs on modern systems. Also gamma will be set to 1.00 if you use the included driver inf to install the driver. I am currently running my trusty V2 along with an ATI Radeon.

Tips to run Need for Speed 2 SE on Windows 2K/XP/VISTA
1. Do NOT copy the glide2x.dll to the game's folder.
2. Use Microsoft's Application Compatibility Tool. Follow the excellent tutorial; http://www.youtube.com/watch?v=jy1qfZBFEWo.

-KoolSmoky

Hi. Just dropping off new drivers. Included are support for new glide features and fixes for the memmap errors reported in this thread. Sorry I hadn't released the files more earlier. I simply forgot for quite a long time. Anyway, check out the first post for details. I wish you all happy holidays and a prosperous new year.

-KoolSmoky

The slave V2 snoops the master in SLI mode. Writes to the master are also received by the slave simultaneously.

-KoolSmoky

In SLI mode, the front, back, and auxiliary buffer is halved for each Voodoo2 board. The remainder of the board's linear frame buffer is unused. Nevertheless, the LFB stride of the V2 is always fixed to 1024 pixels. If you check the stride using the 3dfx Glide API, it will always return the number of bytes for 1024 pixels regardless of the actual resolution.

The V2 came out in 1998. Imagine how many people in the consumer market could afford a system that could do over 1024*768 in 3D.

-KoolSmoky

Just dropping by to say hi. It's a hardware limitation. The Voodoo2 linear frame buffer accesses always assume a 1024 pixel logical scan line width regardless of the actual frame buffer resolution. The maximum width possible is 1024 pixel. The height is not restricted, though.

-KoolSmoky

QuoteOriginally posted by osckhar

@KoolSmoky,
Check it:

3DMark2001Se + V6k (AGP2PCI)

- KoolSmoky beta driver:
NO FSAA - 5025Points
2xFSAA - 3705Points
4xFSAA - 2250Points
8xFSAA - 2250Points

Collin McRae 2 + V6k (AGP2PCI)

- KoolSmoky beta driver:
NO FSAA - Timedemo 90sec - 94 AVG.
2xFSAA - Timedemo 90sec - 56 AVG
4xFSAA - Timedemo 90sec - 29 AVG
8xFSAA - Timedemo 90sec - 29 AVG

Oscar

What 3D API does it use? As I've said before, I only have time for Glide/OpenGL (READ: Spare my time to google. If you think I have reduntant time, you're on crack.) It would be helpful to provide detailed info as much as possible, demo links, screenshots, etc. I see that your numbers for 4x and 8xFSAA doesn't change, but it doesn't necessary mean that 8xFSAA isn't working. Give me some screenshots that illustrates your problem.

-KoolSmoky

QuoteOriginally posted by osckhar
8xFSAA does not work well. When It is enabled V6k only works to 4xFSAA.

First of all, let me just say that I only have time to deal with Glide/OpenGL and they have been tested to work with 8xFSAA. Give me some screen shots that illustrates your problem.

QuoteOriginally posted by ggab
got severe 2D graphic display issues with photoshop...

Remove SSTH3_VIDEO_REFRESH_OPTIMIZATION if you have any set.

Besure to read my previous post:

5. Be sure you do not have any old registry setting left from prior drivers under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\3dfxvs\Device*" or under its subkeys.

-KoolSmoky

Hi guys,

I've been recieving PMs regarding riser card + V56K combo compatibility so I'm posting answers here.

The riser card that is known to work with the V56K is the "Kuroutoshikou CHANGE-AGP2PCI". Several people have confirmed that the V56K is fully functional. Moreover, Osckhar has successfully modded the riser card to run at 66MHz PCI bus speed which is the fastest bus speed that the V56K accepts. For instructions and jumper settings see:
http://www.3dfxzone.it/enboard/topic.asp?TOPIC_ID=6728
http://www.3dfxzone.it/enboard/topic.asp?TOPIC_ID=6256

Other riser cards will mostly likely work, however information is lacking. So if anyone has a riser card working with any of the VSA cards please post them here. Info regarding PCI-E riser cards would be especially useful.

For win2k/xp, the Voodoo5 driver posted at the top of this thread will work with a riser card if the V56K is detected by the system. Other win2k/xp drivers have a bug that makes the card fail with most system configurations and is not foolproof.

-KoolSmoky

QuoteOriginally posted by ggab

hi, may i ask a regedit addon to have the Vertical sync option (enable/disable/software contolled) available in D3D mode in 3dfx tools, it shows in glide/ogl only...

Hi ggab,

Set SSTH3_SWAPINTERVAL to 0 to disable V-Sync. Or you could use the attached vsync.inf to make it show up in 3dfx tools.

USAGE: Under Windows Explorer, or when the file is on the Windows desktop, right click on the file then choose "Install".

-KoolSmoky

Download Attachment: vsync.zip
1.16 KB

Start out by just masking pin 49 side B and see if that enables 66MHz operation. If it doesn't work, then connect it to a pullup resistor to Vcc. You can cut the line on the PCB or create a new pin over the mask. I recommend you do a little researching yourself before doing the mod. You can find the PCI spec docs at PCI-SIG.

-KoolSmoky

Looking at your pic, if you trace the line from pin 49 side B, there's an IVH going from side B to A right above pin 48 side B. I bet it connects to pin 48 side A. Which means pin 49 side B is connected to GND.

What you need to do now is isolate pin 49 side B and connect it to a pullup resitor to Vcc.

-KoolSmoky

Then trace the lines from pin 49 and find where they connect to.

-KoolSmoky

Are pins 46 and 49 on side B connected?

-KoolSmoky

The pin marked in red is not pin 49.

-KoolSmoky

Image Insert:

68.37 KB

Pin 49 on side B of the AGP2PCI riser card needs to be pulled-up to operate in 66MHz. Connecting it to GND signals the mainboard to run 33MHz. So for starters, check if the pin is connected to GND or not.

Isolate the riser card from the system and V56K before doing the checks. You have been warned.

-KoolSmoky