[RandomTiger]

Originally posted by Inquisitor
I think SCP will stick with dx8 for the foreseeable future.

Sounds right.

You need the new .NET dev environment for dx9, and I see no reason to buy that just for this [/B]

Not sure about that, I have a DX9 appwizard for VC6 which seems to work nicely. Or is that not what you mean?

[Grey Wolf]

You have to remember, also, that the vast majority of GPUs don't really support DX9. Everything up through GF4 Ti4800 and the Radeon 8500. And the bargain DX9 cards (like the FX 5200 and it's ATI equivalent) apparently don't handle DX9 very well either, but this (unlike with the other cards) isn't because of the hardware not being designed to handle it. Rather, it's due to the fact that they are slow and are about an equal performance-wise with the GF4 MX cards.

[Descenterace]

I'm using the DX9 SDK with VC6.  If you want to use VB with DX9 though, you need VB.NET.

AppWizard?  I don't use no stinkin' AppWizard... even though there is one available.

My own DX9 experiments work very well at the moment.  Debugging fullscreen mode on a single computer is hell, so my graphics engine will be windowed-only until I get the bugs ironed out.  My hacked-up Direct3D app framework is performing very nicely though, with none of the overheads inherent in the AppWizard framework.
So far, the program draws a rotating, textured, lit cube with material effects.  I'm using the program's general mesh stack for the cube object, as the ship and AI stacks aren't finished yet.  The general mesh stack is used for things such as debris and asteroids.

So DX8 uses the same VC++ API as DX9?  I wish I'd known that when I started writing the Quantum Reality engine...  Does DX8 have the geometry functions that DX9 has?

[Inquisitor]

Oh, I guess I am running on old info about the .NET stuff. Good to know I don;t have to spend the bucks to upgrade.