3dfxzone.it WorldWide Community

3dfx Hardware & Software => Voodoo4/5 Setup and tweaking => Topic started by: darkfalz on 05 February 2005, 16:50:54

Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 05 February 2005, 16:50:54
Will I be able to install the vs-w2k-1.04.00.exe drivers on WindowsXP? I can disable the internal driver quite easily (just rename the inf).

I take it though, that Glide or something crashes even once you can get them to install, is that correct? Is there a patched (not rebuilt) version of the official Glide version that would be able to work?

I am looking for the best way to, if possible, use the final 2k WHQL drivers on XP. Not interested in the Amigamerlin stuff (all respect to him). Keep in mind the only games I play are UT and Q3A.
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 05 February 2005, 22:50:13
Okay, I installed the 2k drivers by installing them once then running through agian, seemed to go okay. I am missing a few tabs though, 3dfx Info, and General settings, and I can't select overlay - this normal for the 2k drivers? Then I replaced the glide with the koolsmoky versions. UT did crash badly once but otherwise been working okay. Shame that OpenGL doesn't recognise r_displayRefresh 85 in Quake III... stuck in 60 Hz :S Will have to put RefreshLock or something... but doing quite well, the Glide stuff I tried ran fine.
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 06 February 2005, 09:46:38
Seem to have a fairly smoothly running system, except for one thing. I simply cannot get Quake III (OpenGL) to run above 60 Hz.

r_displayRefresh doesn't work (which is stupid, because Glide can control refresh rate, works in UT for example)
RefreshLock didn't work (I guess it doesn't work for Glide)
Voodoo Refresh (or whatever it was called) didn't work, got my Quake III in a corner of the screen in 60 Hz again...

Damn it! Anyone have a solution?
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 06 February 2005, 12:39:09
Whoa! A simple existing registry value, FX_GLIDE_REFRESH, did the trick!

Now I'm a happy chappy!
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 06 February 2005, 13:56:54
Getting some major grief from Lewpy's plugins, crashing ePSXe and crashing the whole system in ZiNc... argh. I might try the GlideXP version over Koolsmoky's.
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 09 February 2005, 13:38:58
Okay, I've gone back to WindowsME. :)
Title: Best "official driver" solution for WindowsXP?
Post by: ggab on 10 February 2005, 01:15:55
at least for me, the best glide3x.dll is the one who comes in AM3.0 (v 3.10.0.30303 Sábado, 30 de Agosto de 2003, 03:13:00) for example glide64 video plugin works better (no GFX exceptions' windows)

byes
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 10 February 2005, 23:56:21
I got weird lines with AM3.0 in D3D and also with the latest Glide from sourceforge... I know it's not my card because other drivers, and of course the proper ones under 9x, work great.
Title: Best "official driver" solution for WindowsXP?
Post by: ggab on 11 February 2005, 06:42:15
http://hyperionics.swmirror.com/HS5Setup.exe

HyperSnap-DX is a screen-capture and image-editing tool.
It can capture screens from standard desktop programs and DirectX/Direct3D, 3Dfx Voodoo, and Glide mode games.


maybe a sshot can help....

PS: did u install AM3.0 properly?
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 15 February 2005, 18:35:57
They are just lines across the screen, every 16 pixels or so. Very noticble...
Title: Best "official driver" solution for WindowsXP?
Post by: ps47 on 15 February 2005, 18:50:21
if you have horizontal lines,make sure NOT to set the quality to high in 3dfx tools.use normal or automatic,and the lines will go away..
Title: Best "official driver" solution for WindowsXP?
Post by: SuperFurryFurryThing on 15 February 2005, 19:22:08
Do the lines appear only in a low res mode in D3D i.e. 640 * 480 16 bit, and if you run in single chip do the lines dissapear.

SFFT
Title: Best "official driver" solution for WindowsXP?
Post by: ps47 on 15 February 2005, 20:50:34
..this is a known problem.if you set the 3d filter quality to high and you run an app in 32-bit mode,you will get those lines (they do not have a color,irs more like the screen was cut to stripes and then assembled incorectly).just set the 3dfilter to automatic or normal,and you will be fine..
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 17 February 2005, 00:31:15
Yes it looks very much like that, however I also got them in 16 bit (not quite as noticible though) and with no chang to 3d filter settings (left on Automatic).
Title: Best "official driver" solution for WindowsXP?
Post by: SuperFurryFurryThing on 17 February 2005, 01:39:48
Are you discussing problems in OpenGl/Glide or D3D as they are likely to be separate problems. There is a known problem with the AM 3 core in D3D with low resoulution 16 bit modes in some circumstances.

SFFT
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 18 February 2005, 04:37:07
I wouldn't call it a seperate problem because it's the same artifact. I got it in all D3D modes I tried, 800x600 and 1024x768 in both 16 and 32 bit.
Title: Best "official driver" solution for WindowsXP?
Post by: bloodworm on 18 February 2005, 22:29:16
which video BIOS is your V5 running? and also, have you tried the MESA openGL drivers yet for Q3A and UT?  if you are running the "standard" openGL drivers for your V5, then one of the ICD interceptors will be a must (Rainbows or the GlideXP project one).
Title: Best "official driver" solution for WindowsXP?
Post by: darkfalz on 19 February 2005, 04:45:47
I got the lines under the latest sourceforge Glide3, but not under the final by koolsmoky. Didn't actually try GlideXP, it seems he added too much weird junk to it.

I don't see what BIOS has to do with it. And yeah the MesaFX are great but for the CPU I have on that machine which is only 1 GHz it's really not suitable, it's too slow. MesaFX really needs a modern CPU.