Notice ~ 

Are you searching for our italian Community  Forumzone.it?
Main Menu
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

Topics - Gemail

#1
Please, I ask for help from advanced users or driver writers!
I use in one PC two 3DFX video cards: one Voodoo 3 3500TV AGP and one Voodoo 4 4500 PCI. I need them both, as I use the V3 3500TV for the TV-Tuner (I have no TV or money to buy one or another TV-Tuner PCI card), plus for it's speed, and I need the V4 4500 for playing games that need texture compression or large textures support (and although it's slower than playing with V3 3500, FSAA does look great with V4!).
In Win 9x enviroment I have no problem to use both Voodoo's. The only conflict would have been when the DirectX drivers would have been shared, but I figured that out by "trial and error" and I found out that if I use for example the original 3DFX drivers for Voodoo3(DirectX driver-files names end up with *V3.* rather than *VS.* like for Voodoo4) there are no more problems.
But in Win 2000 enviroment is another story... All the drivers have the same names for files both for V3 and V4 (*VS.*) so the system will lock when trying to be active both of them at the same time adressing the same driver files. The solution would probably be to edit the .inf files and change the names of the driver files so there will be no sharing. I'm not so experienced myself for that task, so can somebody help me solve my problem, please?
Would it work if I follow the following steps to change the Voodoo 4 driver?
1. Extract the driver.
2. Change the names of 3dfxvs.dll and 3dfxvsm.sys to 3dfxv4.dll and 3dfxv4m.sys.
3. Open the 3dfxvs2k.inf file and search for the "3dfxvs" text and where found replace with "3dfxv4" for every instance found.
4. Install the moddiffied driver.
Any suggestions are more than wellcomed! Thanks in advance!
#2
Hi! Please help me again by sharing your experiences :)
There are some games that alow displaying of a FPS counter (frames per second) in one corner of the screen. There is also the program named "FRAPS" that should do that too. But my problem is that the verssion of FRAPS downloadable at www.fraps.com only works in Win XP enviroments and I use Win 9x, plus that lost of games have no such option built in. Now, I won't install Win XP only to get FRAPS working; I'm very happy with Win 9x; but I need to know the FPS I get with different settings for many games I play, including DirectX, OpenGL and Glide. I hope you might know some generic FPS counter that works with Win 9x and displays ingame the FPS number in one corner of the screen so you could give me a hint where to download it. Or maybe you have an older verssion of FRAPS that runs on Win 9x and you could upload it for me...
Please help, any sugestion is greatly welcomed!
#3
For all I knew by now, this special T-Buffer effect that is the Temporal Anti-Aliasing, also named as Motion Blur should not be able to perform on a Voodoo 4 4500 PCI. I saw on various documentations that the only T-Buffer effect Voodoo 4 is capable of displaying is the Full Scene Anti-Aliasing 2x (FSAA2x), as this boards are single chip solutions. On the other hand, Voodoo 5's, as they are double or quad chip boards are able to do not only FSAA 4x/8x, but also TAA (Motion Blur).
To my big surprise, playing the game MotoGP2 with my Voodoo 4 4500 PCI (PC verssion, 1xVSA100 @166Mhz, 32Mb SDRAM) - courthesy by Rolo01, this special effect popped-out:

800x600 - tumbnail

resized to 400x300
It looks like Motion Blur to me, the game's readme clearely states that this special effect will be displayed on video cards that support it, but how is it possible for a single chip Voodoo 4 to do Temporal Anti-Aliasing?
#4
Hi!
Could you recommend a screen-shot utility program that works with 3DFX cards (Voodoo 3, 4, ...). I would like it to be able to capture screen images in games on Direct3D (DirectX) but also on OpenGL and Glide. The key I set in the 3DFX Tools doesn't work at all in Direct3D and in Glide works with a small number of games (mostly it doesn't), so I need a third-party solution ...
Links for available suitable downloads would be greatly appreciated!  ;D
Thanks ...  ;)
#5
Hi all,
My main problem? There are no updated drivers for Windows 9x/ME, especialy for Voodoo 3 Cards.
My solution? Mix 'n' match from newer drivers glide libraries, OpenGL ICD's, etc...
But I need help from more experienced users than myself, so plese give me somme hints :D
For all I know, there are 3 main parts of a voodoo driver: the DirectX core (D3D), the glide libraries and the OpenGL ICD.
I will try to take updated parts from other driver packages to mix with one base voodoo 3 driver.
What I need to know:
In what driver release can I find the latest Glide 2.x (not Glide 2.x to Glide 3.x wrapper), Glide 3.x and OpenGL ICD? Of course, the files doesn't have to be necessary from one single package.
I was thinking taking the latest Raziel Evolution driver for VSA100, as this one has the most tweaks configurable (virtualy every enviroment variable can be set into 3DFX tools), then overwrite on top DirectX (D3D) core from Amigamerlin 2.9 driver (12.1.666 is the latest core suitable for Voodoo3 in Win9x) or maybe 3DHQ (hmm, not so good feedback), then also add the best new glide libs and the ICD.
For OpenGL, MesaFX 6.3.0.1 seems as a good solution, but although all have the same version, the ICD from Amigamerlin 3.1 R11, from SFFT 32 and the one downloadable from dborca's web page have all diferent sizes, so they are not identical neighter in functions ...
About Glide ... I'm allready dizzy ... so many releases, ... numbering is bogous ... Help will be greatly appreciated. As I stated, I want real Glide 2.x not wrapper.
Please, do not hesitate to trow here advices from your personal experiences :) Tank you!
#6
I tried everything I could think off trying to run Delta Force Black Hawk Down with my Voodoo 3 3500TV 16MB, even 3DAnalyze, different drivers, editing .cfg file, but no luck. Damn, one friend of mine played the game on his onboard 8MB video (KLE133)! This is stupid, you cannnot compare this joke of pseudo-video card he has (as I remember, Trident onboard) with mine "beast" (compared to his)! No T&L on both, no DirectX 8 compatible on both ... realy strange!
If anyone knows a "magic touch" to make the game playable on a Voodoo 3 please share it. I'm a big fan of Delta Force series so I realy want to play Black Hawk Down.
#7
Can anyone help me with a description of 3Dfx enviroment variables (I want to know what each one do). For example, what is the effect of dither_rotation? Thanks.
#8
Although Voodoo 3 series are no match for modern standards, I supose there still are users out-there trying to make the most out off this wonderfull piece that is the "Avenger". I'm very happy with my V3 3500TV-PAL, although lack of suport for PAL-D TV-Tuner standard in Win 2000/XP drivers forces me to be limited to Windows Millennium Edition.
There are drivers updated to the curent days in 2000/XP enviroments (thancks for that to the wonderfull men doing this job) but for all I know, support for Windows 9x seems to have been discontinued for quite a long time, sadely ... :(
My questions are, so please Voodoo3/Win9x users please post here, the following:
- The latest drivers core for V3 and Win9x seems to be found in Mikepedo 1.1 release, indeed with a good DirectX 8+ compatibility, native DirectDraw Interface 8.x, but realy buggy (running for example 3DMark 2001 SE build 330 produces odd black and white textures). Why dosn't anybody develope this core? Mikepedo gave up?
- The final (and last) releases of Win9x drivers for V3 that I know about are Amigamerlin 2.9 and 3DHQ beta10 and those are 2,5 years old. Is anybody curently working at a new driver set for Win 9x or this is a lost cause? Too bad if so, Win9x seems to be the best enviroment for gaming with Voodoo cards.
- I want to ask you, Voodoo3 and Win9x users what driver release are you using, witch one gives the best results?
Thank you!
#9
Please help me since I am a novice ...
In MesaFX 6.2.0.2 release there is no "conventional" package like in 6.2.0.1 and previous. There is no glide.dll, only opengl.dll. If I refer to MesaFX tutorial, I need the corect glide.dll for using with opengl.dll. What should I do? Take the glide.dll from 6.2.0.1 package and use with opengl.dll from 6.2.0.2 package? Should I use only the opengl.dll from 6.2.0.2 (no need now with this new release for glide.dll?); if so the tutorials for using MesaFX are now out-dated, do not aply and if so where can I find the new instructions?
From your previous experience what is the "best" MesaFX release in terms of performance and compatibility?
Thank you!
#10
MesaFX / Mesa 6.3 ?
21 May 2005, 15:34:16
This is my first post here, although I have been reading this forum for quite some time, so please excuse my poor english...:)
On Daniel Borca's homepage is available for download a Mesa pre-release labeled 6.3.
http://www.geocities.com/dborca/
As I know, the latest Mesa in 3dfxzone archive is 6.2. Is the one on dborca's homepage a newer release?