This thread has been opened to allow our readers to add their own comments to the news entitled as in this post subject. Please note you can get the full content of this news reading the article posted at this following URL: https://www.3dfxzone.it/news/reader.php?objid=5280
edit : moved and sticky
AMAZING NEWS! Koolsmoky, are you planning further development? It's good to see. :) Maybe you could coop with SFFT. And then ... fix the V56k SLI ****up and stuff. :D
Greetings and thanks,
Raff
thanks a lot!!!
super GREAT news!!!!!
thank you
I don't know whether it's my mainboard again (ASRock 4CoreDual-VSTA), but my V5 5500 PCI doesn't like this driver. Some internet pages look like this sometimes:
http://img76.imageshack.us/my.php?image=buglk0.jpg
I'll test the driver with my Voodoo machine (AGP) on the weekend.
Greetings from Germany,
Raff
Do you want some feedback? Well, here it is. ;)
I've tested some games on my V5 5500 AGP that work fine with newer SFFT's. I focussed on Direct3D, because that's what interested me the most. Here I encountered a bug that disturbed me already on my V5 6000 – driver-independant. Every (approximately) 32 pixels a bright line is shown. Koolsmoky, did you change anything that concerns the SLI scanlines? This does not happen in OGL or Glide. Concerning the games:
- FlatOut 2: Perfect
- NFS Underground: BSOD with reference to 3dfxvs.dll
- UT2004: On some maps the strange bug with "flying" transparent textures of older drivers is back
- Dungeon Siege 2: Crash after loading
- Max Payne 2: Runs fine, even in 1920x1440 (nope, not fluent ;))
- Postal 2: No errors, nice fps
Conclusion: SFFT's Direct3D part is more advanced. The Koolsmoky seems to contain some brand-new Glide-DLLs, but I don't know which improvements were made.
SFFT and Koolsmoky, I'd really appreciate if you two could do some "SLI": Work together, 'cause four eyes see more than two! A new driver package, named "KoolSFFT" or "SFFTmoky" would be nice. :D
Greetings and thanks,
Raff
I have intalled this driver for Voodoo2, but how I can make work a game based on DirectX? There is any way to force a game to use a Voodoo2?
For OpenGL & Glide seems to work well, but I must prove more games
Hi,
I tried the driver and It can not handle the DVI-out from my Voodoo4 AGP.
Thank you,
Oscar
Hi guys,
First of all, there is some important information missing in the file description. The following assumes you have read the "about.txt" included in the driver set.
Voodoo4 and 5:
1. This release is a fix for V4 V5 DVI output, V56K + AGP2PCI, Glide/OpenGL multi-monitor support. You must use the supplied "3dfxvs.dll (5.01.2600.0003)", "3dfxvsm.sys (5.01.2600.0003)", and "3dfxvs.inf" to get it to work.
2. A new "glide3x.dll (3.10.00.22217)" has been supplied which includes a number of fixes and additions made by the glide.sourceforge.net crew. It is recommended that you replace this file over any previous glide3x.dll installed. Although I have released it with the Voodoo5 WinXP/2k driver set, it fully supports Banshee, V3, V4, V5 and will work on Win95, 98, 98se, Me, NT, 2k, XP. If you just need glide3x, extracted it and copy it to the appropriate folder.
3. The V4 V5 DVI fix is more of a hack to enable DVI output for people who are having trouble with hot-plug detection with their flat panel displays. After you have set "ForceDFP" to "1", be sure to reboot. The V4 or V5 BIOS must have DVI support built in otherwise you are screwed.
4. All prior VSA windows driver has a problem of not being able to run Glide or OpenGL on secondary and beyond VSA card if you have multiple VSA cards installed. This has been resolved.
5. The windows display driver "3dfxvs.dll" is DX7 based. If you need a more advanced D3D driver, I would recommend the excellent SFFT driver. You should, however, use the newly provided "glide3x.dll".
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.
Voodoo2:
1. I have not included directx or minigl drivers. If you need them please obtain it from other driver sets. All files provided are newly built drivers with the latest "glide2x.dll (2.56.0.22217)" and "glide3x.dll (3.3.0.22217)" from the glide.sourceforge.net crew. The "glide2x.dll" and "glide3x.dll" support V2 including the Quantum3D Obsidian series and will work on Win95, 98, 98se, Me, NT, 2k, XP.
2. Be sure you do not have any old registry setting left from prior drivers under "HKEY_LOCAL_MACHINE\SOFTWARE\3Dfx Interactive\Voodoo2" or under its sub keys.
To Raff3DC: for your V5 PCI, remove SSTH3_VIDEO_REFRESH_OPTIMIZATION if you have any set. As for including my changes in the SFFT driver, I'll leave that up to SFFT. He has a strict policy of working alone and keeping his work clean. I would like to respect his style.
To Xasd: I did not include the files for directx. Mainly because I believe that the only reason someone will still use a V2 is because they want Glide.
To osckhar: Does your V4 BIOS have DVI support built in? I presume it is a prototype?
And last but not least, don't forget to thank the dev crew over at glide.sourceforge.net :D
-KoolSmoky
@KoolSmoky
I have tried differentes Voodoo cards with DVI-out without luck. The 3Dfx tools shows the DVI option but it does not detect the flat panel when I active it.
Would be nice if SFFT introduceS in his driver the fix FOR V6k AGP2PCI.
Thank you very much,
Oscar
Aye smoky!
QuoteOriginally posted by koolsmoky
To Raff3DC: for your V5 PCI, remove SSTH3_VIDEO_REFRESH_OPTIMIZATION if you have any set.
Does this remove the visible lines?
QuoteOriginally posted by koolsmoky
As for including my changes in the SFFT driver, I'll leave that up to SFFT. He has a strict policy of working alone and keeping his work clean. I would like to respect his style.
Ok. :D
But: Do you have a good knowledge about the SLI functionality in the driver? Primarily the 4-way SLI. As I've written many times, the V5 6000 suffers from a severe bug when using Windows XP and Direct3D. Resolutions up to 1024x768 run fine, everything above is unplayable. Something really disturbs the communication between the GPU's. Look at this: http://3dcenter.de/artikel/voodoo5-6000/index14.php
In 1024x768 the 4-way-SLI works fine and can even compete with a GeForce3. But in 1600x1200 even the single-chip-V4 is faster than our goddess. Please, talk to SFFT, if you can, and try to fix this bug. It's hard to see the 6000 losing so much of its power. The Win98 drivers work, but they aren't as advanced as the SFFT is.
QuoteOriginally posted by koolsmoky
And last but not least, don't forget to thank the dev crew over at glide.sourceforge.net :D
-KoolSmoky
Yeah, thanks! :) Could you make a list of what's been improved? I'll have a look at the glides on the weekend.
Greetings and thanks,
Raff
Hi guys, :)
QuoteOriginally posted by osckhar
I have tried differentes Voodoo cards with DVI-out without luck. The 3Dfx tools shows the DVI option but it does not detect the flat panel when I active it.
To use DVI you need to do what I have written in the "about.txt" and also in my previous post. I have had the same symptoms with my V5 5500 PCI mac flashed with pc bios which is why I made the fix. If you don't know whether your V4 is use "Device0", "Device1", etc, set them all.
QuoteOriginally posted by Raff3DC
Does this remove the visible lines?
SSTH3_VIDEO_REFRESH_OPTIMIZATION sets the memory optimization for desktop and overlay requests. Try it and let us know if it resolves your problem.
QuoteOriginally posted by Raff3DC
But: Do you have a good knowledge about the SLI functionality in the driver? Primarily the 4-way SLI.
The Amigamerlin driver set was the first ever to support all SLI/FSAA modes with the V56k on win2k/xp. Until then it was unfinished business by 3Dfx and would only run in single chip mode. Every one thought that the king of 3Dfx card would be crippled forever on win2k. Guess who provided the cure? ;) The basic SLI setup routines currently reside in the 3dfx windows miniport driver and both D3D and Glide (we all know that OpenGL wraps around Glide3x) use it. Since my main focus has always been on Glide and OpenGL, I really haven't looked at D3D much. I know that the 3dfx windows display driver does extra work to support SLI in D3D so I'm guessing that's where it gets all complicated. Anyway, according to your V56k article, Serious Sam SE runs fine with 4-way SLI in OpenGL mode.
QuoteOriginally posted by Raff3DC
Could you make a list of what's been improved? I'll have a look at the glides on the weekend.
Well, lots of bug fixes have been made, and additions to support multi-monitor. If I have time, I'll show you a demo using the new feature.
-KoolSmoky
Edit: Ah fu**, all my post gone. Have to write everything again...
QuoteOriginally posted by koolsmoky
SSTH3_VIDEO_REFRESH_OPTIMIZATION sets the memory optimization for desktop and overlay requests. Try it and let us know if it resolves your problem.
K, thanks, I'll try it.
QuoteOriginally posted by koolsmoky
The Amigamerlin driver set was the first ever to support all SLI/FSAA modes with the V56k on win2k/xp. Until then it was unfinished business by 3Dfx and would only run in single chip mode. Every one thought that the king of 3Dfx card would be crippled forever on win2k. Guess who provided the cure? ;) The basic SLI setup routines currently reside in the 3dfx windows miniport driver and both D3D and Glide (we all know that OpenGL wraps around Glide3x) use it. Since my main focus has always been on Glide and OpenGL, I really haven't looked at D3D much. I know that the 3dfx windows display driver does extra work to support SLI in D3D so I'm guessing that's where it gets all complicated.
Hmmm. Could you please have a look at the problem? Maybe you see what's f****d up. Turn the king into the king of all classes. :D
I'm not familiar with driver programming (I'm just testing them ;)), but I assume it's not a "big thing", 'cause the 4-way SLI works fine in low resolutions ... It seems as if something can't handle the growing work. OMG, slower than single chip ... [xx(]
QuoteOriginally posted by koolsmoky
Anyway, according to your V56k article, Serious Sam SE runs fine with 4-way SLI in OpenGL mode.
Ya, sorry, I've forgotten to mention that. Glide and OpenGL run fine in 1024x768+.
QuoteOriginally posted by koolsmoky
Well, lots of bug fixes have been made, and additions to support multi-monitor. If I have time, I'll show you a demo using the new feature.
Just if you have time. :)
_____
By the way: The arcticle is currently being translated into English, you guys can have a closer look at it in maybe some weeks. And I promise that if the SLI works fine we'll make another update with new benchmarks and maybe some more "enemy" cards!
Greetings from Germany,
Raff
Hi koolsmoky,
I really appreciate your great work. But there is a big problem concerning all newer glide drivers:
A modification of the texture LOD bias affects only the first VSA100. For example if you use 2xAA and a default LOD bias, the mipmaptransition of the second VSA100 is at LOD -0.5. If you change the bias to -0.75, the other transition is still at -0.5 instead of -1.25 - which leads to crappy imagequality.
Oh, and plz also fix the SLI-****up. ;)
QuoteTo use DVI you need to do what I have written in the "about.txt" and also in my previous post. I have had the same symptoms with my V5 5500 PCI mac flashed with pc bios which is why I made the fix. If you don't know whether your V4 is use "Device0", "Device1", etc, set them all.
koolsmoky,
You are right. It works perfect on my V4 4800 64Mb AGP card. :)
Oscar
QuoteOriginally posted by roflkopp
A modification of the texture LOD bias affects only the first VSA100. For example if you use 2xAA and a default LOD bias, the mipmaptransition of the second VSA100 is at LOD -0.5. If you change the bias to -0.75, the other transition is still at -0.5 instead of -1.25 - which leads to crappy imagequality.
Hmm, are you talking about glide3x or glide2x? What application and VSA card are you using? The glide2x.dll included in the driver set is the original driver from 3Dfx and I have not touched it. You can download a newer glide2x.dll from my website (http://www.3dfxzone.it/koolsmoky) but it still needs more work done. As for glide3x, I cannot reproduce your problem with my V5 5500. Could you post some screenshots? BTW, "FX_GLIDE_LOD_BIAS" takes an integer value between -8 to 8.
QuoteOriginally posted by osckhar
You are right. It works perfect on my V4 4800 64Mb AGP card. :)
I knew it would work. :)
-KoolSmoky
I'm talking about glide3x.
Here are some Q3a Screenshots which illustrate the problem: http://www.keepmyfile.com/download/f9da801748814
EDIT: card is a voodoo5 5500 pci, but a 6000 also has the same problem...
QuoteOriginally posted by koolsmoky
2. A new "glide3x.dll (3.10.00.22217)" has been supplied which includes a number of fixes and additions made by the glide.sourceforge.net crew. It is recommended that you replace this file over any previous glide3x.dll installed. Although I have released it with the Voodoo5 WinXP/2k driver set, it fully supports Banshee, V3, V4, V5 and will work on Win95, 98, 98se, Me, NT, 2k, XP. If you just need glide3x, extracted it and copy it to the appropriate folder.
My Voodoo3 AGP doesn't like the Glides (Win XP). Starting UT or Undying results in a corrupted screen and the need to reset. V5 runs fine.
Greetings,
Raff
QuoteOriginally posted by roflkopp
Here are some Q3a Screenshots which illustrate the problem:
The sign of the lodbais is being lost with performance trilinear routines. I have fixed it and will be fine in the next release. For now you can set FX_GLIDE_LOD_SUBSAMPLE_DITHER to 0 if you need to change FX_GLIDE_LOD_BIAS.
QuoteOriginally posted by Raff3DC
My Voodoo3 AGP doesn't like the Glides (Win XP). Starting UT or Undying results in a corrupted screen and the need to reset. V5 runs fine.
UT uses Glide
2x unless you are using the OpenGL renderer. The glide
2x.dll in the Voodoo5 driver set is the original 3Dfx driver. All original (untouched) 3Dfx Glide drivers (glide2x and glide3x) are incapable of running on winxp unless you are using my modified windows minport and display driver which includes a fix for this issue. Additionally, the glide
3x.dll in the driver set includes a special workaround to enable use with any winxp banshee,V3,4,5 driver set (excluding Microsoft's). If you'd like, you can download a glide
2x.dll that includes the same fix from my web page.
Let me repeat my initial post;
The "glide3x.dll (3.10.00.22217)" in the Voodoo5 driver set fully supports Banshee, V3, V4, V5 and will work on Win95, 98, 98se, Me, NT, 2k, XP. If you just need glide3x, extracted it and copy it to the appropriate folder.
The "glide2x.dll (2.56.0.22217)" and "glide3x.dll (3.3.0.22217)" in the Voodoo2 driver set supports V2 including the Quantum3D Obsidian series and will work on Win95, 98, 98se, Me, NT, 2k, XP.
-KoolSmoky
wow. thank you very much. now it will be finally possible to take voodoo5 6000 aa-screenshots with good texturequality :)
but there are still a few featurerequests - if you run out of new ideas *g* :
x) a possibility to force FXT/DXT compression in d3d/glide/opengl:
x) an option to force 16bit wbuffer instead of zbuffer in d3d.
x) an option to force 16bit rendering in d3d
x) an option to surpress vendor id's (if it's possible) - to run FarCry eg. ;)
x) an option for temporal aa (switch aa sample pattern per frame)
x) a software tnl-engine
x) a software pixelshader-engine ;)
x) a modification which allows to use 2 voodoo5 5500s in sli - per feature connector :D
Unfortunately I do not have the time to work on D3D. Besides, you always have SFFT's excellent D3D driver. I can only find time to spend on Glide related projects. The Voodoo5 driver set I provided are geared toward those who need a stable win2k/xp driver set for Glide and OpenGL.
QuoteOriginally posted by roflkopp
x) a possibility to force FXT/DXT compression in d3d/glide/opengl:
For OpenGL, the application will most likely request and use texture compression if available. As for Glide, existing applications do not require excessive texture ram so there is not much point forcing it. I believe the only reasonable stuff to use forced compression are emulator gfx plugins like Gonetz's Glide64 and Lewpy's PSX glide3 plugin, especially when used with texture enhancers like 2xSaI and Hq4x or Hi-Res retexture packs. In fact, Gonetz and I have made a texture enhancer library with forced texture compression for Glide64. Check it out at http://www.emuxhaven.net/forums/showthread.php?t=6427
QuoteOriginally posted by roflkopp
x) an option for temporal aa (switch aa sample pattern per frame)
Temporal AA is old news. Daniel and I have implemented it a long time ago. Glide3x and OpenGL has it. Set FX_GLIDE_TAA_TOGGLE_KEY and you'll get temporal AA. 2xFSAA will give a 4xFSAA effect and 4xFSAA will give 8xFSAA. "144" will let you toggle TAA on and off with the "NumLock" key. You'll need at least 100fps to fool your eyes.
QuoteOriginally posted by roflkopp
x) a modification which allows to use 2 voodoo5 5500s in sli - per feature connector
SLI would be difficult to do because you need strict signal timings. AFR or Split screen rendering would be more feasible but you'd still need a hardware mod. The feature connector on the VSA board is not a SLI connector. To get this done, Hank's help is a must. There is also a lot of work to do the driver side of things.
-KoolSmoky
QuoteOriginally posted by koolsmoky
In fact, Gonetz and I have made a texture enhancer library with forced texture compression for Glide64. Check it out at http://www.emuxhaven.net/forums/showthread.php?t=6427
seems interesting. I'll have a look on it. on the other side i'm quite sure, that later glide games like operation flashpoint nfs5 and (maybe even) ultima9 would profit from compressed textures.
QuoteOriginally posted by koolsmoky
Temporal AA is old news. Daniel and I have implemented it a long time ago. Glide3x and OpenGL has it. Set FX_GLIDE_TAA_TOGGLE_KEY and you'll get temporal AA. 2xFSAA will give a 4xFSAA effect and 4xFSAA will give 8xFSAA. "144" will let you toggle TAA on and off with the "NumLock" key. You'll need at least 100fps to fool your eyes.
good point. :D
QuoteOriginally posted by koolsmoky
SLI would be difficult to do because you need strict signal timings. AFR or Split screen rendering would be more feasible but you'd still need a hardware mod. The feature connector on the VSA board is not a SLI connector. To get this done, Hank's help is a must. There is also a lot of work to do the driver side of things.
-KoolSmoky
Ok, mayby i'll propose this to hank, after he finished his 256mb ddr vsa101 6000 :D
QuoteOriginally posted by koolsmoky
Unfortunately I do not have the time to work on D3D. Besides, you always have SFFT's excellent D3D driver. I can only find time to spend on Glide related projects.
Unfortunately SFFT is not so communicative and seems to ignore my ideas. but another neat idea would be a fps counter in glide. i'm shure raff would update his nfs5 benchmarks.
QuoteOriginally posted by roflkopp
on the other side i'm quite sure, that later glide games like operation flashpoint nfs5 and (maybe even) ultima9 would profit from compressed textures.
Every game could profit in high resolutions and/or with SSAA enabled. :) Look at Unreal Tournament, which runs fine with WickedGL and maxed FXT1. The higher the settings, the more Glide is slower.
Sure, bigger textures mean more hunger for VRAM and bandwidth, but why wasting fps if you could have them even with small textures? :D
Just yesterday I encountered impressive results of what texture compression can do: http://forum.voodooalert.de/thread.php?threadid=13478
QuoteOriginally posted by roflkopp
Unfortunately SFFT is not so communicative and seems to ignore my ideas. but another neat idea would be a fps counter in glide. i'm shure raff would update his nfs5 benchmarks.
Of course I would! :)
But the most important still is a fix for the SLI bug. I'm sure the goddess could kick some more GeForce asses then. Again I can only ask, or better pray to you: Please look at this bug! :)
Greetings,
Raff
QuoteBut the most important still is a fix for the SLI bug. I'm sure the goddess could kick some more GeForce asses then. Again I can only ask, or better pray to you: Please look at this bug!
Jeah, if any time this bug could be banned, the performance in some games would be greatly improved.
QuoteOriginally posted by Raff3DC
Every game could profit in high resolutions and/or with SSAA enabled. :) Look at Unreal Tournament, which runs fine with WickedGL and maxed FXT1. The higher the settings, the more Glide is slower.
Sure, bigger textures mean more hunger for VRAM and bandwidth, but why wasting fps if you could have them even with small textures? :D
Just yesterday I encountered impressive results of what texture compression can do:
I know very well that compression reduces texture swapping to the hardware and helps with performance. Which is why I give an option to force compression in the Glide64 texture enhancement library. If it prooves to work well and if I have time, I might just port the function to Glide. You have to understand that we are dealing with realtime compression. Games that download all textures to the hardware before a game is started are easy to deal with. BTW, did you resolve your problem with V3 and UT? It would be nice to know.
QuoteOriginally posted by feinripp
QuoteOriginally posted by Raff3DC
But the most important still is a fix for the SLI bug. I'm sure the goddess could kick some more GeForce asses then.
Jeah, if any time this bug could be banned, the performance in some games would be greatly improved.
I understand it would be wonderful to have a perfect V56K. Unfortunately right now I only have time for Glide OpenGL and SLI pretty much work OK with them. Free time is what I need.
-KoolSmoky
QuoteOriginally posted by koolsmoky
You have to understand that we are dealing with realtime compression.
Just like WickedGL. You only have to compress the textures once, if you save the in a swapfile.
But a glide fps-counter would be also a nice (imo easier to implement) feature.
Maybe we should start a petition for metabyte to make wickedgl open source.
QuoteOriginally posted by roflkopp
Just like WickedGL. You only have to compress the textures once, if you save the in a swapfile.
But a glide fps-counter would be also a nice (imo easier to implement) feature.
I already do that with the Glide64 texture enhancer library. It uses the system memory to cache realtime enhanced compressed textures to achive speed. The cache will also be saved to disk so it can be used next time you run it. I understand you want this feature in the Glide driver itself.
As for the Glide fps-counter, isn't there any other tool like fraps?
-KoolSmoky
QuoteOriginally posted by koolsmoky
I already do that with the Glide64 texture enhancer library. It uses the system memory to cache realtime enhanced compressed textures to achive speed. The cache will also be saved to disk so it can be used next time you run it.
sounds good.
QuoteOriginally posted by koolsmoky
As for the Glide fps-counter, isn't there any other tool like fraps?
-KoolSmoky
Not that I know of. (fraps doesn't work under glide)
QuoteOriginally posted by koolsmoky
I understand it would be wonderful to have a perfect V56K. Unfortunately right now I only have time for Glide OpenGL and SLI pretty much work OK with them. Free time is what I need.
-KoolSmoky
I don't want to rush you. :) We're living with this bug for more than six years now. But it would be nice to know if somebody could kill it, finally ...
The compression for Glide sounds very nice, too. :)
Greetings,
Raff
koolsmokyQuoteAs for the Glide fps-counter, isn't there any other tool like fraps?
try this http://win32.fatal.ru/glidefps/ this programme was made by one of members of our -=Voodoo Masters=- club.
QuoteOriginally posted by max1024
QuoteAs for the Glide fps-counter, isn't there any other tool like fraps?
try this http://win32.fatal.ru/glidefps/ this programme was made by one of members of our -=Voodoo Masters=- club.
Thanks for the tip. :) Anyone try it out, yet?
# Would a moderator please move this thread to the "3dfx, hardware and software - General Forums, General", thanks.
-KoolSmoky
V6k + AGP2PCI works perfect under Windows XP. [8D] I have tried different FSAA without problem. :D
Oscar
excellent news osc!
have a GREAT time ;)
voodoo power! via 3dfxzone.it's boards :)
QuoteOriginally posted by koolsmoky
:) Anyone try it out, yet?
Yes. It's working perfectly...
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...
thank you.
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: (https://www.3dfxzone.it/enboard/images/icon_paperclip.gif) vsync.zip (https://www.3dfxzone.it/public/uploaded/koolsmoky/2007811113612_vsync.zip)
1.16 KB
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
thanks koolsmoky :)
PS: i'm really glad to see Osckhar's New World Record with his V6k + AGP2PCI !!!
@KoolSmoky,
8xFSAA does not work well. When It is enabled V6k only works to 4xFSAA.
Oscar
i got severe 2D graphic display issues with photoshop...
sshot:
(http://img207.imageshack.us/img207/8964/20070906204432xl4.jpg) (http://imageshack.us)
in opera's browser too, but i hardly ever have them (in tabs)...
PS: v4500 agp,wXPsp2, same config as glide64's tests
thanks
if i use sfft a48...... no 2D issues...
[:(]
please, anyone with a copy of photoshop, test my issue (zoom an image, browse the menues....)
thanks
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
@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
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.[:p]) 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
QuoteWhat 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
Sorry, both games are D3D. 8xFSAA works perfectly using API Glide, when 8xFSAA is enabled under D3D it works like 4xFSAA. I will try to get some SShots.
Thank you,
Oscar
Hi everybody!
I have a problem with my game/Graphic. When i are gonna play a game ex counter-strike then i can only play in Software mode. And i wan't to play with OpenGL.
It's only works with openGL. COUD SOMEBODY PLEASE HELP ME TO FIND A DRIVER TO OPENGL OR SOMETHING. PLEASE
I have a 3dfx Voodoo4 4500 - AGP
QuoteOriginally posted by Pedersen123
Hi everybody!
I have a problem with my game/Graphic. When i are gonna play a game ex counter-strike then i can only play in Software mode. And i wan't to play with OpenGL.
It's only works with openGL. COUD SOMEBODY PLEASE HELP ME TO FIND A DRIVER TO OPENGL OR SOMETHING. PLEASE
I have a 3dfx Voodoo4 4500 - AGP
hello Pedersen123 and welcome :)
Since you're writing the same problem in 2 different topics, are you using the "driver set for V2/4/5" (see the tittle of this topic) ?
Any news about further development? :)
Greetings from Germany,
Raff