Linked by Eugenia Loli-Queru on Thu 17th Aug 2006 19:05 UTC
DirectX10 is not just another version of DirectX. This version has been re-built from the ground up to change the way applications think about material management and load balancing between the CPU and GPU. D3D10, as also DirectX10 is called, takes advantage of the improved communication between the CPU and GPU and efficiently manages the data transfer between them. Screenshots included.
Thread beginning with comment 153346
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-11-11
It's okay. That was a long time ago.
Yes it was because there was a lag between the release of directx with win95 and the game publishers actually releasing games that used DirectX exclusively with the win32 api that win95 introduced. (Before Win95 there was Windows 3.1(1) which did not have either DirectX or the win32 (32 bit native) protected mode api's.)
Yes for the first several months games didn't use directx because it was so new and not everyone had Win95. At least a year passed before several games worked natively in Windows and DirectX but it happened quicker than I thought it would. Still though, Win95 lived up to its promise as a gaming OS, something that all previous version of Windows failed at miserably.
Even a year after win95 was out DOS games were still being released. Things really changed in 1997 with many games coming out for Win95 or newer (iirc) and not DOS. Games like Total Annihilation, quake2, etc were all Windows native and used DirectX to some degree.
I find it interesting that today we take for granted that major pc games today will be windows native. It simply wasn't always so as you and I remember.