Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - AntiMatter_16

#1
Would it be possible to enable SLI in vista? Or is it as impossible as it is with XP?
#2
I'm having a problem with my Voodoo3 and Quake III. It will not let me select the voodoo (glide) rendering in the setup menu. I was originally using XP and the SFFT 34 drivers, but then reinstalled Win98 with the lastest Amiga Merlin drivers. Still no go. Homeworld also won't let me select the 3dfx rendiner. Both games will let me run the OpenGL rendering, but it's really REALLY slow. Unreal Tournament lets me select the Glide Rendering, but it's helluva slow as well.

I tried using these dlls, that PS47 mentioned, but it didn't fix my problem...
#3
I installed the DLLs... didn't seem to change anything. Homeworld and Quake III still don't find Glide Rendering. I did get 2 FPS more in Quake I though. =) Do these replace the SFFT34 drivers I installed, or are they independant?
#4
Just installed the 34 version over the 33. Running XP with a Voodoo 3 2000 running on an old AMD K6-II 500 oc'ed to 550. 256 megs of PC100. Ran GlQuake fine, 96.2 fps. Quake III doesn't want to find the GLide renderer, so it runs in OpenGL, kinda slow. Homeworld doesn't want to run in GLide either. Not sure of the problem. Any advice? UT detects Glide okay. It doesn't run too well though, even on the lowest settings. Need For Speed High Stakes runs well. It also detects GLide. I had some crashes with the 33 driver. Dunno if they're still around for 34. Could just be that it's an old game, and not so XP compatible.
#5
Yes, I know about voodoomage, etc. But that's not what I'm asking. I'm asing if a project started from scratch, and not built up from old drivers, could overcome the D3D shortcomings.
#6
What would it take to build a set of voodoo2 drivers from the ground up to be compatible with windows XP Direct3D, OpenGL, and GLide? I don't know much about the D3D and voodoo2 problem. Is it possible to solve it from a software level if it was started from scratch? Or is there some sort of conflict between how Windows XP handles hardware and the hardware of the Vooodoo2?