Slashdot Mirror
The End Of DirectX As We Know It
socram writes "Speaking with ATI and NVIDIA at ECTS allowed us to confirm that after DX9.0, DirectX Graphics is no more. In name only. Microsoft's next set of core presentation and 3D APIs are now under the umbrella of Windows Graphics Foundation and Avalon. Microsoft will still rely on DirectX in name for the rest of the core components, but the graphics API is now under a new name. Look out for WGF 1.0 compatibility on the back of that next generation graphics card's box. Some WGF 1.0 Info!" Update: 09/06 22:27 GMT by T : David Ross of hexus.net points out that this text comes straight from hexus, and should have been credited as such.
This is a boat load of hogwash. DirectX is here to stay. DirectX is the damned core, Avalon, or whatever the heck they end up calling it is simply a layer on top of DX. But don't take my word for it, google it. There is enough info out there, that anyone that knows how to program for DirectX will immediately realise that it is being modified with the new UI in mind. It's being done to help it hook into DirectX, and if you examine the DX API closely (especially the latest SDK release), you'll notice a trend to add APIs that allow features that are required for a fully integrated UI. And at the end of the day, game developers will still be using the DX api.
---
Programming is like sex... Make one mistake and support it the rest of your life.
No, it's the gamedevelopers that does that for you by checking for if your card supports the features it needs to be playable.
It's not MicroSoft's fault, by any extension, it is however silly that you are not allowed to check if it is playable according to _your_ standard; and it's the gamedevelopers you should blame.
I guess it's easy to point at something big, like MS if you want someone to blame, people tend to do that.
Actually the whole graphic subsystem was in userland in Windows NT 3. It was bulletproof but slow and it did not allow the low level hw access needed for DirectX, so they moved it into kernel with NT 4.0. And I'm quite sure it will stay there.
Does anyone have a pointer to more detailed technical specs on this? Like the reference manual for writing a compatible driver?
main(O){10<putchar(4^--O?77-(15&5128 >>4*O):10)&&main(2+O);}
Two things:
1) that page, judging by the date at the bottom, is 7 years old - that's plenty of time for the situation to have completely changes
2) judging from the logo on it and the URL, the guy is particularly anti-MS; you might want to cite a source with a little more objectivity
It's official. Most of you are morons.
As a historical note, Halflife added D3D support at some stage, even though it was based on Quake1/2, which was also OpenGL (and Glide & Software) based.
That being said, it was probably a lot easier to add at the time than with current engines, which implement a lot more features.
And he almost decided to kill it off. According to Carmack, the "godawful interface" for OpenGL pBuffers/Render to Texture, made him be "the closest ever to switching over to D3D".
If you are interested in listening to an hour of video-graphics supergeeky stuff, download the one hour video of his keynote from Quakecon 2004.
It contains an hour of tech-talk from John C. about the doom3 engine, and what he's working on now.
- OpenGL (Direct3D)
- OpenAL / CoreAudio (DirectSound)
- Quicktime (DirectShow)
- OpenPlay (DirectPlay)
- HID Manager (DirectInput)
I may have missed a few things. WGF is roughly equivalent to OpenGL / Quartz Extreme and everything else that DirectX does at the moment, while Avalon is equivalent to Aqua / WindowServer. Of course, the differences in architectural designs mean that these equivalencies are only very approximate.I am TheRaven on Soylent News
Back in the early 1990's, Microsoft saw the re-emergence of console systems, and realised the PC platform was under threat. After consulting with many game developers, the one complaint that kept coming up was the lack of a consistent interface to control hardware. Game developers had to write their own drivers to support all the different sounds cards, video cards and CPU's that were available. So Microsoft announced a set of of libraries that would give programmers direct control of the hardware without needing to resort to hardware programming. This set of libaries became known as DirectX.
Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads