Slashdot Mirror


The People Behind DirectX 10

ThinSkin writes "In the first of a three-part series covering the people behind the new DirectX 10, ExtremeTech interviews Microsoft's David Blythe and Chris Donahue to discuss the development, decisions, and future of the new API. They answer several questions such as how different it will be than DX9, why it will only be for Vista (and not for XP), and when we might be able to see it."

24 of 352 comments (clear)

  1. What will their NEXT version be? by mi · · Score: 5, Funny

    It better not be called "X11"...

    --
    In Soviet Washington the swamp drains you.
    1. Re:What will their NEXT version be? by $RANDOMLUSER · · Score: 5, Funny

      I heard they were thinking of calling it "ClosedGL".

      --
      No folly is more costly than the folly of intolerant idealism. - Winston Churchill
  2. Duh by csplinter · · Score: 5, Funny

    "questions such as how different it will be than DX9, why it will only be for Vista (and not for XP)"

    Oh... I don't know... It couldn't be so people will buy vista.

    1. Re:Duh by Anonymous Coward · · Score: 5, Informative

      This is going to be an annoying flamewar on Microsoft by a bunch of people who didn't RTFA.

      I was about to comment as well on how Microsoft just wanted to force people to upgrade, but read the article and you can see it was the driver model of the older systems that was the problem. Microsoft took the Apple approach of making things better instead of sticking to the broke, buggy design of Windows that all of you seem love(I am talking about the 97% of you). Honestly, this falls right in line with all the news about Vista(driver and kernel re-designs)

      So, to re-cap... The designers chose to not be hindered by the older design decisions and to look towards the future.

    2. Re:Duh by TubeSteak · · Score: 5, Informative

      According to TFA, it has something to do with their new driver model, meaning less driver running in kernel mode.

      That somehow ties into virtualizing access to the graphics hardware.

      You can read the specifics on this page
      http://www.extremetech.com/article2/0,1697,1982033 ,00.asp

      P.S. The Printer Friendly page on extremetech leaves out pictures & perhaps more importantly, leaves out their captions.

      --
      [Fuck Beta]
      o0t!
    3. Re:Duh by Utopia · · Score: 4, Informative

      It says right in the article that DX10 supports the new Vista driver model (which has user mode execution etc.)
      Porting it to XP would means having support XP's driver model as well.

      Supporting two different driver model means more complexity and less things added to DX10 in the same timeframe.

    4. Re:Duh by csplinter · · Score: 5, Insightful

      "Supporting two different driver model means more complexity and less things added to DX10 in the same timeframe."

      Yes but, I don't really consider time frame a "technical reason" as far as this goes. Thats more of an economical reason, wouldn't you agree?

    5. Re:Duh by Anonymous Coward · · Score: 5, Insightful

      The changes to the Windows driver model have far more to do with DRM than any stability issues.

    6. Re:Duh by gowen · · Score: 4, Funny

      Well, you see, thats the trouble with Windows.

      There's so many different distributions available that fragmentation between them is inevitable. ;)

      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    7. Re:Duh by TheRaven64 · · Score: 4, Interesting
      The point of an API is to hide the implementation details. A Direct3D programmer doesn't have to know whether they're using an Intel, ATi or nVidia chip, for example, in order for their code to work. This is called abstraction. Similarly, they don't need to know how the driver is implemented; with DirectX 3, there were widely different driver models on NT 4 and Windows 95 implementing the same API. With OpenGL, the Windows, Mesa and IRIX implementations are hugely different, and yet they still implement the same API.

      If your user-visible API dictates the structure of your drivers to the extent that you can't back-port it to another driver model, then you're doing something deeply wrong. Or you're using technical buzzwords to confuse people into thinking that a management decision is a technical one.

      --
      I am TheRaven on Soylent News
    8. Re:Duh by Anonymous Coward · · Score: 5, Insightful

      Yes but scroll down. These jokers think developers will be doing DirectX 10-only games within 2 years. Not only does that presume that Vista will actually be out in 2 years, it also presumes that Vista will be so massively successful in this timeframe that 90% of gamers will have it on their systems thus justifying a DirectX 10-only policy from publishers.

      This is the stuff of which dreams are made. i.e. it's not remotely plausible. Look at the stats on w3schools, for example. Today, June 2006, 89% of Windows users are on XP. XP has been out for 4 years and it doesn't even make that much sense today to ignore Windows 2000 users. There are still as many W2K users as Mac users and the "port" from XP to Win2K is easy enough to make it worthwhile. Not many people would make an XP-only program today.

      Two years ago, XP was on 57% of Windows machines - i.e. after 2 years it achieved 60% market share. No-one, two years ago, made XP-only software for end users.

      Which OS to put DX10 onto is not a technical decision. The commercial realities forbid a Vista-only API unless MS want to wait five years for DX10 to be widely accepted by end-users.

      In other words, they will put DX10 onto XP or DX9 is all we will get from most publishers until 2010. Few developers have the resources to target two versions of DX at once.

    9. Re:Duh by flithm · · Score: 4, Insightful

      You make a point, and I wouldn't argue that you're wrong, because you're not. But in the software development world getting away from anything that adds more complexity is generally better for the overall health of the system.

      Adding the ability to support two driver models would have a dramatic influence on the design of the project and would likely force them to go in a totally different direction. It's not that it's not possible to do, it's just that it would likely be quite detrimental.

      Personally speaking I give them a salute for finally doing something right. They're evil anyway so why does it matter? Just consisently do what's best for the software and eventually people will be okay with the decisions.

    10. Re:Duh by heinousjay · · Score: 5, Insightful

      They're evil anyway so why does it matter?

      Because so many people here have tied their self esteem up in the success of Linux and the consequent failure of Microsoft that they have to bitch about everything.

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    11. Re:Duh by andi75 · · Score: 4, Insightful

      > A Direct3D programmer doesn't have to know whether they're using an Intel, ATi or nVidia chip, for example, in order for their code to work.

      HAHAHA! Best joke I've heard in a while. You obviously haven't been programming with D3D a lot.

      It's absolutely vital that you check Vendor ID, Device ID, and Driver version in order to work around the countless bugs, quirks, and performance holes in all the well known broken systems out there (unless you absolutely want to slap a BIG 'only supported on Card X with (at least) Driver Y' STICKER on your packaging).

    12. Re:Duh by mrchaotica · · Score: 4, Insightful
      And wouldn't DRM be safer in kernel mode anyway ?

      I'm not sure what you mean by "safer" but the DRM would work more effectively, which is why they're putting it there. The design goal is to have a "Trusted" kernel running on "Trusted" hardware, so that the system can disallow any software-based circumvention technique -- including device drivers that tried to save the framebuffer to a file. That's both the reason why most drivers are going to run in user mode, and why the rest have to be "certified" by Microsoft. Certification isn't about quality; it's about DRM enforcement.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  3. That's an interview? by Netochka · · Score: 5, Insightful

    Seems more like a bunch of pre-approved PR junk... Some sample 'questions':

    A lot of people are complaining, "Oh, why won't we have DirectX 10 for Windows XP." There's a good technical explanation for that, where it's really not possible to do what DX10 does in the Windows XP driver model."

    So if the decision had been made, "Yes, we're going to try to make all this work on XP," you'd really have to sort of hamstring DirectX 10. You'd have to say, "Then we can't do this, we can't do that..."

    You could even see the graphics card having a big hand in doing some of the stuff that was traditionally done on the CPU. Things like collision detection, or calculating obscured geometry so you don't have to render it. You start to see a lot of flexibility in how developers can use both the geometry shader and the stream-out-to-memory function together.

    Video is another area where you're starting to see the graphics card manufacturers doing a lot of fun stuff with their video processing using the power of the GPU. And you could see DX10, especially with the reduced overhead, enabling more powerful video processing on the graphics unit.

  4. Why should DirectX 10 support Windows XP? by cperciva · · Score: 5, Insightful

    From the comments so far, it seems that people feel that Microsoft is somehow failing in a sacred duty by not making DirectX 10 available for Windows XP.

    Why should Microsoft make DirectX 10 available for old versions of Windows? How many new video drivers released for Linux in 2006 support early 2.4.x kernels?

    Sometimes making progress means saying "sorry, we don't support that; you'll have to upgrade to something newer".

    1. Re:Why should DirectX 10 support Windows XP? by Jugalator · · Score: 4, Insightful

      Microsoft still has an obligation to (legal) users of XP.

      Oh, so they still have?

      Where is the formula to decide how much service depending on product cost a company should give to their consumers?

      Because Microsoft has already supported their XP users for years in non-essential software to use the OS. For how much longer should they do so? Many here seem to know the answer because they seem to say Microsoft is doing something wrong here. Please don't leave out the details for me and give me the date.

      If this was essential updates and about security, stability, and so on, the answer would be simple: during the product lifetime that Microsoft sets up for all their operating systems. But this is glitz to play some new games.

      --
      Beware: In C++, your friends can see your privates!
  5. DirectX & Antitrust by 10Ghz · · Score: 4, Insightful

    Why have we had lawsuits about media-players and the like, while something like DirectX has been left alone? I mean, DirectX (or more precisely: Direct3D) is replacing OpenGL, especially in games. And DirectX runs only on Windows. Doesn't that mean that porting those games to other platforms would end up being very difficult, and if you wanted to play games on your PC, you practically needed Windows (well, that's true even today, but the reasons for that are elsewhere).

    In short: authorities were concerned about Microsoft dominance in the web-browser market. And they have been worried about Mcirosoft dominance in the media-playback market. Yet they are not concerned about DirectX and the dominance it gives to Microsoft? How come?

    --
    Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  6. What obligation? by spoco2 · · Score: 5, Insightful

    I mean really? What obligation are they under? You have a copy of an operating system that runs everything it's supposed to now and in the immediate future. There was nothing in the deal that said "Your copy of Windows XP will continue to support the bleeding edge games for 10 years after we release it".

    Come on.

    How many programs only run on Mac OSX and don't run on OS9?

    I hardly see how a finger is being given at all here... and it's not like you haven't had fair warning that Vista is coming out.. hell it's late, late, late... so there's no big 'whoops I bought XP because I didn't know Vista was coming out'.

    The main deal is that Vista will still run all the XP stuff, so you haven't had the 'finger' given to you for buying XP, because when you do upgrade to Vista down the track you won't have to upgrade all your software as well if you don't want to... that would be giving the finger... kinda like how Apple did with OSX not really supporting old OS9 programs.

    Man, Microsoft can do no right by some people, no matter how hard they actually do try.

  7. Re:MS says no to openGL by omicronish · · Score: 4, Informative
    DirectX10 and Vista also means Microsoft will drop support for OpenGL in Windows.

    Not true; see Kam VedBrat's comments on Vista and OpenGL support. To summarize, Microsoft will provide an OpenGL 1.4 implementation that sits on top of Direct3D, legacy (XP-era) OpenGL ICDs are supported but will disable Aero, and new OpenGL ICDs may be written that works with Aero.

  8. Finally ate their own words... by Antony+T+Curtis · · Score: 4, Informative

    I remember when Microsoft Windows NT 4 was released with its new in-kernel video drivers. Critics of OS/2 were saying how much better it would be than OS/2 which had the video drivers working in user mode - as DLLs loaded by Presentation Manager.

    Sad truth, although it was easily demonstrated that DIVE was faster than DirectX on the same hardware, practically no games were ever written for OS/2 with people citing the critics.

    Hopefully with the new driver model, they can address one of DirectX's big shortcomings which has existed since its beginnings - blitting graphics with an obscuring window intersecting it. With DIVE, the fps increases as there is less pixels to blit. DirectX the performance goes down as it makes heavy work with many more kernel-mode/user-mode transitions. Of course, to solve this, Windows games opted for full-screen mode so that there will be no obscuring frames above the window ... but it rather limits the multitasking ability of the system turining it into a fancy DOS.

    When I used to play games, I rather enjoyed having the game run in a window next to my wordprocessor... Excellent for turn based games like Civilization.

    --
    No sig. Move along - nothing to see here.
  9. Give me a break! by xtracto · · Score: 4, Insightful

    What's keeping MS from backporting some of the new Longhorn kernel/driver niftiness to XP? Oh, right. Money. There's no money in adding new things to an already-sold product. It's all about selling the new hotness.

    So, one of the first complains I read over here about Windows is how they have been carrying a legacy of compatibility from Win 3.11 days. Now, they try to simplify the platform (didnt Mac did that when going from OS9 to OSX?, and from PPC to Intel?) and everybody starts whining.

    What is keeping Microsoft from backporting is the complexity it would yield, Windows XP is a mess, thats why they had to restart the development of Longhorn to a new model. They decided to throw away the compatilibity and improve the technology.

    I do not know how good or bad will vista be, I use Fedora anyways, but I think there is just so much bullshit people can throw at Microsoft, IMHO they are *trying* to do something fine, for a change.

    --
    Ubuntu is an African word meaning 'I can't configure Debian'
  10. This is slashdot... by LordEd · · Score: 4, Funny

    You don't need to back it up. All you need is Microsoft and DRM in the same sentence to get +1 insightful.