First, let's set the scene here. After coming up with enough willpower to actually use my computer instead of playing
Metroid Prime, I decide to download and install DirectX 9. Why? I dunno. Considering I'm already screwed in driver support because D3D8.1 totally fails on my 3Dfx Voodoo3 2k PCI card, I figured I'd at least benefit from any enhancements or optimizations that are in D3D7 and in the DirectSound and DirectMusic areas.
After letting it install, I fire up the good ol' "dxdiag" program, to see what new stuff it sports. As Aaron has mentioned to me in another thread, the most noticible difference they've done is ask you whether or not you want Dxdiag to see if your Audio and Video drivers are WHQL signed. Just for the heck of it, I clicked "Yes", and it does its check and starts up like normal.
But ya'll already know that stuff.
So I'll cut to the chase:
I'm getting some interesting behaviour in the "Display" and "DirectMusic" tabs of DxDiag. First off, when I ran the D3D7-interface test, I think I broke some speed records for my card, as I just saw it render at like
4000 FPS. On a Voodoo3 PCI.
Of course, there's not much to render in that test, since it only consists of a textured, spinning cube, but its funny as heck to watch it cause screen tearing as it goes so fast.
Next up, is the D3D8/8.1-interface test. Naturally, it fails.
Then, it throws me a curve ball.
It passes the D3D9-interface test, and is giving me similar speeds in rendering compared to the D3D7 test. Yes, reality seems to be having an "off day".
I've yet to test any of the newer DirectX games yet; I'm gonna try out Star Trek: Armada 2, as it takes the role of being "Acid Test for Hardware D3D8-compatibility".
As if that wasn't enough of a shock, when I go to test the DirectMusic interface on the Microsoft Synth, after I click the test button, the program locks up. After "End Task"-ing it, Win98SE gives me the first BSOD I've seen in 3-5 months. -_-
At any rate, things now look a bit more promising in my V3 2k PCI's future.