I had/have a very few time on this week, but
TO THE DGVOODOO 2 TEAM
Thank you, thank you, thank you, thank you very much. The DGVoodoo fix has been working EXCELLENT for players of Jedi Knight: Dark Forces 2 and Mysteries of the Sith.
It's not a team. It's just me. 😀 Anyway, great news! 😎
I would like to report that latest build Windows 10 BUILD 9926 + DirectX 12 + NVIDIA we are having problems with DGVoodoo. I look forward to the next update!
As for Win10, I'm going to wait for the first final release of it. It's true that I mentioned Win10 compatibility in the readme (just for fun), maybe shouldn't have to do that. (But I don't yet know where to install it, I don't want to get rid of the nice UI of Win7. Win10 has the same flat UI like Win8. 😢 )
There are still a few problems with Jedi Knight. When using the -windowgui option (which Steam does automatically) the game crashes very often upon entering the game menu with the fault caused by dxgi.dll. Also the game crashes when you select one of the higher resolutions in software mode.
I'm planning to test all StarWars games myself and see what issues we have there. Currently MotS and Shadows Of the Empire the only ones I tested.
Problem with No One Lives Forever (GOTY Edition): intro videos don't play (but you can disable the videos so no big problem here) and some textures don't show up in-game
NOLF and GTA2 revealed some incompatibilites between dgVoodoo and MS DDraw. I can and will fix those but the bad news is that NOLF uses DXTC (compressed) textures what aren't supported in dgVoodoo. I either implement it or NOLF won't work but it's a worryingly cool game to not deal with it. Anyway, it's an unplanned development. 😵
I also tried MechWarrior3. It suffers from a little incompatibility too, but when I helped it through the problematic part by the debugger then it run and looked beautifully.
The DirectX 2 SDK from http://craig.theeislers.com/ has the d3d docs and binaries, all with the correct dates for DirectX2 ...
Yes, it's a cool blog. I wanted to download those old SDK's from there but the files were removed. 😒
So it looks I did a mistake but I relied on the 'DirectX Then and Now' article in which there is the statement:
DirectX 3 was where we first launched Direct3D, based on the technology of Rendermorphics, a company we acquired earlier that year.
However I could download a preliminary document about a planned driver model for Win9x which contained D3D. Maybe that was included in DX2 SDK, I don't know.