I tried alpha46 under WinXP x64 and the results are very impressiveUT99 works perfectly in Glide mode, the framerate is 60fps constant but i hadn't activate vSync; in windowed mode the game turns in software rendering without any adviceAlso FreeSpace2 works well in Glide rendering, but it have some LOD problems: far ships appears black, when closing the textures appears fadingOther DX games works like under WinXP x86

I keep having problems with Glide under WinXP x86, even after i used Driver Cleaner; maybe i should format...

Btw: World of Warcraft runs without big bugs on a Voodoo3 with Alpha 46. When I had tested the game maybe one year ago, there were many texture problems (on Voodoo5 too). They are gone with present drivers, but the shadow maps are white instead of black and you can't see the ability icons ... I think it's due to hardware limits.

Is possible to give feedbacks about GLide based games, comparing SFFT current release performance and compatibility to those of some previus versions like SFFT Alpha 45 or minor?

Thanks in advance.

Bye Bye

After Alpha 42 any Glide app. nor even initializes. I'm using a V3 2K (my 3K burnt ) w/ Win2K SP4 + Update Rollup + all fixes. DirectX 9.0c version is the most recent one before April's update. The "problem" probally resides on the main drivers, because de Glide libraries are the same.

I've attached a DrWatson log in wich I was trying to run ePSXe with Lewpy's plugin (works ok w/ Alpha 42 or below).

You should be able to run any glide combination you want with the sfft drivers. The ones that are shipped with it are the only ones I have found that run under Win XP 64 and also are the only ones I have seen that run Arifix Dogfighter ok. You can always run other glides if you have problems with specific applications.

About GLide games on Win32 OSes, as SFFT writes, we can replace GLide libraries packed with Alpha 46 using other stable releases. It isn't a big problem because we will not have new Glide games ;)

Good posting,

Bye

Yes, I tried it but without success. I tested SSFT 46 either with the offical 3dfx Glide libraries (the last ones released for 2k/xp) or the ones shipped w/ the drivers. I also tried the Koolsmoky releases. The point is that any Glide 3x library works w/ SSFT 43 and above. It simply crashes (with an ilegal task). In other hand, every single library I've tried w/ 42 and below does work perfectly.

It's quite weird . A question: Is the Glide access somewhat managed by the display driver or the applications can access it directly? Isn't it supposed to be a independent API?

Well that is odd, the supplied drivers definitley work, under 32 bit aswell as 64 bit, I seem to recall that the Glide Xp releases used with AmigerMerlin work aswell under 32 bit. It has been a while since I tested them. The supplied ones are based on Koolsmokeys anyway, so Koolsmokeys should work. If other glides have problems with bad Handle issues, then they may not work. the Process Handle interface is no longer supported, so older versions of glide may be broken. The glide interface is not driver independant no user mode interface to hardware can be. I suspect that you may not be testing with the glide dll's that you think you are. At least 3 of them should work. I can't say that I tested the last 3dfx w2k releases, I think that I tested XP compatible ones, as I seem to recall that the Process Handle Interface doesn't work under XP anyway, at least I think that I saw that claimed in one of the Glide sources, which incorporated code to get round the issue.

These four crashes with 43 and above (yes, I tried w/ all of them, both Glides and display drivers) but do not with 42 and below. Maybe under 2K environments the display driver (or Glide?) needs this old Procces Handle Interface to correctly manage Glide routines, whereas under XP alternate access methods can be used, since de Handle Interface doesn't work properly. Do you remember of have done any significant change on display driver or Glide 3x library after 42th release?

The problem is that I have tested these on Win2k, or at least 3 of them and they work. What card are you using, and how are you testing them, i.e. with what programmes. I presume that if you are using a native glide application that they will be using glide2 anyway, and my opengl testing (which uses glide3x) works. The later glides emulate the process handle logic internally so should work without its support in the driver, and as someone has pointed out UT99 works on X64 without the Process handle interface, using the same glide dlls that are used on XP and W2k.

I just have 2 applications that can uses Glide atm: ePSXe (with Lewpy's Glide 3x plugin) and a Nintendo 64 emulator (Project64/1964/etc) using Glide 64 plugin (wich also uses Glide3x). Both of them show the same odd behavior.

Well, to test I delete "3dfxvs.dll" and "glide3x.dll" from System32 and "3dfxvsm.sys" from System32/Drivers directories, substituting them with the desired version to test. So I reboot the system and run DxDiag tool to check if the drivers were correctly recognized and are in use. The only combination that produces a successfully result is Alpha 42 or below w/ any Glide 3x library.

This driver works better than the windows xp driver.Some games that wouldn't work before will run now.Other games that worked fine have serious problems with this driver.I get incorrect textures drawn on the characters in the game.This example image is from one game that didn't work at all before the driver update. It appears fine in windowed mode, but in full-screen it appears as shown on the right.

It might be best not to mention the game titles here. I could e-mail them if necessary.Are there any adjustments that might correct this kind of problem?If not, I hope at least this info can be of some value to future improvements.