Since DirectX uses COM, the DirectX 7 interfaces (used to call functions)
are still there in DirectX 8, as are the interfaces from DirectX 3 to 6.
DirectX 8 adds it's own set of interfaces, and true they do have reduced 2d
capabilities, but a program written for DirectX 7 won't use any of the DX8
functions, it will just use the DX7 functions as it did when run with
DirectX 7.
Basically, because DirectX is built on the COM model, new interfaces are
added instead of upgrading the old ones. The theory behind this is that it
should give extremely good backwards compatibility, which I guess it does
overall (I think without this method (adding new code instead of updating
the old code) there would be ten times the amount of DirectX problems), .
Of course, when MS release DirectX 8, they also streamline and fish out bugs
from the DX7 code, which can introduce new problems with old games.
It's quite possible that the majority of people who have DirectX8 have never
even seen the DX8 code in action, since there isn't many DX8 games about
yet.
> Here is what I found at Microsoft:
> Migration of Microsoft DirectDraw into Microsoft Direct3D:
> In version 8.0 of DirectX, DirectDraw is fully integrated into Direct3D to
> enable drastically simplified application initialization, improved data
> allocation and management performance, and reduced memory footprint.
> So, if you still have games that uses 2D DirectX, I bet it is better to
stay
> with DX 7a for now as I think a lot of older games will have problems with
> this.
> Brian
> > Hi all,
> > Just downloading DX8 now as DX7 seems to have screwed up somehow - just
> > wondering if there were any compatibility issues I need to know about
> before
> > I install 8? I use a Sidewinder non-FF wheel and play GPL and MBTR, but
I
> > was also wondering about issues with any other games and programs....
> > Cheers,
> > Jim