What's new:
- Fixed and improved driver installer.
- Fixed some D3D issues.
- 3Dfx Tools TemporalAA support enabled. (Special Glide3x lib
download required).
- Full v5 6000 support.
- Updated glide/opengl libs (finally the Evo's v.1.00.09 issues are
fixed).
- Improved performace and mainly compatibility with Dx8.x and Dx9.x
games.
//www.evolutiondrivers.cjb.net
[8D]
coooool :D (i'm downloading)
ps: DBorca's TemporalAA Patch Setup does this: replaces your \system's glide3x.dll with the TAA one :) (remember to back up the another one [8D])
Alright, possible stupid questions here:
What version of windows is this update for? Win9x or WinNT/2k/XP?
Secondly, I'm curious if you can do anything for adding support for FF7pc into the drivers in some way without compromising anything. Or, heck, maybe just support for having the Duck Truemotion codec run (in a DirectShow5 context, mind you).
It appears that all display drivers that are newer than version 4.12.01.0543 have some incompatibility with either FF7pc or Duck Truemotion that causes me to get only the audio track of the Eidos Logo movie (It's impossible to get the game to ignore trying to play the movie, so I can't tell if the problem's with the codec or the game) with a black screen, followed by a hard lock. The codec works fine when used outside of the game (i.e., ran from windows media player).
Furthermore: the same thing happens in software mode! Which is why I think it might be occuring in the portion of the drivers responsible for DirectDraw itself, and not merely the Direct3D portion.
I should also mention that even your Evolution Driver (ver. 1.00.09 for Win9x) is not immune to this, either. I haven't tried 1.00.16 yet, but I'm hoping that it somewhow works.
QuoteOriginally posted by Ragnarok72
Alright, possible stupid questions here:
What version of windows is this update for? Win9x or WinNT/2k/XP?
Secondly, I'm curious if you can do anything for adding support for FF7pc into the drivers in some way without compromising anything. Or, heck, maybe just support for having the Duck Truemotion codec run (in a DirectShow5 context, mind you).
It appears that all display drivers that are newer than version 4.12.01.0543 have some incompatibility with either FF7pc or Duck Truemotion that causes me to get only the audio track of the Eidos Logo movie (It's impossible to get the game to ignore trying to play the movie, so I can't tell if the problem's with the codec or the game) with a black screen, followed by a hard lock. The codec works fine when used outside of the game (i.e., ran from windows media player).
Furthermore: the same thing happens in software mode! Which is why I think it might be occuring in the portion of the drivers responsible for DirectDraw itself, and not merely the Direct3D portion.
I should also mention that even your Evolution Driver (ver. 1.00.09 for Win9x) is not immune to this, either. I haven't tried 1.00.16 yet, but I'm hoping that it somewhow works.
all evo's drivers are for 9x based system .
QuoteOriginally posted by kaneda-san
all evo's drivers are for 9x based system .
Ok, then. Time to install.... ;)
However, my question regarding FF7pc/Duck Trumotion codec still stands.
Well I have done a quick test with the driver, and it certainly fixes the problem with Colin McRae Rally 2, which was running very slowly. Graphic corruption still exists in MachWarrior 4 Mercenaries. Il2 Sturmovic still seems very slow, I think that this is texture download related, and the DX 8.1 SDK Environment Mapping Cube Map Sample still shows corruption (This is an extended vertex format parsing problem). You might want to look at these issues. All of the above are DirectX problems.
SFFT
Ok!..
I'll take a look soon... I really need more free time now. [^]
tried commandos3,to see if the problem is still there (all characters were invisible once the game entered the hybrid 2D/3D mode-basically in any exterior.weird,because the game runs fine even on a matrox400 card).ther problem is still there[xx(]..well actually with evo you are able to see something,small texture corruptions where the characters are supposed to be..if you turn on 4x FSAA,grey boxes will appear on those places where characters are supposed to be,and this makes the game somewhat playable (yeah!),althought its still pretty annoying (diehards only).I have been playing with 3da a bit,and I have some info,I'll post screens today..
ok,here are the screens (latest evo,voodoo5):
3d only works fine (interiors):
Image Insert:
(https://www.3dfxzone.it/enboard/../public/uploaded/ps47/2004101122037_normalgameint.jpg)
30.94 KB
2d/3d hybrid mode (exteriors),evo dislays something (standard drivers dont show anything),that two colored stripes are the green baret:
Image Insert:
(https://www.3dfxzone.it/enboard/../public/uploaded/ps47/2004101122254_normalgameext.jpg)
75.64 KB
exterior in window (3danalyze),desktop set to 16-bit:
Image Insert:
(https://www.3dfxzone.it/enboard/../public/uploaded/ps47/2004101122423_windowgame16bit.jpg)
81.35 KB
no change,looks like the standard game (stripes are less wisible,and disappiered because of image compression,but they are there.)
exterior in window,(3danalyze),desktop set to 32-bit:
Image Insert:
(https://www.3dfxzone.it/enboard/../public/uploaded/ps47/200410112254_windowgame32bit.jpg)
66.68 KB
forcing 32-bit colour FIXES THE CHARACTERS,but screws the backround[xx(]
normal fulscreen,evo driver 4x FSAA enabled:
Image Insert:
(https://www.3dfxzone.it/enboard/../public/uploaded/ps47/20041011221837_4xFSAA.jpg)
83.14 KB
oh yeah,we have gray boxes for characters!off to play the game;)
conclusion:the game exteriors backgrounds are 16-bit.the characters are however 32-bit,and for some weird reason,voodoo5 cant render the background in 16-bit and the characters in 32-bit at the same time.
possible fix: force 32-bit rendering for all hardware accelerated textures (or something similar) option in D3D options/3dfx tools..
(thinking about it,it may need exactly the opposite-convert all 32-bit textures to 16-bit..)
I can be wrong of course..;)
Hey Raziel, I found a new bug! ;) Although, I'm assuming this exact game issue hasn't been brought up yet, so if it has, then, uh, I guess nobody's released a fix yet despite it already being brought up. [:p]
My Config: Evolution 1.01.16 set, on a V5 5500, in Win9x.
The name of the game is Star Trek:Bridge Commander. If I use 2xFSAA or noFSAA mode, I have support for the "Enhanced Glows" feature of the game, and it works well. HOWEVER, if I try to use the "High Color" mode in the options and play the game, I get this:
Image Insert:
(https://www.3dfxzone.it/enboard/../public/uploaded/Ragnarok72/2004102923557_STBC_32bitRender.jpg)
64.2 KB
And yes, it'll do that even if I enable Force 32bit Rendering in the 3dfx Tools.
But.....if I run the game with 4xFSAA on I lose support for the "Enhanced Glows", but the "High Color" mode works as it is supposed to:
Image Insert:
(https://www.3dfxzone.it/enboard/../public/uploaded/Ragnarok72/20041029235751_STBC_32bitRender_4xAA.jpg)
75.41 KB