Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

The People Behind DirectX 10 352

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."
This discussion has been archived. No new comments can be posted.

The People Behind DirectX 10

Comments Filter:
  • by Netochka ( 874088 ) on Wednesday June 28, 2006 @01:57AM (#15618841)
    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.
  • Re:Duh (Score:1, Insightful)

    by Firehed ( 942385 ) on Wednesday June 28, 2006 @01:57AM (#15618843) Homepage
    So... keep the old stuff broken, and jack up the price of a marginally-better product that does something to improve the situation? Helluva reason not to make XP forwards-compatible.

    Now let the flamewar begin :)

  • Re:Duh (Score:5, Insightful)

    by csplinter ( 734017 ) on Wednesday June 28, 2006 @02:15AM (#15618917) Journal
    "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?
  • by cperciva ( 102828 ) on Wednesday June 28, 2006 @02:22AM (#15618945) Homepage
    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".
  • by kihjin ( 866070 ) on Wednesday June 28, 2006 @02:38AM (#15618992)
    Microsoft still has an obligation to (legal) users of XP. These users supposedly paid for a product. Basically Microsoft is giving the finger to it's XP consumer base. Although, no surprises there.

    The Linux kernel can be freely downloaded at http://kernel.org/ [kernel.org] I don't think upgrading to Vista will be a zero-cost venture, especially since the hardware requirements are excessive.
  • by 10Ghz ( 453478 ) on Wednesday June 28, 2006 @02:41AM (#15619001)
    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?
  • Re:Duh (Score:3, Insightful)

    by I'm Don Giovanni ( 598558 ) on Wednesday June 28, 2006 @02:49AM (#15619034)
    What's really "funny" is that people (slashdotters and their ilk) criticize Microsoft when they backport tech from Vista to XP, saying, "Well, there's no reason to buy Vista then". Yet when Microsoft doesn't backport tech from Vista to XP (like DirectX 10), you guys still bitch.

    Which is it? Do you want Vista tech backported to XP or do you want Microsoft to keep Vista tech exclusive to Vista?
  • What obligation? (Score:5, Insightful)

    by spoco2 ( 322835 ) on Wednesday June 28, 2006 @02:50AM (#15619038)
    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.
  • by Jugalator ( 259273 ) on Wednesday June 28, 2006 @02:50AM (#15619043) Journal
    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.
  • Re:OpenGL (Score:4, Insightful)

    by I'm Don Giovanni ( 598558 ) on Wednesday June 28, 2006 @02:53AM (#15619053)
    Why don't MSFT simple submit a proposal to extend OpenGL in a open way?

    Why *should* they? And don't answer with some ideological doctrine, give a *practical* reason why Microsoft should do what you propose. DirectX has been wildly successful without any submissions to extend OpenGL.
  • by Anonymous Coward on Wednesday June 28, 2006 @02:59AM (#15619069)
    The X11 drivers run in user-mode. The Kernel module is only a interface to the hardware. The bulk of the [graphics] drivers are user-mode.
  • by xtal ( 49134 ) on Wednesday June 28, 2006 @03:01AM (#15619076)

    Why should Microsoft make DirectX 10 available for old versions of Windows?


    In one swoop, they've condemned people to upgrading if you want to play games on the dominant PC gaming platform. Do you see why that might irritate a few people? Vista sure isn't going to be free.

    What's going to cost more? Vista or an Xbox 360?

    On the other hand, that'd remove my main reason for not saying screw it all and moving to an x86 mac for everything. My existing PC plays all the games I'm going to have time for for the next few years recently. So maybe it's not a bad thing at all! I've stuck with Windows 2000, I haven't moved to XP yet, as all my CAD and design files work fine..

    Microsoft intends to play a game of market thermonuclear war to get Vista integrated and entrenched ala XP/2000. Fortunately, that's the type of war that could also leave their market share in smouldering ruin just as easily as it will reinforce it.

    Mark my words : The less technical ground Vista has to fight on, the nastier the marketing efforts are going to be.

  • by Jugalator ( 259273 ) on Wednesday June 28, 2006 @03:14AM (#15619105) Journal
    The full Windows XP lifetime doesn't apply to updates not essential to run the OS itself well, so DirectX has little to do with Microsoft's lifecycle policies beyond the mainstream support. This ends at earliest this year; 5 years after the product has been released. After this, the product enters the extended support phase, but then mostly just security updates and paid support is available. Customers can find out this policy before purchasing any Windows version to decide what OS is right for them and if Windows is appropriate for their scenario at all.

    The Windows XP end of life has not been decided according to their pages, and is not necessarily in 2009.

    I'm also a bit unsure of exactly why hardware upgrades requires some sort of obligation by the vendor to have their software be backwards compatible? (your opinions about this matter seem to go in that direction) Do you believe this because it is proprietary software? Would you not ask for this if it was an open source OS? Is the obligation a moral one? Proprietary software ethics? But in that case, do you also request that computer game and software applications should scale back well to support older hardware because otherwise they'd be doing an immoral act of breaking functionality with older hardware? Or does this only apply to proprietary operating systems, like Windows and Mac OS?
  • by Flyboy Connor ( 741764 ) on Wednesday June 28, 2006 @03:36AM (#15619174)

    Basically, DirectX is meant as an Interface between Windows and (Video) hardware. It says "if you call my function xxx, I will translate that to a certain call to the hardware". It is terribly easy to make DirectX 10 compatible with XP. You just take DirectX 9, add the new calls, and let them return "sorry, I cannot do that". Then game developers will simply add an option "activate advanced DirectX 10 features" to show off the cool stuff, but any XP user will still be able to play the game. So there is no good reason to exclude XP from the new games market, as Microsoft is trying to do.

    Even better, they could (and IMHO should) open up the source code of DirectX. I am dead certain that an XP version of DirectX 10 would be created in days.

    But of course, they have great MARKETING reasons why they will not do that. Yes, it is all marketing. The rest of the argumentation is blah.

  • Give me a break! (Score:5, Insightful)

    by xtracto ( 837672 ) on Wednesday June 28, 2006 @03:38AM (#15619183) Journal
    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.

  • by datafr0g ( 831498 ) * <datafrogNO@SPAMgmail.com> on Wednesday June 28, 2006 @04:00AM (#15619257) Homepage
    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?


    Because nobody's being forced or tricked into using DX to play games - the people who made the game made the choice and that choice is entirely up to them.

    If MS locked down Windows so that only DX API's could be used (no OpenGL, etc) then there'd be cause for argument.

  • Re:Duh (Score:5, Insightful)

    by Anonymous Coward on Wednesday June 28, 2006 @04:21AM (#15619315)
    The changes to the Windows driver model have far more to do with DRM than any stability issues.
  • Re:Duh (Score:3, Insightful)

    by ultranova ( 717540 ) on Wednesday June 28, 2006 @04:46AM (#15619382)

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

    Why would a program using an interface be affected by what mode the code behind the interface runs in ?

  • Re:Duh (Score:5, Insightful)

    by Anonymous Coward on Wednesday June 28, 2006 @05:57AM (#15619547)
    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.
  • Re:Duh (Score:2, Insightful)

    by webvictim ( 674073 ) <`ten.mitcivbew' `ta' `sug'> on Wednesday June 28, 2006 @07:45AM (#15619805) Homepage
    The fact that Microsoft are making DX10 only for Vista doesn't surprise me in the slightest. Yes, it's because the whole driver structure has been changed... but it is also rather convenient for them.

    Microsoft: "You must upgrade to Vista because DirectX 10 will not work with Windows XP, due to a new driver architecture." Me: "I see... but surely that means you're just attempting to pull more money out of me and other Windows users by our eyeballs. After all, I wouldn't upgrade to Vista otherwise because I've used the beta and it was slow as hell. It concentrated so much on "pleasing" visual effects and transparency that it took twice as long as XP to do even the most menial tasks. My computer is not below average by any means, would you care to explain why I'd buy a new operating system that would slow my computer down rather than keep the existing one which works just fine for everything I want to do?" Microsoft: "Uh... well, it'll be more reliable." Me: "I've had uptimes on Windows XP of three weeks before now without rebooting. In fact the only reason I reboot at all is to install new drivers for a piece of hardware or something like that. That's quite reliable enough thanks, given that the majority of people (not slashdotters, naturally) turn their computers off every night so don't even need that extended uptime." Microsoft: "Oh. Well you won't be able to play new games like Halo 2 without Windows Vista." Me: "That doesn't concern me. Why should I upgrade?" Microsoft: "Because it'll put another £100 in Bill Gates' coffers." Me: "I thought so!"

    The Vista beta was horrific. Yeah, sure, they're going to fix some of the problems before the final release, but the truth is that it rated my computer 3/5 for hardware performance when I have a 256mb Geforce 6600GT, 1GB of RAM and an Athlon XP 2800+ processor. My computer runs faster than anyone else's I know, even those with faster processors and the same amount of RAM. What the hell do you need to get 5/5?

    I'm digressing, but the point is that Microsoft are just attempting to grab our money. They won't be getting mine, that's a sure fact.

  • Re:Duh (Score:4, Insightful)

    by Fred_A ( 10934 ) <fred@f r e d s h o m e . o rg> on Wednesday June 28, 2006 @08:06AM (#15619877) Homepage
    Since the display drivers have apparently been mostly moved to userland, there will probably be lots of stability issues (positive ones hopefully).

    I'm not a Windows users as such (I only use it to play games every now and then) but since for once they did seem to make a good decision in that specific area, it shouldn't be downplayed... regardless of how much fun it is to diss Microsoft in general...

    And wouldn't DRM be safer in kernel mode anyway ?

    Keep the bashing for when it's justified, it's not as if there aren't enough occasions to indulge, especially with Microsoft.
  • Re:Duh (Score:5, Insightful)

    by flithm ( 756019 ) on Wednesday June 28, 2006 @08:20AM (#15619940) Homepage
    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.
  • by Weedlekin ( 836313 ) on Wednesday June 28, 2006 @08:55AM (#15620133)
    You seem to be forgetting the fact that new computers are still shipping with XP, and will continue to do so until Vista comes out (whenever that is). If it launches on the projected date (yes, I know this is unlikely), this will mean that a lot of machines bought over the XMas 2006 season will have an OS that MS will start treating as obsolete a month later. IMO the way they handle this could affect how a _lot_ of customers relate to them in the future: if for example they offer free upgrades for all PCs bought within 90 days of the product launch, and a heavily discounted one to six month-old installations, most people will be reasonably happy; trying to milk such users for a full upgrade would however piss many of them off.
  • by Aceticon ( 140883 ) on Wednesday June 28, 2006 @08:56AM (#15620140)
    The problem here is that, with the help of their 95% share of the PC market, MS has made DirectX the de facto abstraction layer for games on the PC.

    Since MS will not fix issues with older versions of DirectX after they start distributing a new version, game developers are pushed into developing their games to the latest DirectX version.

    So via this mechanism, MS makes sure that game developers use MS' chosen DirectX version.

    By making DirectX 10 to be Vista only, and since they have locked-in game developers to the latest version of DirectX, it's actually MS (which sold you XP) which is making sure that in the future you will have less use of XP.

    For clarity, here's an analogous situation:
    - Imagine that a washing machine manufacturer, after selling millions of v1 washing machines, had (somehow) made an agreement with all detergent manufacturers so that (somehow) any new detergent batches they made could not be used in v1 washing machines, only in the "new and improved" v2 machines.

    In this situation would you not hold it against the washing machine manufacturer since they had no responsability in making sure that the older washing machines worked with the newer detergent batches?

    The issue here is that, to get what they payed for (play games/clean clothes), consumers need a base component and a consumable, both coming from two different sellers (OS, game/washing machine, detergent). If, knowingly, the seller of the base component makes it so that, some time after the sale of that component, there will be no more consumables available for it, then said seller is knowingly decieving their customers.

    That's what MS is doing here.

    There are only 3 possible outcomes:
    • Game developers break their bond to the latest version of DirectX by dropping DirectX and using OpenGL. This would be great for cross-platform interoperability of games in general and specifically for gaming under Linux
    • Users drop gaming on the PC and concentrate on consoles for their gaming needs
    • Consumers pay the MS tax ... again


  • by pbhogan ( 976384 ) on Wednesday June 28, 2006 @09:45AM (#15620486)
    That's a noble sentiment, but what's likely to happen is game developers will stick with DX9 until the overwhelming majority of their customers switch to Vista (which could take a while), or they'll have to write their own DX9/DX10 abstraction layer. Either way it's a pain and the responsibility really should be Microsoft's for writing a compatibility layer for XP. DX10 should be a crossover model, not a throw everything out the window model (no pun intended). Perhaps by DX11 enough people would be using Vista to justify saying it should only run on Vista. Microsoft has been releasing more than one DX version per Windows version, so that's not an unfair way of looking at it. If anything, Microsoft will be hurting their developers and in fact chasing them toward other solutions like OpenGL for graphics and only using the bare necessities from DX for input, etc. DX was already limited to one (admittedly market majority) platform, but now it's narrowed to a single operating system? Personally I don't need user mode execution for my 3D shaders, thanks all the same.
  • Re:Duh (Score:5, Insightful)

    by heinousjay ( 683506 ) on Wednesday June 28, 2006 @09:52AM (#15620548) Journal
    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.
  • DRM? (Score:3, Insightful)

    by The MAZZTer ( 911996 ) <.moc.liamg. .ta. .tzzagem.> on Wednesday June 28, 2006 @09:53AM (#15620569) Homepage

    Hardware accellerated desktop, display drivers that can restart themselves if they crash, less reboots to install new drivers, multiple hardware accellerated windows, virtual memory for video cards.

    Obviously those are all features intended to overshadow the main new feature... DRM!

    Sorry... sarcasm doesn't translate well over the internet...

  • Re:Duh (Score:3, Insightful)

    by demachina ( 71715 ) on Wednesday June 28, 2006 @10:07AM (#15620669)
    " The designers chose to not be hindered"

    So instead they chose to hinder application developers, especially game developers, with two choices:

    A. Design for DirectX 9 and not use any DirectX 10 specific feature
    B. Adopt DirectX 10 and abandon any potential customer not running Vista which will be more than half of their target market for a LOOOONGGGG time

    If they opt for B, and I wager a future version of HALO will opt for B, then we can switch to hindering consumers. When the game they want to buy runs best on or requires DirectX 10, but unfortunately the consumer has 2000 or XP what do they do. There is a 50/50 chance the hardware they have wont run Vista or run it well. So at this point, to run a 50 dollar game the family has to buy at a minimum the Vista retail upgrade package, or worse a whole new computer.

    I'm glad the DirectX engineers aren't hindered, because everyone else will be, you know like just all their customers.

    It is a basic reality today, most consumers DON'T NEED Vista or new hardware to run a web browser, email and office apps. PC's have reached a level of power that is overkill for what most people use them for. 3D games are one of the few applications that are pushing new hardware and software sells for Microsoft and Dell. Therefor it follows that DirectX is the best avenue to compell Vista sales for Microsoft, and new hardware sales for manufacturers, especially for high end machines that have better profit margins. Since Microsoft controls a fair number of game titles they can try to use them to drive Vista upgrades, at the risk of alienating some customers from their game divisions. But then too a lot of gamers are fanatics for spending huge amounts of money on their computers and graphics cards
  • by ameline ( 771895 ) <ian...ameline@@@gmail...com> on Wednesday June 28, 2006 @10:16AM (#15620750) Homepage Journal
    Re Closed GL...

    David Blythe used to be an architect in the advanced systems division of SGI. Very sharp guy. (If I recall, he even fixed a couple of gl bugs I found on the (now old) infinite reality engine.)

  • Re:Duh (Score:5, Insightful)

    by andi75 ( 84413 ) on Wednesday June 28, 2006 @10:35AM (#15620937) Homepage
    > 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).
  • by PhoenixPath ( 895891 ) on Wednesday June 28, 2006 @11:26AM (#15621373)
    A lot of people here seem to be operating under a major misconeption.

    DX10 is *not* a DX9 patch. Yet you're asking MS to make DX9 DX10 compatible?

    Microsoft has *never* backported to an older product compatibility for a *new* anything. Ever. Tehy have in the past on occaision provided backwards comptibility in a *new* product, but they have *never* modified an *old* product to support a new model.

    DX10 will simply *not* work in XP using XP's driver model. They would be forced to backport the driver model of Vista. This is an absurd expectation.

    Does a new Linux kernel backport it's improvements to a previous kernel? Hell no.

    This is amazing. I have *never* seen a group of people so blinded by their dislike of a company to expect them to do something *no-one* does.

    Apple doesn't do it, Red-Hat doesn't do it, Blizzard doesn't do it, and you expect, no, DEMAND that Microsoft do it.

  • Re:Duh (Score:5, Insightful)

    by mrchaotica ( 681592 ) * on Wednesday June 28, 2006 @11:38AM (#15621496)
    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.

  • by kimvette ( 919543 ) on Wednesday June 28, 2006 @12:34PM (#15621912) Homepage Journal
    why it will only be for Vista (and not for XP) is:

    They need a compelling reason for people to buy the upgrade.

  • by NRAdude ( 166969 ) on Wednesday June 28, 2006 @03:02PM (#15623174) Homepage Journal
    Every sentence was constructed of frontpage Slashdot topic. I'll confirm it for you all, peice by peice:

    No one but the poor sods still doing x86 pc game development give a damn about directx.
    true: Simple Direct Media Layer, openAL, and Mesa are all cross-architecture and cross-platform compatible with 100% documented API and daily updates.

    The pc market has been in decline for over five years now and there is no sign it will ever recover.
    neither true or false: wherever there is economically-available software and an acceptable user-interface to that software, the people will choose.
    And it is going to get a lot worse as MMORPGs continue to eat up pc game players gaming budgets of time and money.
    conditionally true: modern MMORPGs have proven to be designed for addiction, more than satisfaction; a good MMORPG would agree with a user's will to let down the game and continue about his life with a schedule that isn't violated by entertainment; satisfaction that is decided by unique skill and technique more than variable enhancements of random tools collected in the artificial environment that do less to enhance the scene and more to abbrogate and upset the ballance of responsive interaction by the user. Think of Diablo 2 and Everquest: both are repetitive, addictive, have no technique to play other than collecting a predictable balance of character enhancements, and every player that returns is certainly for the "nostalgia" and not remembering the dissatisfaction that caused their absence.

    Every pc developer is looking to Sony and the PS3 so save them with the 100+ million sized installed base of console gamers.
    conditionally true: a console has a fixed architecture that developers and users expect to not cause any variation of playability to effect availability of the software and media.
    And everyone has to listen to them cry about how their directx codebase is now effectively worthless.
    true: DirectX isn't meant to be scalable and backwards-compatible as is openGL, because DirectX is subversion hidden under a misleading title/name that is neither direct and neither associating with technology-X; Microsoft DirectX expects to conquer every venue and leave the compatibility among antiquity and abandonware. At least in Linux, the Amish peacfully co-exist with the Borg and gothic Mimes of Apple.
    Boo fucking hoo.
    true: Atticus Finch caught Boo in the chicken-coupe with Hoo, and he remedied the situation with a buckette of water. Tell your Mother that her "morality-inspiring" movies are just as dirty as Britney Spears and Paris Hilton.

    Anyone dumb enough to still be basing their graphics engine on an increasingly marginalized API like directx deservers what is coming to them.
  • by Abcd1234 ( 188840 ) on Wednesday June 28, 2006 @03:13PM (#15623245) Homepage
    That negotiation can be done with an ARB as well.

    Uhuh. What's your point? In the case of DX, the designers are also acting as the ARB. So? Heck, that just further disputes the idea that "[the] glue is (ultimately) dictating to the materials what properties they must possess", since clearly they are dictating nothing, but rather working with hardware/software vendors to design an API which fits the needs of the game developers.

Arithmetic is being able to count up to twenty without taking off your shoes. -- Mickey Mouse

Working...