are there any real 3dfx driver sources available? at least something, what could give the first point from start with?
Mesa and other opengl libraries are quite fast and compatible, but the bad thing is that most of games nowdays are in direct3d, and d3d compability is very poor for 3dfx cards :(
The Source has been realized since 1 year now.
Look for on the Web and you will find it.
BUT don't link here the File, thanks.
You can download it from "Removed". It's almost 40Mb. ;)
@PanoramixDruida
This is a pity that you didn't still understand something important :
The Source belongs to NVidia, this is its intellectual property and because this is the Law, nobody can in theory put online and use it.
Remember also (you agreed these Rules):
- "Remember that all information that is disclosed in these areas becomes public information and you should exercise caution when deciding to share any of your personal information."
- "You also agree that you will not post any copyrighted material that is not owned by yourself or the owners of these forums."
The last great 3dfx sites on the Web (and they are very rare now) are not crazy : they don't put online the File but everybody knows where you can find it...
And because This site is the only Site on the Web working on the 3dfx drivers, it wants NO problem...
Is it clear ?
[}:)]
erm, so why didn't you edit his post and remove the link? [?]
QuoteOriginally posted by r21vo
are there any real 3dfx driver sources available? at least something, what could give the first point from start with?
Mesa and other opengl libraries are quite fast and compatible, but the bad thing is that most of games nowdays are in direct3d, and d3d compability is very poor for 3dfx cards :(
Oyes! Which reminds me of this:
http://www.fsf.org/philosophy/no-word-attachments.html
Sorry guys! [V]. I didn't know it. I'll never do things like that anymore [:(]
QuoteOriginally posted by PanoramixDruida
You can download it from "Removed". It's almost 40Mb. ;)
Please Panoramixdruida, use a pvt message for the link.;)
QuotePlease Panoramixdruida, use a pvt message for the link.
Thanks Amiga, but I prefer not to do that. Seriouslly, I didn't realize I couldn't do that. Sorry again guys. It'll never happen again. ;)
thx, I found & downloaded the sources.
Archive actualy include very much sources for building new releases of drivers, is anybody succesfully done it already?
Also I found there BIOS sources, but it seems that they are only for napalm, unfortunately I've only VooDoo3 (avenger) so i can't test them :(
whole structure of archive is a bit hard to understand, but i'm sure it's not impossible :D
QuoteOriginally posted by r21vo
Archive actualy include very much sources for building new releases of drivers, is anybody succesfully done it already?
Yeah, I did it some time ago, although only a shallow approach. I had to puke a week after, from d3d intoxication. There's still a patch on my situ.
However, building the drivers for Napalm is useless, since there is a better core for VSA-100 out there. The guy who leaked the archive provides better binaries than the sources he released. That's a pity, because people has to work hard to reach his binaries' performance first, then overcome them. An unnecessary handicap, IMHO!
QuoteOriginally posted by dborca
However, building the drivers for Napalm is useless, since there is a better core for VSA-100 out there. The guy who leaked the archive provides better binaries than the sources he released. That's a pity, because people has to work hard to reach his binaries' performance first, then overcome them. An unnecessary handicap, IMHO!
so It means that NuAngel's drivers are the fastest drivers for Napalm out there for now? Has anyone asked him about releasing his source to public?
Go ask Reid for his source ;)
This is not NuAngel'core.
Some NuAngel drivers are using simply the last beta core done by Reid Campbell and a Team.
I doubt also that R.C gives a source in public.
QuoteOriginally posted by patience
This is not NuAngel'core.
Some NuAngel drivers are using simply the last beta core done by Reid Campbell and a Team.
I doubt also that R.C gives a source in public.
It's still a pity, nevertheless.
However, newer amigamerlin releases for win9x -- if any -- might be based on this core. And I can assure you we won't use other people's DLLs.
Cheers to whoever manages to read between the lines. :D
QuoteOriginally posted by dborca
QuoteOriginally posted by patience
This is not NuAngel'core.
Some NuAngel drivers are using simply the last beta core done by Reid Campbell and a Team.
I doubt also that R.C gives a source in public.
It's still a pity, nevertheless.
However, newer amigamerlin releases for win9x -- if any -- might be based on this core. And I can assure you we won't use other people's DLLs.
Cheers to whoever manages to read between the lines. :D
:D :D :D Green Evil strike again !!
Can someone point me to the voodoo3 driver sources? Thank you! Please use PM
www.google.com
actualy I don't know do these sources work for v3 because everywhere is only info about v4,v5 in sources..
The Avenger (doodoo 3) stuff should be in the "H3" folder.
QuoteOriginally posted by lecram25
The Avenger (doodoo 3) stuff should be in the "H3" folder.
there were no H3 foder in downloaded archive (39,3 MB (41 238 517 bytes)), there were only H5 folder, so it means that those sources are only for VooDoo5 (and v4 i guess)?
Lemme go check.
EDIT:
WOW, seems that I overlooked that one; it's been a while since I've been in the source. The onyl doodoo3 stuff is located at the sourceforge. Ask dborca.
Assuming that they are the same sources that I got They can be made to work on a V3.
SFFT
No different sources. (http://my.fit.edu/~mmichael/Smileys/dork.gif)
I couldn't find any V3 sources on sourceforge..
anyway's just got a VooDoo 4500 AGP for testing purposes :)
You could, however, try harder...
Checkout glide3x / glide-devel-branch from the CVS.
You'll end up with a complete sourcetree (all 3dfx HW supported).
The "h3" directory is for Banshee/Voodoo3, but it's somehow phased out, as "h5" is compatible with Banshee, Avenger, Velocity, Napalm.
Take it as a homework to try and spot what do "sst1" and "cvg" stand for.
it seems that sst1 = VooDoo1 & cvg = VooDoo2.
i found those sources on sf, but they seem very poor...
QuoteOriginally posted by r21vo
it seems that sst1 = VooDoo1 & cvg = VooDoo2.
i found those sources on sf, but they seem very poor...
That's why you spend time and work on them. Not everything gets handed to you on a silver platter you know. (http://my.fit.edu/~mmichael/Smileys/b3deyeroll.gif)
QuoteOriginally posted by r21vo
it seems that sst1 = VooDoo1 & cvg = VooDoo2.
i found those sources on sf, but they seem very poor...
Yeah, you being so bright, I guess you only had to glance through them and emanate highly specialized opinions, right? If you feel they seem so "poor", grab the keyboard and catch up with some code. I ported the sst1 branch from glide2x, you know, and it works pretty good.
PS: and, btw, you're wrong. sst1 is used for Rush, too.
QuoteOriginally posted by dborca
Yeah, you being so bright, I guess you only had to glance through them and emanate highly specialized opinions, right? If you feel they seem so "poor", grab the keyboard and catch up with some code. I ported the sst1 branch from glide2x, you know, and it works pretty good.
PS: and, btw, you're wrong. sst1 is used for Rush, too.
I didn't ment "poor" as "this code sucks" but as "this code seems uncompleted, like I see too less files to succesfuly compile something, compared to the other sources I got from net, correct me If i'm wrong". I respect your job, and can only say "doh, if i had knowledge like that".
All what I could find out on that sf site was that there is some development going on fixing/merging glide libs under *nix. There were no signs of sources for voodoo stuff for windows.
PS: I'm at beginner level compared to you..
QuoteOriginally posted by r21vo
All what I could find out on that sf site was that there is some development going on fixing/merging glide libs under *nix. There were no signs of sources for voodoo stuff for windows.
Okay. Do not forget to checkout the "glide-devel-branch". The default branch is what 3dfx originally comitted. Anyway, The sources are pretty complete, you just need to write your own makefiles for windows. The current status is like that:
- sst1 - needs win32 makefiles, DOS/Linux ok! Missing some files to compile Rush
- cvg - needs win32 makefiles, DOS/Linux ok
- h3 - needs win32 makefiles, DOS/Linux ok
- h5 - ok