Hello,
i'm interested if there is any progress on DRI TDFX driver. I think that we still doesn't have SLI support on Linux. From Daniel I know that SLI support was planned and former 3dfx engineer have some idea how to implement it.
Maybe would be better to post it on DRI-mailing list,but on this community forum are also skilled developers.Maybe someone would help :)
Hum,
there are some promises... but I dunno.
Anyways, I still couldn't find time to look at Linux since my failed attempt to write the server-side of miniglx for SOLO builds.
Oh,Daniel. Maybe news. Dieter Nuetzel from dri-maillinglist told me that he have a 'late' copy of the tdfx SLI tree.
Do you have the same sources?
I don't know Dieter.
I have the DRI, drm and Mesa sourcetree. I have some other sources as well.
I'm glad to see there are some news, but... I wish I had a nickel for every people that just "had" something. Well, obviously I'm exaggerating. I wish it was true. Capisci?
Yep, I understand you. Dieter promised me that he will send me that sources, so I will forward them to you of course.
Maybe that will help.
THX for your work Daniel.
I've updated the TDFX driver today. I haven't had the time to look into the DRI guts (hence SLI not working yet), but the driver itself worked pretty good on Mesa demos, GLExcess, Quake3 and UT2k3 demo.
Hello Daniel,
I tested your changes with a DRI snapshot from 20040722. With little time for testing I already see improvements in some things, with exception of a game called FooBillard (http://foobillard.sunsite.dk) (seems lighting problems, but I am a newbee in 3D :-) ). Well, I have not tested version 3.0 of the game before, but version 2.9 was running nice in Linux, with just one problem with the menu. The menu problem might be big texture sizes, according with the FAQ, but versions 2.9 and 3.0 of the game run without problems in Windows. I have Voodoo 3 3000 AGP 16MB, Windows 98 and Slackware 10.0, tested with Glide provided by distro and with binary release 3.10.00.30303 from glide.sf.net. A compiled package of the game for Slackware is available from http://www.linuxpackages.net. May be problem with Glide, DRI driver or Mesa? Do you have an idea?
Hi mateuscg,
Hehe, I'm running Slak, too :D
You have to understand a few things: about one year ago the TDFX driver was more advanced than the regular Glide driver. Since then, I worked only the Glide driver, totally neglecting TDFX. I thought it was time to fix it now, based on my experience, so it was only a week-end job. Please report me as many demos/games/apps as you can, preferably small pieces.
To whom it may concern: if someone has DEMOS from popular games, please send me the executable part only. Usually, the textures/data are shared between Win & Linux versions, and this would spare me from downloading hudreds of megs twice. Remember, I need DEMOS only.
EDIT: hmmm... about FooBillard... I wonder how did it work with previous DRI driver on Voodoo3. Because 2.9 and 3.0 use large textures for menu entries. The sw_rescale_hack is not enabled in TDFX yet. Anyway, it's kinda dumb, cos it doesn't test for max texture size. And even dumber because it's the first game I've seen that uses a separate texture for each menu entry. 99.9999999% of games out there "compose" text using small textures, each representing a letter.
QuoteOriginally posted by dborca
Hi mateuscg,
...
Please report me as many demos/games/apps as you can, preferably small pieces.
I have only few apps to test: a Quake 3 demo, Tux Racer, Racer, emulators..., but I'm a very bad lucky guy because if something could go wrong, it would go wrong in my computer :-). Seriously, I hope someone else can test intensely this new DRI driver to make sure everything will run right.
Quote
EDIT: hmmm... I wonder how did it work with previous DRI driver on Voodoo3. Because 2.9 and 3.0 use large textures for menu entries.
Well, I need to clarify some things here: menu entries didn't work in versions 2.9 and 3.0 with Linux, only worked with Windows. The problem existed with previous versions of TDFX driver, before your recent changes. This game showed new problems, other problems, with your changes and I tested version 3.0 again to take some screenshots.
With Windows, works perfectly:
(//../public/uploaded/mateuscg/200472725522_foobillard-win32.jpg)
With TDFX DRI driver provided by distro (Slackware 10 - X.org 6.7):
- I haven't looked in config options to see if the white sides of the table are problems or not. There are two problems here: the menu entries and a black band in the field of the table that moves according of view angle. The black band didn't happen in version 2.9 with Slackware 9.1.
(//../public/uploaded/mateuscg/200472725939_foobillard-dri-slackware-10.jpg)
With TDFX DRI driver from 20040722 snapshot:
- The black band problem is fixed, but problems other than menu entries appeared, I think are lighting problems.
(//../public/uploaded/mateuscg/20047273055_foobillard-dri-20040722.jpg)
(//../public/uploaded/mateuscg/20047273149_foobillard-dri-20040722-2.jpg)
Quote
The sw_rescale_hack is not enabled in TDFX yet.
Menu entries showed right with Windows, so this is the method used by Windows drivers? Will fix the problem in Linux?
I'll try to look into the matter.
Yes, the SW_RESCALING_HACK does the job for Windows. Which MesaFX were you using?
Daniel, it's posible to make a control panel for all these options (sw rescaling, FXT1 to NCC conversion, other options...). Maybe also in Windows, because V3 3000 with it's small VRAM need some of these features. I mean for change on-the-fly or after a reboot.
Athlon 1700+
256 MB
V3 3000 AGP
Mdk 10.0CE/BeOS 5.0/W 98SE
QuoteOriginally posted by piriu
Daniel, it's posible to make a control panel for all these options (sw rescaling, FXT1 to NCC conversion, other options...). Maybe also in Windows, because V3 3000 with it's small VRAM need some of these features. I mean for change on-the-fly or after a reboot.
The Mesa Control Panel does this job.
I see you're on W98SE. After hitting OK / Apply, you have to restart the filemanager (if any) or the open windows.
QuoteOriginally posted by dborca
I'll try to look into the matter.
Yes, the SW_RESCALING_HACK does the job for Windows. Which MesaFX were you using?
I'm not using MesaFX. It's a "clean" Windows 98 install, with last official driver from 3dfx (1.07.00) and with last Glide3x release from glide.sourceforge.net (3.10.00.30303). If necessary, I can try with MesaFX, no problem, just have not installed it yet because I haven't used something that requires special features provided by MesaFX.
Mateus
Good news, I tested dborca's recent changes with a recent DRI snapshot (20040904) and the FooBillard regression bug was fixed.
(//../public/uploaded/mateuscg/20049515910_foobillard-fixed.jpg)
The menu issue is the only problem left.
Daniel, I was testing some video players in Linux and discovered a problem: some settings are not available with the TDFX 2D driver. The driver doesn't support the minimum recommended XV (XVideo) atributes: XV_ENCODING, XV_HUE, XV_SATURATION, XV_BRIGHTNESS and XV_CONTRAST (taken from XFree86 server 4.x Design (DRAFT): The XFree86 X Video Extension (Xv) Device Dependent Layer). With your knowledge of 3dfx programming, could you take a look at this or give a tip about how this could be implemented (by example, which register could be changed to adjust the brightness setting)? I have found a patch for XV atributes implementation in Radeon cards and it didn't look too difficult, so maybe I can do the same in TDFX driver, but need some tips.
it just might be your lucky day/week/month. i'm almost finished transition from the windoze to the good ol' slack! :D so expect news in the linux area... ehm... more or less - as time permits.
Any clues on how long before you can have a peak at SLI, and perhaps get it working? Kinda up in the air right now if the old V5 or the GF2 is going in my spare box, linux sli support would tip me towards the V5 (even tho I know it wouldn't have all the features and crap the GF2 would).
have a peak? maybe today...
but make SLI working? hard to tell...
i wish i could get it done as quick as possible.
QuoteOriginally posted by dborca
it just might be your lucky day/week/month. i'm almost finished transition from the windoze to the good ol' slack! :D so expect news in the linux area... ehm... more or less - as time permits.
What to say to this news??? ....
VIVAT VIVAT VIVAT Daniel!!! ;)
Great news Daniel! Also, could you take a look at this mail list archive, please?
http://www.mail-archive.com/xmame%40toybox.twisted.org.uk/
It's a list about an emulator that has support for compile against Glide2 or Glide3 (other build options exist). The program tries to use Glide directly and, according with the docs, can be compiled to run from X (executable gets xfx sufix) or from console (executable gets svgafx sufix). There are two recent threads about Glide. One thread with pleople talking about a missing grBufferSwap function in Glide3 for Voodoo3/4/5. Too bad they are submitting patches to Red Hat and Debian mantainers and not to Glide mantainers :-(. Other thread talks about the "grSstSelect: non-existent SSTF" error when trying to run the emulator with Glide3 under X, since Glide already is used for DRI support. Can an application uses Glide3 directly under Linux? Must Glide be compiled without DRI support in this case?
voodoo3/4/5 (2D+3D core) must use DRI. they have no need of grBufferSwap, because they use grDRIBufferSwap. using glide directly might be problematic.
however, Guillem - the Debian maintainer - just fixed grBufferSwap yesterday. he's in our team. i am not interested in redhattish linux flavors. [:p]
daniel i have tried to install the linix driver on falconflys site
which i thought was the same driver on 3dfxzone.it.im running 4.5
linspire and it is a debian build .when i overwrite the dri and the
drm and the glide files at reboot it wont boot into linspire anymore .
Its possible that the rpm file gets corrupted in some way using alien.
Is the falconfly driver and the 3dfxzone driver the same ro are they
different builds?I bought wine x hoping that my voodoo 5 could be
utilized.the site has a voodoo 3 driver but does not have a voodoo 5 driver.any help to get this to work would be appreciated.i am a newbie
to linux but im interested in learning as much as i can.so its
possible that i doing something backwards in my installation.
QuoteOriginally posted by recoton
daniel i have tried to install the linix driver on falconflys site
which i thought was the same driver on 3dfxzone.it.
I haven't been on falconfly site for quite a while now. dunno what version his archive carries...
Quoteim running 4.5
linspire and it is a debian build .
i'm running slak, so i might not be of much help. i don'tr even know what linspire is. you could try to contact Guillem Jover - just google for him. he's quite a nice guy and has some background contributing to the 3dfx community.
Quotewhen i overwrite the dri and the
drm and the glide files at reboot it wont boot into linspire anymore .
Its possible that the rpm file gets corrupted in some way using alien.
oh boy, anything but rpms. is this a breed of redhat? i suppose you don't have a console boot mode? that is the only solution that springs to mind.
QuoteIs the falconfly driver and the 3dfxzone driver the same ro are they
different builds?I bought wine x hoping that my voodoo 5 could be
utilized.the site has a voodoo 3 driver but does not have a voodoo 5 driver.any help to get this to work would be appreciated.i am a newbie
to linux but im interested in learning as much as i can.so its
possible that i doing something backwards in my installation.
okay, anyone with some linspire/debian/rpms/winex experience could help recoton? heloo?!?
Hello recoton,
I use Mandrake linux 10. I also have WineX(Cedega). If you want to utilize your voodoo you must just use DRI drivers from your distro and you MUST have libglide3.so (or similiar) library that has DRI support. I think that you can find it on glide.sf.net. DON'T overwrite anything, DRM depend on kernel! If you will change DRM you must compile it from DRI CVS. Daniel did some progress on TDFX driver so you can try his updates from MESA CVS. Much better performance in RTCW:ET [8D]
Linux Doom 3 Client/Server Binaries and Demo Released:
http://zerowing.idsoftware.com/linux/doom/
-------------------------------------------------------
Minimum Specs:
GNU/Linux system,
Pentium III, 1Ghz
256Mb RAM
Kernel 2.4, 2.6 is recommended
glibc 2.2 and up
3D card:
NV10 or R200 minimum hardware
OpenGL hardware acceleration
64 MB VRAM
sound card + OSS ( with mmap support )
-------------------------------------------------------
Would be hard to implement MesaFX hacks into Linux to get Doom3 running with Voodoo 5?
QuoteOriginally posted by mateuscg
Linux Doom 3 Client/Server Binaries and Demo Released:
http://zerowing.idsoftware.com/linux/doom/
YAY! Doom3, feel my wrath! [}:)]
Quote
-------------------------------------------------------
Minimum Specs:
GNU/Linux system,
Pentium III, 1Ghz
256Mb RAM
Kernel 2.4, 2.6 is recommended
glibc 2.2 and up
3D card:
NV10 or R200 minimum hardware
OpenGL hardware acceleration
64 MB VRAM
sound card + OSS ( with mmap support )
-------------------------------------------------------
yea-yea-yea...
QuoteWould be hard to implement MesaFX hacks into Linux to get Doom3 running with Voodoo 5?
are you kidding? but there _IS_ a problem... without SLI in Linux, it could get a bit slower...
PS: fork it! the ftp server is dying with 421 (too many users).
PPS: got the linux version. ;)
PPPS: got the win32 update. ;)
lol, Daniel, Linspire is the new name for Lindows;)
I dunno if MS filed a lawsuit and forced them to change the name, or just asked 'em to, but they did.
I did finally get the voodoo 4 driver to work on my voodoo 5 .when i used the 3dfx source code on the linspire site it made a special
debian file and after install the file it actually worked .i dont know if it mingeled with the other file thet i tried to install before or if it really came form the linspire 3dfx source.i couldnt find anybody on the site that had a voodoo 4 o5 5 installed.it seems to be fast and stable though.I still hoping for sli.Also microsoft tried to sue lindows for the name but in turn was counter sued by
lindows and probaly get a big pay off to chage there name to linspire,
which sounds better anyway.pretty solid linux build .
Just thought I'd mention the facts on the whole lindows/windows thing. Microsoft sued for trademark violation. Lindows sued stating, truthfully, that it was illegal to trademark a generic english word. Microsoft realized that they didn't want everyone and their brother to start stomping all over their trademark(after it was rightly declared void) and made a few quiet proposals to the Lindows people. They both dropped their cases, Lindows changed their name voluntarily, Microsoft "bought" the Lindows domains, and a few other lindows related domains for big money. Lindows gets a better name and the company gets a large cash injection, Microsoft doesn't have to try and defend their illegal trademark in court.
@amp
oh, yes... :) i remember now...
@Shogakusha
damn, that's a good lesson! [:0] impressive! [^]
Hello Daniel, was the sources of SLI tree from Dieter usefull for you?
umm.. sorry, haven't got the time to toy with it...
some other news (might or might not be of any interest): the doom3 is tested and works with the TDFX driver, but only with shadows disabled. the build will be out in a few days.
That is really good to hear that. Will it be available as binary package?
QuoteOriginally posted by vykupitel
That is really good to hear that. Will it be available as binary package?
yes, namely tdfx_dri.so! i might release the patch, too... i dunno...
QuoteOriginally posted by dborca
QuoteOriginally posted by vykupitel
That is really good to hear that. Will it be available as binary package?
yes, namely tdfx_dri.so! i might release the patch, too... i dunno...
Damn ! I really want both SLI and Doom3 support (Better SLI w/o Doom 3 than only Doom3, i have Win98 for that monster butt kickin' stuff). It's not good to have three chips just for more noise and heat. :D
QuoteOriginally posted by vykupitel
Hello,
i'm interested if there is any progress on DRI TDFX driver. I think that we still doesn't have SLI support on Linux. From Daniel I know that SLI support was planned and former 3dfx engineer have some idea how to implement it.
Maybe would be better to post it on DRI-mailing list,but on this community forum are also skilled developers.Maybe someone would help :)
hi , im in the forums already
QuoteOriginally posted by edmundoab
hi , im in the forums already
ehm... <scratches on the back of my head>... is this a good thing, or a bad thing?
ps: just kidding :D
pps: i have a bunch of nicknames - in my closet - from coder wannabees that made similar assertions. i ate them all. :D
Are there any news Daniel?
hey, I still don't have the money to offer a purchase of the Rev 3 :(
sorry.
anyway, I don't know whether I am going to be good news or bad news in the forums.
But I am happy to meet other 3dfx enthusiast around.
At least I don't feel so odd that I am having a weird hobby, ( as what my friends labels me :( )
Do you know what's the tdfx driver ? [?]
You're off-topic...
Daniel, DRI part of Linux driver lacks a mantainer, so do you want to have these honor? And maybe you can implement in Linux: sofware rescaling and s3tc to NCC conversion, because with today computing power this could be a significant speed gain.
sorry, no progress in this area. i've been busy with other things.
QuoteOriginally posted by piriu
Daniel, DRI part of Linux driver lacks a mantainer, so do you want to have these honor? And maybe you can implement in Linux: sofware rescaling and s3tc to NCC conversion, because with today computing power this could be a significant speed gain.
1) sw rescaling will be done
2) NCC is not useful in any way. it is not part of any OpenGL spec, and cheating texture compression with NCC is a BadIdea -- too slow and too ugly. it will be completely removed from MesaFX, too! i think cheating with palette quantization can still be an option. the difference between NCC and palette is the size of codebook (which is not a problem, anyway)
3) technically, i _AM_ the maintainer of TDFX driver (obviously, since I did most of the important work in the recent past). if i ask Brian to put my name there, that won't help anyone more than it helps now. but would burden me instead, since i'd have to look at it regularly - and that might or might not be possible. i will think about it, tho...