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."

352 comments

  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. Re:What will their NEXT version be? by Bromskloss · · Score: 1

      They have bought NeXT?

      --
      Swedish plasma phys. PhD student; MSc EE; knows maths, programming, electronics; finance interest; seeks opportunities
    3. Re:What will their NEXT version be? by Anonymous Coward · · Score: 3, Interesting
    4. Re:What will their NEXT version be? by ameline · · Score: 3, Insightful

      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.)

      --
      Ian Ameline
    5. Re:What will their NEXT version be? by Citizen+of+Earth · · Score: 1
      I heard they were thinking of calling it "ClosedGL".

      I heard "SharedGL".

  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 Dance_Dance_Karnov · · Score: 0, Offtopic

      need a "+1 stating the obvious" mod.

    2. 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.

    3. Re:Duh by csplinter · · Score: 1

      from wikipedia: Duh; The slang exclamation duh is used to express one's disapproval of the obviousness of something.

    4. Re:Duh by Dance_Dance_Karnov · · Score: 0, Offtopic

      from real life: sense of humor, somthing /. has not.

    5. Re:Duh by Firehed · · Score: 1, Insightful
      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 :)

      --
      How are sites slashdotted when nobody reads TFAs?
    6. Re:Duh by Sureshot324 · · Score: 1

      I will be laughing my ass off if some hacker makes dx10 work with windows xp.

    7. Re:Duh by csplinter · · Score: 2, Interesting

      Call me anti-Microsoft, fanboy, zealot if you will but, I find it seriously hard to believe that they were having trouble getting DirectX 10 to work at a decent speed on Xp, an operationg system that hogs probably half as many resources as Vista will. Theres no reason given in the article why it should run faster on Vista it just says there is one.

    8. 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!
    9. Re:Duh by csplinter · · Score: 1

      I've actually read about a group discussing the idea of taking a crack (no pun intended) at hacking halo 2 to work on Windows Xp.

    10. 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.

    11. Re:Duh by addaon · · Score: 1

      Dance, keep in mind that there's no "+1 trying to be funny" mod; the moderators have to choose from "+1 funny" or, in your case, "-1 asshat".

      --

      I've had this sig for three days.
    12. 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?

    13. Re:Duh by Anonymous Coward · · Score: 0

      Yes, Microsoft are such a small company and can't possibly keep things backwards-compatible between two contiguous Windows versions.

    14. Re:Duh by csplinter · · Score: 0

      Yes, my point exactly. They could do it, but apperently it is more profitable in their eyes, to only release it for Windows Vista. I'm sure if they had decided it would be more profitable if DX10 ran just as well in Xp as they would make it happen.

    15. Re:Duh by RMingin · · Score: 2, Interesting

      What I find really amusing is how many MS fans will say 'Oh, obviously; DX10 depends on LDDM, and XP doesn't have Longhorn's nifty new driver model!'.... Yet 98SE supported both WDM and it's predecessor, at the same time.

      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.

      --
      The preceding comment is my own, and in no way construes an opinon of the Emperor of Mankind.
    16. Re:Duh by I'm+Don+Giovanni · · Score: 3, Insightful

      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?

      --
      -- "I never gave these stories much credence." - HAL 9000
    17. Re:Duh by toddhunter · · Score: 1

      Which is it? Do you want Vista tech backported to XP or do you want Microsoft to keep Vista tech exclusive to Vista?
      I want to be able to play the newest games without buying and installing a new OS. Easy enough.

    18. Re:Duh by giorgiofr · · Score: 1

      I don't know what these "funny people" you speak of want. *I* want a pony!!!!!111oneone1

      --
      Global warming is a cube.
    19. Re:Duh by CaptnMArk · · Score: 1

      Personally, I don't want the XP version, I want the W2K version.

    20. Re:Duh by Tim+Browse · · Score: 1

      No.

    21. Re:Duh by strider44 · · Score: 1

      Is that funny? I thought the answer was that we want Microsoft to backport it so that there's no real reason to get Vista... After all, we don't *want* to spend several hundred dollars on an upgrade...

    22. 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.

    23. Re:Duh by ultranova · · Score: 2, Insightful

      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 ?

      --

      Forget magic. Any technology distinguishable from divine power is insufficiently advanced.

    24. Re:Duh by LarsWestergren · · Score: 1

      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.

      Oh, that's fresh, a Slashdotter accusing other Slashdotters of groupthink. Yet for all your snide accusations, most of the highly rated posts at this time of writing seem to support their decision, as backporting would be difficult and expensive.

      I can only speak for myself. I like to play PC games, but I don't want to pay for new versions of Windows. Actually I have made an oath to avoid paying ever again for Microsoft products as far as possible (not because I think their products are bad, but because I loathe their business practices). If most new games start using DX10, I'll guess I'll have to decide what is most distasteful choice - stop gaming, buing a console or buying Vista.

      --

      Being bitter is drinking poison and hoping someone else will die

    25. Re:Duh by mgblst · · Score: 1

      Wow, it is almost as if there are different people, with different opinions and different needs and different wants. Surely this isn't possible. The world is consists of two people, me and not-me. Otherwise it makes it really difficult to understand.

      The problem is that this will force people to upgrade, and Vista is a pretty huge upgrade for most people. So they will either miss out on the new games, or new games won't be able to utilise the new functionality of dx10.

      And I haven't really seen anyone bitch about backporting new tech to XP - what are you talking about. How did you get modded to 5?

    26. 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.
    27. 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
    28. Re:Duh by miyako · · Score: 1

      Some people want Microsoft to backport some of the new features to XP, and other people want Microsoft to make sure Vista is full of new features, no contradiction there.
      I also think that many people want Microsoft to backport things that can reasonable be backported, instead of arbitarily making things "Vista Only" to force upgrades, but would also like Microsoft to bring some innovation to Vista that means features can be added that werent possible in XP for example.
      Personally, I don't really care that much. I use Linux and OS X and will continue to do so after Vista is released. If I used Windows and had reason to really care about it, I would say that I don't have a problem with a Vista exclusive version of Direct X, but Direct X 9 has been out for a while, and it doesn't seem too unreasonable to ask for Microsoft release one last version of Direct X for XP and then focus on a Vista only release. I would even think that it might be beneficial for Microsoft to do so. I'm not sure how backwards compatible Direct X is, but having a version that runs on Windows XP and Vista might help ease the transition to Vista, instead of forcing developers to make a choice between XP and Vista / DX9 and DX10. Of course if DX9 games can be expected to run properly on DX10 then there is really no problem, but if that isnt the case then it might turn out like what happened with Windows 98, and Vista may be out for several years with people still keeping around Windows XP to play games on.

      --
      Famous Last Words: "hmm...wikipedia says it's edible"
    29. 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.

    30. Re:Duh by Anonymous Coward · · Score: 0, Informative

      DX attempts to be as thin as possible to provide something end-users care about: performance.

      In most developer's worldview there is something deeply wrong with caring about performance at the expense of architecture.

      DirectX is possibly the one API where that worldview is wrong. DX exposes a bottom-up view of the GPU. That's how it's designed; that's why it outperforms OpenGL so spectacularly and that's why game developers - all bottom up developers par excellence - love it so much.

      MS have the money to spend on doing architecture "wrong" to achieve high performance. So do games companies. This defines the industry, like it or not.

    31. Re:Duh by Alioth · · Score: 1

      There is more than one Slashdotter you know. The people who complain about the first issue are NOT NECESSARILY the same people who are complaining about the second.

    32. Re:Duh by Anonymous Coward · · Score: 0

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

      I read the article, I just don't buy it. Now I'm sure the tech guys were ready and eager to throw off the shackles of backward compatability - so it was a "technical decision" in a sense, but this is really a marketing decision - consumers have yawned about vista and this is just the sort of thing to try to drive customers to upgrade.

      Personally I think it is gonna backfire, if there is no xp version then game companies will stay with dx9 long enough for competing APIs to catch up. dx has enough lock in that this isn't gonna doom them by any stretch, but it is definitely a blunder.

    33. Re:Duh by OgreChow · · Score: 1

      Then perhaps you should give your business to companies that do not switch to DX10. If someone built a car that got twice the gas mileage but required a special process to be applied to the gasoline, would you be whining because the new gas wouldn't work with your old car? Get over it. You can still run your OS, and run the games that you want to run today. If enough people feel like you do and don't want to upgrade, game manufacturors will still support you. If no one feels like you do and everyone else upgrades, than tough luck for you.

    34. Re:Duh by Anonymous Coward · · Score: 1

      DirectX is slower than OpenGL for many things. OpenGL was, after all, designed for the visualisation of 3D on workstations.

      I don't know how well it stacks up at the moment, but in Quake/Quake2 era (Dx7-8?) one of the reasons for Romero to keep with OpenGL was because it was slower to render.

      Nowadays, I don't think that there is any significant difference between the two now, except that OpenGL will be compatible with the XP driver model and the Vista driver model.

      PS if you care so much about being labelled Troll, and request that others show why you are troll, please show where you get your statistics from that DX is faster than OGL. Your current missive reads as either "-1 Misinformed" or "-1 Troll".

    35. Re:Duh by webvictim · · Score: 2, Insightful
      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.

      --
      When did I realise I was God? Well, I was praying and I suddenly realised I was talking to myself.
    36. Re:Duh by Anonymous Coward · · Score: 1

      You mean John Carmack, and he also has a dislike of proprietary APIs that sways his decision making. Regardless, that was 10 years ago, well before DX7 and DX8.

      OpenGL can work about as fast as DX (see Doom 3 for an example of a fast OpenGL game), but I personally like programming on the DX9 architecture (haven't used DX10). But as a caveat, I'm very comfortable with COM programming; some people aren't.

    37. Re:Duh by astralbat · · Score: 1

      So... Alter the XP kernel, rewrite the driver model and have every vendor release new certified drivers? I think this would confuse both developers and consumers.

    38. Re:Duh by Fred_A · · Score: 3, Insightful

      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.

      --

      May contain traces of nut.
      Made from the freshest electrons.
    39. Re:Duh by plague3106 · · Score: 1

      Of course being the anti-MS fanboy zealot you claim that its hard to believe their reasons, even though you know nothing of their driver implementation or DX implementation or any of the restrictions that getting DX10 to work on XP brings. Basically, you're not qualified to evaluate their statements, but you chose to do so anyway.

      I'm sure you never ever came across a situation where you just couldn't make the code any better because of other restraints you have to stick with. That never happens in the real world does it?

    40. Re:Duh by plague3106 · · Score: 1

      Care to back that up with some references? Preferably directly from MS, as they are the ones building DX10.

    41. Re:Duh by plague3106 · · Score: 1

      Who said it had anything to do with the public API? They said the internal workings would have to be much different to support XP, and that they would be sacrificing alot of performance to make it XP compatible.

    42. 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.

    43. Re:Duh by plague3106 · · Score: 1

      Because the code (DX10) using the interface (HW driver API) has to deal with a new API that can allow for greater performance.

    44. Re:Duh by plague3106 · · Score: 1

      What I find really amusing is how many MS fans will say 'Oh, obviously; DX10 depends on LDDM, and XP doesn't have Longhorn's nifty new driver model!'.... Yet 98SE supported both WDM and it's predecessor, at the same time.

      And win98 crashed a hell of a lot more too, didn't it?

      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.

      Um, ya. Do you expect all the new features for a 2006 model car to be backported to your 2003 model? Why do you expect the same from software?

    45. Re:Duh by plague3106 · · Score: 1

      Don't worry, it will be quite a while before any DX10 games come out. You still have a few years left before you'll have to buy a new OS. $140 for 5 years averages to $28 a year for the cost of your OS. Not as big a deal if you look at it that way..

    46. Re:Duh by tolan-b · · Score: 1

      Seeing as we're talking about an article have you considered R-ing-TFA?

    47. Re:Duh by molarmass192 · · Score: 1

      Last I looked (and it's been a while), as a developer, you poll DX to find out if it supports a particular interface version. There is some level back compatibility, so an older game will work on a newer DX, but it's certainly not at the "all older DX API coded games work against DX new" level. That said, I would be completely shocked if MS didn't make DX 10 provide DX 9 compatible. That's a bit like begging for a game devs to choose another interface (eg. SDL + OpenGL) but MS isn't dumb, I just can't see them providing an opening like that.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    48. Re:Duh by LocoMan · · Score: 1

      Premiere Pro was XP only since it came out (2003). The official excuse from Adobe was that the new graphical system of XP allowed them to do preview most effects without having to render them, that back then was something only dedicated hardware based video editors could do, and that was one of the main selling points over previous premiere versions. Or at least that's what they said in the adobe forums anytime the question came out, wether it was true or not is left to the reader.

    49. Re:Duh by WilliamSChips · · Score: 1

      Or just, you know, add a compatibility layer.

      --
      Please, for the good of Humanity, vote Obama.
    50. Re:Duh by plague3106 · · Score: 1

      I did, I didn't see anywhere that said they changed the driver model soley to accomodate DRM.

    51. 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.
    52. Re:Duh by demachina · · Score: 2, Insightful

      " 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

      --
      @de_machina
    53. Re:Duh by ichigo+2.0 · · Score: 1

      Do you realise how extensive the changes in DX10 are? Besides, even if it was somehow possible to "add a compatibility layer" it would be a slow, bugged PITA, so what's the point? Everyone would still upgrade to Vista to get a better and faster DX10, and those who wouldn't probably didn't need DX10 in the first place. I know people have fallen in love with XP and are afraid of change, but Vista is better, so just stop whining and upgrade. If you can't afford it, then use piratebay or whatever, I.P. is no excuse to stay behind. XP will be 6 years old in 2007, that's the same amount of time as between Win95 and WinXP for crying out loud!

    54. Re:Duh by Anonymous Coward · · Score: 0

      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?

      No. And even aside from the time-to-implement issue, complexity is bad for performance, memory, maintenance, future development, and stability.

    55. 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).

    56. Re:Duh by penguinbrat · · Score: 1

      Exactly, this to me is or should be the same concept as programing in straight out 'C'. Regardless of which platform or architecture you are devloping on - printf is still printf, it is up the C libraries on the system to translate that statement into the machine code. I see no valid reason for this, I mean Linux went through a huge module change from 2.2 -> 2.4 -> 2.6 (2.4 -> 2.6 atleast), the video card comps had to only change the format of the module to work with the new kernels NOT change their hooks for the graphical subsystems.

      The only valid reason for this that I can see, is that they are doing the equivalent of making the kernel more or less an interpreter for 'C'. That changes the sub system of the C libraries to being the system itself - which tells me they are putting WAYYYYY to much importance on the graphics.

    57. Re:Duh by bheer · · Score: 1

      > 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?

      Only on /. could this be modded +5. Imagine this conversation in the 70s: Why does Unix treat a file as a stream of bytes when many mainframe OSes support block record-type files? Surely it wouldn't be too much trouble to add record-oriented I/O to stdio? Or, a more modern twist: how technically feasible is it to make Edgy Eft have a case-insensitive filesystem?

      Dig deep enough any technical reason in software is really an economic reason in disguise because software (unlike physical structures like say bridges) do not have to obey physical laws. If you really want to, anything in software can be solved with an abstraction layer.

      So maybe you'd like to quit splitting hairs over dictionary definitions and look and the semantics behind what the GP's saying.

    58. Re:Duh by PhoenixPath · · Score: 1

      C: Provide support for both. This is *very* realistic, and will probably be the norm for at least a year upon the release of Vista.

      There is a 50/50 chance the hardware they have wont run Vista or run it well.

      Vista runs fine on my 1.5Ghz, 768MB, Radeon 6800 128MB system. Considering this, and the fact that a $600 system purchased *today* will support Vista beautifully, I *really* don't see how, in late 2007, 50% of the users won't have the hardware to support it.

    59. Re:Duh by PhoenixPath · · Score: 1
      Yet 98SE supported both WDM and it's predecessor, at the same time.

      What's keeping MS from backporting some of the new Longhorn kernel/driver niftiness to XP?

      If you fail to see the difference here in what you are asking, let me explain it:

      Windows 98 SE supported it's own driver model and that of a *previous* OS. They did *not* backport WDM to Windows 95.

      Windows Vista will support DX10 natively, and DX9 through a seperate API (This is *exactly* the same as your 98SE example)

      They will *not* backport the new model to a previous OS.

      point:
      1. 98SE supported previous models. The previous OS did not support the new model.
      2. Vista supports previous DX API. The previous OS will not support the new API.

      Huh.... Your argument seems to be a bit flawed....
    60. Re:Duh by PhoenixPath · · Score: 1

      DX9 will be supported in Vista via a different API.

      Since Vista is the only OS that will support DX10, DX10 and 9 will *both* work on any system that has DX10 running.

      DX 10 does not specifically support DX9, but the DX9 API is going to be there to provide that backwards compatibility.

    61. Re:Duh by PhoenixPath · · Score: 1

      You will not get above a 3 on *any* system unless the Vid card has 512MB of ram. This has already been discussed. This does *not* mean Vista will not run just as well on a 256MB vid card, or even a 128MB, for that matter. The rating is intended for use on pproducts other than just Vista, and provides for future products/upgrades.

      Using your current rating as an excuse not to upgrade to Vista is absurd. It's be near impossible to build a 5 rated system today. But, considering it's not necessary, why would you want to?

      My system, a 1.5Ghz beast with a mere 768MB of RAM and a 128MB Radeon 9600 runs Vista/Aero just fine. Check out the latest Beta, it's even faster.

    62. Re:Duh by slimjim8094 · · Score: 1

      Excuse me? That's bullshit.

      Do you have any clue what you're talking about? I haven't actually written a device driver (trying to learn) but do you even know what one is? How the hell could it possibly be related to DRM? "Oh, my nVidia user-mode gfx driver is part of DRM"???

      I'm not a fan of DRM by any means, just that statement is total bullshit

      And, now that I've ranted about that for a couple of minutes, it's probably a troll...

      Damn

      --
      I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
    63. Re:Duh by mrchaotica · · Score: 0
      but Vista is better

      Vista is not better, because it integrates DRM and Treacherous Computing even worse than XP does!

      (Incidentally, my lone remaining Windows box runs 2000 -- I refuse to submit even to XP's "activation" bullshit.)

      --

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

    64. Re:Duh by Chosen+Reject · · Score: 1

      There is more than one Slashdotter you know.

      You mean all you people aren't just my imaginary friends making all these posts? YES! I have friends!

      --
      Stop Global Warming!
      Just say no to irreversible processes!
    65. 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

    66. Re:Duh by Anonymous Coward · · Score: 0

      THINK!

      With the driver in userland, it is subservient to the OS kernel. That means it cannot break DRM or call routines that it should not have access to.

    67. Re:Duh by tolan-b · · Score: 1

      Sorry, /.'s post folding made it look like you were replying to a different post. My mistake.

    68. Re:Duh by Anonymous Coward · · Score: 0, Informative

      Sure here you go. One of a series of articles on the changes that Microsoft is making.

    69. Re:Duh by Chowderbags · · Score: 1

      Great that they're trying to move away from broke, buggy design. Now, could they do that for the rest of the system? For example, maybe let us uninstall (or never install in the first place) Internet Explorer, Outlook, Windows Messenger, and all their other buggy software that creates endless security holes?

    70. Re:Duh by TheNetAvenger · · Score: 1

      "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?


      Ok, both of you are a bit wrong on this...

      For MS to support DirectX 10 in WindowsXP, the driver model of XP would have to change, there WOULD BE NO WAY TO IMPLEMENT the DirectX 10 technology on the XP Driver model.

      Some of the very basic reasons go from the Driver model Ring change to higher end differences like GPU multi-tasking and GPU Memory virtualization. All of which XP has no clue how to do. In fact, Vista is the only OS Driver model that I know of that support these concepts.

      So this isn't about creating a separate version of DirectX 10 for XP, it would be about redesigning the XP driver model, which would be a nightmare of compatibility problems.

      Vista's biggest problem so far has been pulling the WDDM driver technology together and offering XP performance and stability. Vista (Past Beta2) is succeeding at this, but considering the mass amount of OS level changes this has taken, implementing this on XP is impossible, not just infeasible.

    71. Re:Duh by Anonymous Coward · · Score: 0

      Romero? I think you mean Carmack.

      I'm talking about DX9, the version that's been out for, oh, only about 5 years. Maybe I got modded down for only making a statement that's true today because the moderators are only up to date with Windows history from the last century?

      OGL is fundamentally more abstracted than DX and that's why it's fundamentally slower. That was the OP's point - you should abstract more. And I was saying it's wrong - for 3D APIs, less abstraction is better. But the whole complex subtle point got completely lost on you lot because some idiot decided that a small part of my statement was contentious and therefore the entire thing was a "Troll".

      Pearls before swine.

    72. Re:Duh by killerkalamari · · Score: 1

      It is a basic reality today, most consumers DON'T NEED Vista or new hardware to run a web browser, email and office apps.

      Additionally, you don't really need Windows. My grandma is sick of her computer being screwed up with spyware and viruses, it is hardly usable (even after being "fixed"). When I told her I could put Linux on it and she wouldn't have to worry about all that junk she was really excited. All she uses the computer for is to check the occasional e-mail and view websites. For basic computing, we've been there for quite some time. Even Windows 95 is fine for the apps you mentioned (and to stretch that to the limit there are many MS-DOS word processors, spreadsheets, etc, and with WATTCP and packet drivers you can even get online! I actually use this configuration to ssh my ancient laptop to my main system or shell.. much faster than booting Linux and I can switch off the power at any time.)

      Having my grandma try Ubuntu will be a neat test too, because some have claimed that it is as easy for a clueless person to screw up Linux as Windows. Well, I guess I'll find out :)

    73. Re:Duh by zootm · · Score: 1

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

      It's a sad day when something like this gets modded +5. Any justification for that comment would be appreciated, since it looks like nonsense FUD.

    74. Re:Duh by Tweekster · · Score: 1

      Probably because most of those people just simply wont care enough to bother upgrade to Vista.

      So the hardware supports it, (and that is still a big maybe) but who is gonna go and line up to upgrade. People will make do with what they have. The days of people upgrading their OS itself are long over. They buy a new computer, and if that computer still works, the upgrade to vista isnt gonna happen

      --
      The phrase "more better" is acceptable English. suck it grammar Nazis
    75. Re:Duh by darkmeridian · · Score: 1

      A future version of Halo won't run on current hardware. It's gonna be a killer app, and everyone is going to get a new system just to run that game. Or they are going to get an Xbox 360 or whatever.

      --
      A NYC lawyer blogs. http://www.chuangblog.com/
    76. Re:Duh by ichigo+2.0 · · Score: 1

      That's what cracks are for. And Vista is better, I don't really give a damn if I can't play Bluray discs or HD-DVDs at full resolution, hell I have only bought one DVD in my entire life so I'm not even their target audience. Looking forward to HD-DVD rips though.

    77. Re:Duh by James_Duncan8181 · · Score: 1

      Also note here that the sampled group is web developers, a group far, far more likely to have a modern machine then the standard Windows user. You'll be able to see the Vista stats shoot up there as people install it for testing sites on IE7, I suspect.

      The situation has historically been slower changing then you describe, and is likely to be far more for gamers this time round. Vista has a large jump in hardware requirements, and is at present appallingly slow compared to XP. What gamer is going to want to drop 20fps on an FPS for features you can't see when you are in-game? This keeps gamers on XP, meaning that games prodcued need to support XP, meaning that gamers stay on XP....

      Slow.

      --
      "To any truly impartial person, it would be obvious that I am right."
    78. Re:Duh by mbourgon · · Score: 1

      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.

      Yes - Office 11 isn't out yet. If past performance is any indication, that'll bog your system something fierce as well.

      --
      "Sometimes a woman is a kind of religion, she can save your soul & set you free from all your sins" - Bad Examples
    79. Re:Duh by mrchaotica · · Score: 1

      It's the principle of the thing that matters to me.

      --

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

    80. Re:Duh by Some_Llama · · Score: 1

      I think you would need Microsoft and DRM in the same sentence, but then also something ABOUT microsoft and DRM in the same sentence, preferably that the combination is bad. Which it is bad. No likey. Evil M$

      *crosses fingers*

    81. Re:Duh by plague3106 · · Score: 1

      They are making changes to support DRM, but that article doesn't say that DRM is the driving force behind the changes. I bet they could add the DRM bit without changing the driver architecture. So no, you're link doesn't back up that the sole reason they are changing the drivers is for DRM.

    82. Re:Duh by Glonk · · Score: 1
      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).
      If you RTFA, you'd see that's really a thing of the past in DirectX 10.
    83. Re:Duh by kaffiene · · Score: 1

      And if you believe that BS, you would have to be a M$ fanboy (or a moron) - you choose.

    84. Re:Duh by innocence18 · · Score: 1

      Or it means you've done something deeply wrong in the past that you're now trying to rectify.

      --
      Anonymity of the internet is responsible for the views expressed in my post.
    85. Re:Duh by PhoenixPath · · Score: 1

      The days of people upgrading their OS itself are long over.

      An interesting theory, but woefully incorrect. I've upgraded mane folks from 98 and 95 to XP this year alone.

      people just simply wont care enough to bother upgrade to Vista.

      Going only by the amount of press and interest the Beta 2 has generated, I'm going to call BS on that one. It's said for every OS MS produces and fails to be true every time. And when they *do* buy a new PC? You can *bet* Vista will be on it.

    86. Re:Duh by ceswiedler · · Score: 1

      Indeed. I work on an MMOG which will be released in about two years, and we've considered and rejected using DX10 because there won't be enough people using Vista yet.

    87. Re:Duh by Anonymous Coward · · Score: 0

      The Direct3D 10 model requires a completely different model for interacting with the display hardware, which includes virtualizing it. Just like DOS didn't support virtual memory or preemptive multitasking, XP doesn't support virtual texture memory nor does it support preempting shaders mid-instruction.

      Just like you couldn't just add those features to DOS because it didn't have the architecture to support them, Windows XP doesn't have the architecture needed to support virtualizing the display hardware. Since it is an architectural change, it is simply not something that's possible in a minor version upgrade. It requires a major version upgrade, and the next major version is called "Vista". They could just as easily call the next major version "XP SP3" and make it a free download, but you still wouldn't be able to run DirectX 10 on your XP SP2 system no matter what.

      dom

    88. Re:Duh by andi75 · · Score: 1

      > That's really a thing of the past in DirectX 10

      And if you believe that, I've got a bridge to sell to you.

      It's not about what the card/driver *claims* it can do. It's about what it *can* do, and hopefully in a reliable and performant fashion. Mistakes happen, and buggy hardware and software gets released. But it doesn't necessarily get patched/fixed. That means it's the application programmers responsibility to work around the issues.

    89. Re:Duh by Anonymous Coward · · Score: 0

      No, they can't introduce Trusted Computing based DRM without major architecture changes to Windows... and specifically to the driver model. Everything Microsoft has done in the last 5 years has been building towards a system based entirely around a trusted core.

    90. Re:Duh by Anonymous Coward · · Score: 0

      You really need to learn about the corporate versions of windows. No activation, no WGA, SPs slipstreamed. Much nicer.

    91. Re:Duh by mrchaotica · · Score: 1

      That's not the point, especially since using corporate Windows is not legal for normal end users.

      --

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

  3. Why only on Vista by pampi · · Score: 1

    Becuse if somebody found bug in Vista, then it's DX10 fault, period.

  4. It will be for Vista only... by Anonymous Coward · · Score: 0

    ... for the sole purpose of making me warez it.

    No problemo, over to you Roblimo.

  5. 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.

    1. Re:That's an interview? by Netochka · · Score: 0, Offtopic

      Well, in all honesty, I'm not really that anti-microsoft, and yeah, I actually considered not posting the comment because it was just shameless microsoft bashing. I'll admit some of the stuff in the interview was quite interesting, and I probably should've mentioned that in my post. Really it's the interviewers that I have more of a problem with here, they come off sounding way too eager to please, as if they're just regurgitating info from the press release or something.

    2. Re:That's an interview? by QuietLagoon · · Score: 1
      Seems more like a bunch of pre-approved PR junk...

      Of course it's PR. Microsoft always has the "behind the scenes" interviews before a major release. It's all a part of the marketing campaign for Vista.

      Microsoft knows they have major perception problems with Vista, and they are trying to build up a positive "buzz" to counter all of the negative issues surrounding Vista.

    3. Re:That's an interview? by Anonymous Coward · · Score: 0

      "but I'm out."

      Don't let the door hit you on your way out.

      "I'm so sick of you script kiddie, I-hate-microsoft-because-everybody-else-here-does- too types"

      I'd venture to say Microsoft users are more likely to fit that catagory. You guys can only do what MS lets you do. And, as you say, OSS soooooo hard. Well, it's easy when you have some savvy.

      "Slashdot used to have some decent people here"

      Yeah, until it was envaded my MS fanboys who can't handle that their baby is being called ugly.

    4. Re:That's an interview? by CCFreak2K · · Score: 1

      Things like collision detection, or calculating obscured geometry so you don't have to render it.

      Gee, wasn't someone already doing this?

      --
      "Beware of he who would deny you access to information, for in his heart he dreams himself your master."
    5. Re:That's an interview? by Emetophobe · · Score: 1
      Things like collision detection, or calculating obscured geometry so you don't have to render it. Gee, wasn't someone already doing this?

      Game programmers maybe? Culling or "calculating obscured geometry so you don't have to render it" isn't done "automagically", this has to be programmed (unless you're using a game engine that does this for you).

  6. I misread this as Direct X10 by mikeage · · Score: 1

    and began panicking... no more X10 pop unders!

    --
    -- Is "Sig" copyrighted by www.sig.com?
  7. 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 Anonymous Coward · · Score: 0

      Yep, but with Vista you'll have to pay $499 for it.

    2. Re:Why should DirectX 10 support Windows XP? by kihjin · · Score: 3, Insightful

      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/ I don't think upgrading to Vista will be a zero-cost venture, especially since the hardware requirements are excessive.

      --
      This slashdot-related signature is a stub. You can help kihjin by expanding it.
    3. 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!
    4. Re:Why should DirectX 10 support Windows XP? by phorm · · Score: 2, Interesting

      OK, I'll bite on this one.

      First, compatability. Let's say you're a desktop user with a 2.4 kernel. Why would you not switch to a 2.6 kernel. Hmmm, well maybe you have some legacy hardware that only works on 2.4. But hold on a second, if your machine is using such legacy hardware, then what are the chances that it's going to have/need a new skookum video card. Hmmm.... not very

      So in most cases, your newer kernel is going to work with the hardware. Cue in Vista... well it might work with your hardware, but chances are pretty good that not all older software, let alone hardware, are going to work with the new OS... hmmm, not good, but then we run into...
      Secondly, performance. Well, chances are that (again, if you can fit a newer video card) your processor won't need any upgrades to run 2.6. In fact, in many cases you'll see better performance using 2.6 with the same resources, provided you don't bloat your kernel.

      Now let's check with Vista: Oooops, nope it looks like the hardware requirements are a little steeper for that one, aren't they? Moving on

      Third, modularity+environment. While some parts of the kernel definately affect userland, the two are different. The desktop environment, such as KDE, doesn't really care if you're running 2.6 or 2.4.

      Modularity of windows.... buzzzz. Nope, sorry. Chances are that with that shiney new system core you will also be seeing lots of UI and interface changes. You can't get a "kernel upgrade" in the windows world in quite the same way.

      And lastly, the big deciding factor for many: cost. Windows XP Pro has it's "end of life" listed in (I believe) 2009. However, directX 10 basically forces a few issues here:

      - Hardware vendors don't get newer capabilities from DX9. Therefore, they develop for DX10. Consequently, your games are rather suckish or possibly playable in DX9. Microsoft might still be patching XP, but they'll happily blame the vendors for not releasing compatible products when Vista rolls around. So for all those that want your stuff to still work... it's time for an upgrade. In the case of businesses (not everyone needs directX10, but I'll be betting that some graphics software might), that can be a hefty chunk of change.

      Somehow, it seems one has a lot less alterior motives when saying "we won't suppose this, but if you update for free we will" versus "we won't support this, but if you hand us another wad of cash we'll try"

    5. Re:Why should DirectX 10 support Windows XP? by 1iar_parad0x · · Score: 1

      If I'm a developement shop who wants the largest possible user base for a product that cost me a fortune to make, it makes a big difference. Most modern games already require users to upgrade to the latest and greatest hardware, why alienate your user base even more?

      In response to your question, MS should make DirectX 10 available for old versions of Windows because developers would like to sell their games to XP users while using a fully supported API. It's kind of like how all the VB6/VBA developers got upset over .NET. If MS wants us to use their products (i.e. buy server licenses) may be it should support their products a little better. Why should I make a long term commitment to a particular architecture if there's a chance it's going to make life miserable for me down the road?

      --
      What do you mean my sig is repetitive? What do you mean my sig is repetitive? What do you mean....
    6. Re:Why should DirectX 10 support Windows XP? by xtal · · Score: 1, Insightful


      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.

      --
      ..don't panic
    7. Re:Why should DirectX 10 support Windows XP? by Jugalator · · Score: 2, Insightful

      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?

      --
      Beware: In C++, your friends can see your privates!
    8. Re:Why should DirectX 10 support Windows XP? by kihjin · · Score: 0, Flamebait

      Well, I take it you weren't one of the few people to dish out the $200 (or however many hundreds of dollars it costs) for a licensed copy of XP. I'm not saying that I did.

      What I am saying is that Microsoft shouldn't simply ignore it's XP consumer base. I feel this is a mistake.

      Vista's biggest competitor will be XP (assuming Vista is released in the next 15 years). What better way to "encourage" users to the new platform by designing an API (which will undoubtedly be adopted by countless game publishers) that only works on Vista?

      But like you said: it's not a stability or security update, so no big deal. It'll just end up being the most expensive DirectX upgrade of all time.

      --
      This slashdot-related signature is a stub. You can help kihjin by expanding it.
    9. Re:Why should DirectX 10 support Windows XP? by batkiwi · · Score: 1

      Explain to me how new features in a new version of a product somehow lessen what the windows XP users paid for?

      Are you ripped off or owed anything if the new ford focus next year comes with satellite nav, and the one you bought this year doesn't?

    10. Re:Why should DirectX 10 support Windows XP? by xtracto · · Score: 1

      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.

      Wow, one of the most stupid comments I have read in some time. First, Microsoft has no obligation in giving you anything after you bought a LICENSE to use their software (XP). However, they will SURELY give an upgrade discount to acquire the license to use their new Operating system (Vista) which will be cheaper than buying the new license.

      Come on! it is really tiring the amount of fanboy trolls that appear in a Microsoft story, please try to make interesting discussions! this is no digg

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    11. Re:Why should DirectX 10 support Windows XP? by duncanmacvicar · · Score: 1

      Yes, and sure a link to the Linux kernel is the alternative for Joe user.

      A link to http://www.distrowatch.com would have been better.

    12. Re:Why should DirectX 10 support Windows XP? by Krimszon · · Score: 2, Funny
      ...old versions of Windows...


      XP is the latest version of Windows
    13. Re:Why should DirectX 10 support Windows XP? by kiddygrinder · · Score: 1

      Game devs aren't dumb, they're gonna have to get quite a substantial cash injection from ms to make the upgrade to dx 10 (for a marginal increase in functionality) worthwhile, since the cost is basically cutting their customer base in half.

      --
      This is a joke. I am joking. Joke joke joke.
    14. Re:Why should DirectX 10 support Windows XP? by Anonymous Coward · · Score: 0

      They usually support products (with critical updates) about seven years. Five years for less critical updates. After seven years, the product is in obsolescence (like Windows 2000 is now).

    15. Re:Why should DirectX 10 support Windows XP? by MrTufty · · Score: 1

      The majority (and I mean, the _vast_ majority) of people currently running XP aren't the sort of people who will buy Vista off the shelves. They're people who will simply buy a new PC with it pre-packaged. In short, Vista is going to take off whether the Slashdot crowd believe it or not, and whether it's the best operating system or not. Most home users will simply not have heard of Linux at all, much less have considered it as a viable choice. They'll probably have heard of MacOS, but that's more visible in the marketplace.

      For myself, I want Vista. It's a worthwhile upgrade as far as I'm concerned, as a user and a developer.

    16. Re:Why should DirectX 10 support Windows XP? by Anonymous Coward · · Score: 0

      You have totally unrealistic expectations.

      I bought my copy XP in 2002, thats 4 years of use I've got out it, 4 years of fixes and upgrades, 4 years.

      Does Microsoft Office 98 support Office 11 documents? No.
      Does Half Life load maps from Half Life 2? No.
      Does not getting Direct X 10 on your Win XP make your XP useless? No. Keep your whining.

    17. Re:Why should DirectX 10 support Windows XP? by drsquare · · Score: 1
      In one swoop, they've condemned people to upgrading if you want to play games on the dominant PC gaming platform.

      And in one swoop, Nintendo have condemned people to upgrading to the wee if they want to play games on a dominant console.

      You've also not realised that most major developers will not use DirectX 10 if it only works on Vista, as they'd be cutting off most of their customer base. They'll only switch once most people have Vista, in which case it's the right time to cut off the stragglers.
    18. Re:Why should DirectX 10 support Windows XP? by clickclickdrone · · Score: 1

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

      OK to an extent except XP is todays current technology. You could buy a PC up until the end of this year or therabouts and it will still have XP but then find a game that comes out Jan 2007 won't work because it's DX10 only. Even by PC standards, that's a short lifespan for your XP system. Sorry dude, your 4 week old PC's out of date.

      --
      I want a list of atrocities done in your name - Recoil
    19. Re:Why should DirectX 10 support Windows XP? by clickclickdrone · · Score: 1

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

      Probably the wisest thing I've read on /. this year. So many of the headline features such as WinFS have been dropped, what's left is just a prettier XP to most consumers.

      --
      I want a list of atrocities done in your name - Recoil
    20. Re:Why should DirectX 10 support Windows XP? by TheRaven64 · · Score: 1
      When DirectX 7 was released with Windows 2000, developers had the option of using it, or sticking with DirectX 6. If they stuck with DirectX 6, then anyone with Windows 95, 98, ME, or 2K could play their game. If they used DirectX 7, then anyone with Windows 95, 98, ME, or 2K could play their game, and they got some new features.

      When DirectX 10 is released with Vista, developers will have the option of using it, or sticking with DirectX 9. If they stick with DirectX 9, then anyone with Windows 98, ME, 2K, XP, or Vista can play their games. If they used DirectX 10, then anyone with Vista (or an XBox 360) can play their games. If they move to OpenGL, then pretty much anyone with sufficiently powerful hardware can. The next generation of games are likely (with the exception of a few XBox360-only titles) to be written using either DirectX 9 or OpenGL; the small market share of Vista at launch will ensure that it is not economically feasible for anyone not owned by Microsoft to develop games which will only run on it (games cost a lot to develop these days). If the OpenGL ARB pulls its finger out, then this decision could well kill DirectX.

      --
      I am TheRaven on Soylent News
    21. Re:Why should DirectX 10 support Windows XP? by Anonymous Coward · · Score: 0

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

      One thing you seem to be forgetting is that Windows is not a standalone product someone buys because it's cool or anything. Windows is needed by millions of applications. People don't want Windows, people want those applications.

      Why can't DirectX10 just be another application? Why does it have to be bundled with the OS? Oh, because Microsoft doesn't know how to abstract properly and is thus forcing people to upgrade an entire OS for a new feature? Isn't this exactly what gets them into legal trouble all the time?

    22. Re:Why should DirectX 10 support Windows XP? by NickFortune · · Score: 3, Informative
      Why should Microsoft make DirectX 10 available for old versions of Windows?

      Because they're not a nasty vicious monopolistic corporation hell-bent on extorting every last cent from their customer base, and who would never stoop so low as to refuse to release a key product for a mature platform still well within its support cycle, purely to force an upgrade cycle upon a market that feels no particular need to switch to an unproven product that offers debateable advantages and which will require expenditure on new hardware in most cases?

      Opps, sorry. Wrong parallel universe.

      --
      Don't let THEM immanentize the Eschaton!
    23. Re:Why should DirectX 10 support Windows XP? by PopeRatzo · · Score: 1

      Linux is an OPEN SOURCE operating system. I don't know what you do, but my outfit spend hundreds of thousands of dollars running the Windows operating system. That customer/vendor relationship sort of creates a "sacred duty" to continue to support not just their products but their customers. By moving development of their primary media technology to a platform that none of us has is baloney.

      --
      You are welcome on my lawn.
    24. Re:Why should DirectX 10 support Windows XP? by Weedlekin · · Score: 2, Insightful

      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.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    25. Re:Why should DirectX 10 support Windows XP? by botik32 · · Score: 1

      Well, as someone already pointed out in another reply somewhere above, this is a FUCKING API. APIs should be designed NOT TO CHANGE when the internals change. So, either Microsoft still hasn't learned how to write a proper API, or they DELIBERATELY CHOSE to make it incompatible.

      Both cases suck lame ass. How the fuck would a stable and open API like OpenGL be superseeded by an inferior/crippled/unstable API like DirectX?

    26. Re:Why should DirectX 10 support Windows XP? by PhoenixPath · · Score: 1

      It's the same as telling game devs to backport any improvements made in sequels to be backported to the previous game as a 'patch'.

      It's an absurd request. But just because it's MS, we can ask for the world, right?

    27. Re:Why should DirectX 10 support Windows XP? by PhoenixPath · · Score: 1

      I paid for Warcraft 1.0

      Does that mean Blizzard needs to backport all the graphics improvements from Warcraft 3 to Warcraft 1??

      Hell no!

      So why the hell are you expecting Microsoft to do it? It's absurd. I cannot believe we're even having this discussion.

      Are you people's brains not working any longer, or are you so blinded by your anti-MS fanboyism you cannot even see how absolutely ridiculous what you are asking for is?

    28. Re:Why should DirectX 10 support Windows XP? by phorm · · Score: 1

      While I would just as easily request such support for an open-source OS, depending on age, I wouldn't expect that somebody would dedicate so much of their own time resources without being paid (and MS has been paid for windows, they're not so rich for nothin'). If they did, fine, if not I'd have to look at alternatives, possibly making an update or patch myself, which I have done on occasion. If DirectX 10 was a module available for linux and somebody decided it would only be available for say, the future kernel 2.8, and adoption of 2.8 was hampered for some reason, then given its popularity it would be likely backported by some other party... which doesn't happen in closed-source, of course. If possibly, I'd do my best to assist such efforts as well.

      Now moving back to windows. While games don't necessarily 'scale back' to support old hardware, many do allow you to pick'n'mix features to allow more broad compatability. Thus, I could play the game at a decent speed with my older card, while getting a better visual experience with my newer one. DirectX can break this loop, as it seems that if DX10 is so radically different from DX9 it would be harder to support both, and as game shops migrate to DX10, windows XP will quickly drop into the dustbin for gaming. Not to mention the direct and possibly intentional impact this would have upon software such as Cedega, etc, and truely... if I can run my windows/DirectX9 games at close-to-par (or sometimes better) in an OS as different as linux, then I have serious doubts that it is that difficult to allow for them to run in XP and not just Vista (especially when one owns the source to both).

    29. Re:Why should DirectX 10 support Windows XP? by nixNscratches · · Score: 1

      If DX were open source.. those who wanted XP support could just fork the project and deal with the technical issues themselves. That said, this is a legitimate business issue, and MS has every right to move forward with a cleaner API and implementation and if that means no backwards compatibility, then so be it.

    30. Re:Why should DirectX 10 support Windows XP? by DarthVain · · Score: 1

      Just two quick points....

      1) Microsoft still sells XP. Until they stop selling it, there SHOULD be an expectation that they will support it. Even after they stop selling it, it SHOULD be expected that they would support it for a year or two, so they are not just leaving those that bought it high and dry.

      2) When the heck is Vista supposed to come out? If I am building a new computer, do I want to be one of the losers that buys the last unsupported copy of XP, then have to buy Vista. That sucks (and is currently the situation I am in). So this also kinda invalidates your Linux example, as in Linux you can just upgrade your OS to the most current version, and then install the video drivers. I think it goes without saying that this will NOT be possible with Vista. You will have to BUY a completely new OS, and leave the old behind.

      Anyway my 2 cents.

    31. Re:Why should DirectX 10 support Windows XP? by Anonymous Coward · · Score: 0

      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".


      I think people are pissed because Microssoft is providing them with little time to upgrade. They are telling their customers to upgrade to an unreleased product, which if following form will be filled with bugs and problems. Usually vendors give their customers some time to transition off of the old OS, but this isn't the approach MS is taking with Vista. It isn't the users' fault that MS can't ship product, they ought to ease users into the transition more gradually. MS is treating their customers very carelessly in this case.

      How long has the 2.6 kernel been out? Quite a while... The comparison is not valid.

    32. Re:Why should DirectX 10 support Windows XP? by kabocox · · Score: 1

      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?

      We are not talking about making DirectX 10 availble for Win3.11, Win95, Win98, WinME or WinNT. I believe that it should be runnable on Vista, WinXP, and Win2000 though. Why? Ok. DirectX is mainly thought of for games and gaming, but there could be some business apps that decided to use DirectX for some reason. DirectX is an API. If DirectX 10, 11, or 12 requires new drivers from hardware vendors that's one thing, but to say that the API won't work at all? That is just managment BS. Honestly, I've not been as pleased with MS with WinXP and making sure all the "third" party drivers were checked out. I'm not talking about no name generic drivers, I'm talking about nVidia, Ati, HP or Creative drivers getting warnings that the driver hasn't been signed off by MS. I'm sorry, but if MS can't get nVidia, Ati, HP, or Creative to have all their drivers for XP signed off by MS, then what makes them think that they'll be able to do it for Vista? Good idea yes, but will the other "third" party vendors go for it? Not likely.

      If anything MS needs to release the DirectX10 API and have a blurb stating for new features your video card/sound card drivers will need to be updated with your vendor's getting their drivers "MS certified" for DirectX 10 or even for WinXP or Vista.

    33. Re:Why should DirectX 10 support Windows XP? by seriesrover · · Score: 1
      But that would mean wanting it both ways. An OS is only obselete IF it seizes to be able to do what you want it to. If you bought a machine from a vendor with an old OS that doesn't do what you want after the new OS has come out, then thats on your head - dont't buy, go to someone else. You should know what you're paying for. If you don't its your fault


      MS isn't abandoning XP anytime soon - heck it still supports older version for years after.

    34. Re:Why should DirectX 10 support Windows XP? by cabd · · Score: 0

      What is this "legal windows user" you speak of?

      --
      When mad at one, try running a mile in their shoes. That way, not only do you have their shoes, but you are a mile away.
    35. Re:Why should DirectX 10 support Windows XP? by snuf23 · · Score: 1

      "What I am saying is that Microsoft shouldn't simply ignore it's XP consumer base. I feel this is a mistake."

      Really this comes down to the decisions of the developers. If the installed base of Vista capable machines is nil, odds are they won't be pushing DirectX 10 or games that only run on DirectX 10.
      There is going to be a lengthy adoption period. For one thing, right now there aren't any video cards that support DirectX 10 features. Odds are the first gen ones won't be that great either (if DirectX 9 is any indicator). Also games currently in the pipeline are not going to be Vista only. I guess the possible exception would be if Microsoft tries to push it with their own game releases. This would probably be stupid.
      Because developers aren't going to hurt their bottom line to help Microsoft push Vista sales, I think we are going to see a long adoption period for DirectX 10.

      --
      Sometimes my arms bend back.
    36. Re:Why should DirectX 10 support Windows XP? by maxume · · Score: 1

      Feels no particular need to switch to an unproven produce except that they *want* to play a game. If you don't need Vista, don't buy it.

      Microsoft not spending money backporting DX10 to XP, to keep people who don't want to give them more money happy, isn't all that surprising.

      --
      Nerd rage is the funniest rage.
    37. Re:Why should DirectX 10 support Windows XP? by NickFortune · · Score: 1
      Microsoft not spending money backporting DX10 to XP...

      Presupposing that Vista is different enough from xp that backporting is a non-trivial task. Their marketing says it is, but then they said that about 98 and ME, so I'm inclined to cynicism

      ...to keep people who don't want to give them more money happy, isn't all that surprising.

      And heaven forbid they should keep their existing customers happy. Nope, the thing to do is to punish their customers who recently invested in their operating system. It's like the idea that if there are no queues in a post office then too many staff are being employed; if Microsoft's customers are happy, that would mean MS weren't being aggressive enough, right? And anything short of maximal aggression would be A Bad Thing ... apparently.

      So, no, I don't find it surprising, either. Hell, I'm so far beyond surpise, I'm not even disappointed. But then I don't run windows anymore..

      --
      Don't let THEM immanentize the Eschaton!
    38. Re:Why should DirectX 10 support Windows XP? by maxume · · Score: 1

      If the benefits from keeping existing customers happy is less than the cost of supporting xp, they shouldn't do it. Apparently, that is the situation. It's not like that many people are running xp on hardware where dx10 is going to make a difference.

      --
      Nerd rage is the funniest rage.
    39. Re:Why should DirectX 10 support Windows XP? by NickFortune · · Score: 1
      If the benefits from keeping existing customers happy is less than the cost of supporting xp, they shouldn't do it.

      You know, I think the trouble with this debate is that too many people are conflating ethical, legal and economic imperatives when they use the word "should".

      Some commentators seem to think MS "should" release DX10/Xp because they have a moral obligation to do so. I disagree, and I suspect you do likewise. If that's the extent of our variance we can stop arguing now.

      Some seem to think that MS "should" be required under law to offer DX10 for XP. Again, I think we both disagree,

      Then we have the economic case. Here, you seem to assume, not unreasonably, that MS have run the numbers and concluded that their benefits from witholding DX10 from XP outweigh any they might gain otherwise. I wouldn't dispute that, save that I think they're being short-sighted.

      The benefit for MS is forcing their game players into an early upgrade. It's a tactic they've used before, from the origins of Direct X to the 3.1.1/95 break, to the backwards compatibility problems of migrating to XP. Add to that, the fact that gamers tend to be the only home consumers of leading edge computer kit left, and that's probably as far as they've thought about it.

      On the other hand, things have changed quite a bit since the days of 3.1.1 when this stunt arguably worked best. For one thing, the PC games market is dying; in no small part because MS is trying to kill it to push X-Box sales.

      The thing is, if all the gamers are forced to consoles to get the new games, then they're not going to be particularly driven to upgrade to vista. And if they do upgrade, they're likely to feel somewhat let down when they find there are no new games coming out for the platform. The sad thing being that, apart from a few PHBs who don't actually use their software, MS are all set to alienate the last remaining stronghold of MS fanboyism.

      This is classic MS, but their traditional tactics evolved in a market that wasn't being squeezed between high end gaming consoles on one side, and Linux on the other. By building bridges, rather than burning them, they could start building a userbase thay could support them past the fall of their OS monopoly - something I think is both inevitable and looming large in their future. IMHO, obviously.

      It's not like that many people are running xp on hardware where dx10 is going to make a difference.

      ...because Vista is going to be such a radical step forward - or at least have so much eye candy - that current machines just won't be able cope, yes?

      Only we have OSX which is generally considered to be as pretty an interface as could be asked for, and that runs just fine on current x86 kit. So does Xev. And most of the prettiness in Vista is MS playing catch up. Apple and Linux have had a lot of this stuff for years.

      Which brings us to the question of whether Vista _really_ needs this hardware requirement. It can be done without, which suggests either poor coding skills, or (as I;m inclined to believe) that MS are just bloating their software to make it seem as if it must be more powerful.

      Based on past experience...

      --
      Don't let THEM immanentize the Eschaton!
    40. Re:Why should DirectX 10 support Windows XP? by Weedlekin · · Score: 1

      "An OS is only obselete IF it seizes to be able to do what you want it to."

      Note the topic we're dealing with, i.e. DirectX 10 not running on anything except Vista. This means that for gamers (who are the only ones affected), Windows XP will indeed be obsolete despite the fact that Microsoft will still be charging them for it with new machines.

      " If you bought a machine from a vendor with an old OS that doesn't do what you want after the new OS has come out, then thats on your head - dont't buy, go to someone else"

      I said nothing about machines bought _after_ Vista ships. My post was entirely concerned with those bought a few days or weeks _before_ it ships, so most of the rest of what you have written is irrelevant. Perhaps you should read what people actually write before answering.

      "MS isn't abandoning XP anytime soon - heck it still supports older version for years after."

      What is the topic again ? Oh yes, it's all about DirectX 10 not being available for Windows-XP! Thus, in the context of this discussion, Windows XP has already been abandoned, because there will not be any new versions of DirectX for it, and based on Microsoft's past behaviour, precious few if any bug fixes for the existing version.

      --
      I'm not going to change your sheets again, Mr. Hastings.
    41. Re:Why should DirectX 10 support Windows XP? by maxume · · Score: 1

      Yeah, we disagree on whether they are in a position to do any 'forcing', or perhaps I think there is a carrot and you think there is a whip.

      As for why people won't be running vista on old hardware, for the most part, people in windows land don't upgrade their os, they upgrade their computer. Sure, there are a few users that do, but the "masses", as it were, buy new.

      --
      Nerd rage is the funniest rage.
    42. Re:Why should DirectX 10 support Windows XP? by NickFortune · · Score: 1
      Yeah, we disagree on whether they are in a position to do any 'forcing',

      Odd. The only reference to "force" in my last post was in refernce to the pressure MS and Sony are putting on Game studios to release of XBox or PlayStation only. Or failing that, to delay release to the PC so as to drive console sales. Perhaps I might have expressed myself with greater clarity if I had written "if those gamers (who wish to enjoy the latest games) are forced (by delayed or restrited release cycles) to buy consoles to do so...".

      The point being that until PS3 comes out (if ever) then MS are competing against themselves here. They may driver more games to abandon the PC for consoles (which is about the only way this strategy makes any kind of sense for them) but they're probably not going to induce many games to upgrade just for DX10, and the ones that do are going to end up bitterly dissapointed if MS keep pressuring game studios to starve the PC market. It's a short term gain against even more long term resntment. Not that such considerations ever seemed to bother them in the past, but I do think times are changing.

      or perhaps I think there is a carrot and you think there is a whip.

      I'm sure MS think they're offering a carrot as well. I just think this one is going to leave a sour and lasting taste in the mouths of those who chase it, and I question whether this is a sensible time for the software giant to be pissing off even more its userbase.

      But you know, it doesn't affect me one way or the other.

      people in windows land don't upgrade their os, they upgrade their computer

      Exactly! Which is the problem MS face. Most users are happy with the level of computing power they currently have. MS want a wave of purchases so they can proclaim Vista as a success. But the average joe isn't going to do it, and the PHBs are notoriously reluctant to upgrade software. The omly folks who are likely to spend the money on a Vista capable rig right now are likely to be Gamers. So I guess they reckon that if they want to generate that buzz, gamers are the segment where they need to apply pressure.

      --
      Don't let THEM immanentize the Eschaton!
    43. Re:Why should DirectX 10 support Windows XP? by maxume · · Score: 1

      From paragraph 5:

      "The benefit for MS is forcing their game players into an early upgrade. It's a tactic they've used before, from the origins of Direct X to the 3.1.1/95 break, to the backwards compatibility problems of migrating to XP."

      *shrug*

      --
      Nerd rage is the funniest rage.
    44. Re:Why should DirectX 10 support Windows XP? by NickFortune · · Score: 1
      Oops, my apologies. I searched for "force" rather than "forcing". Honest mistake on my part.

      That said... I'm not sure what you're objecting to. We both seem agreed that - by means of carrot or by means of stick - MS are trying to manipulate their userbase by withholding DX10 from XP. (You may feel "influence" is a kinder term). You tend to cast their actions in a more positive light than I. Never the less, I think we agree on the "what" and largely on the "why" of it all.

      So I'm really not sure what your objection is. Are you questioning my assesment of this strategy as possible unwise over the medium to long term, or maybe you just think I'm being mean for no good reason?

      I dunno, maybe the thing to do is to shrug and move on to more productive discussions

      --
      Don't let THEM immanentize the Eschaton!
    45. Re:Why should DirectX 10 support Windows XP? by maxume · · Score: 1

      Lately I'm a fan of thinking of things in terms of framing. I don't think that Microsoft is actively limiting user choices, which to me, they would have to do to be able to control their users. I say control because force has that strong connotation. I just don't think it's a good way to look at the issue, it isn't Microsoft's job to be nice to me. I do see your point that it might be in their best interests to be nice to me though.

      Your assessment could very well be right. I doubt it, Microsoft, despite the vitriol they face in certain communities, is not in the business of making bad decisions. It may seem like it, but hey, they clear a billion dollars a month.

      My most recent comment was just to point out that I wasn't actively trying to argue unfairly.

      --
      Nerd rage is the funniest rage.
    46. Re:Why should DirectX 10 support Windows XP? by NickFortune · · Score: 1
      it isn't Microsoft's job to be nice to me. I do see your point that it might be in their best interests to be nice to me though.

      or at least, they might find their interests better served if they nicer in sometimes. The trouble is, I don't think "nice" is something that gets taken into consideration at Redmond. They seem to have this ghetto "everyone's out to get us" mentality which makes them see their users as hostile. I think they're nasty be reflex because they see themselves as hated and under attack. And I think becomes a self fulfilling prophecy. I was a Microsoft fanboy once upon a time...

      Microsoft, despite the vitriol they face in certain communities, is not in the business of making bad decisions.

      Ten years ago that point would have been unassailable.

      It may seem like it, but hey, they clear a billion dollars a month.

      I think they made some excellent decisions in the past. In the last ten years though I don't think they've had to - I think their wealth and power has insulated whenever they've made a mediocre decision, and when they've made the occasional stinker, they've been able to fix it in advertising or in politics

      A also think the time is coming when they are going to have to make some very good decisions indeed if they want to remain in business at anywhere near their current level. Office is under pressure from OpenDocument, Desktop linux is finally starting to see large-scale governent and corporate deployemnt. That wouldn't be so much a problem if there was anywhere for MS to go, but they seem to be losing the embedded market, never had servers no matter how hard they tried, phones are being hotly contested.. about the only breakthrough they made was into games consoles, mainly by burning money until it happened.

      The trouble is that people don't like them. That wasn't a problem while they were seen as the only game in town. But that's increaslingly not the case, and some of the new offerings can undercut them by a lot. Apple were in that position with respect to MS, and they survived (in no small part) by having a core of deeply loyal users. Somehow though, I can't see that tactic working for Microsoft.

      --
      Don't let THEM immanentize the Eschaton!
  8. OpenGL by moria · · Score: 0, Troll

    How is it different from OpenGL? Why don't MSFT simple submit a proposal to extend OpenGL in a open way? It seems MSFT will never learn to play openly.

    1. Re:OpenGL by cyber-vandal · · Score: 2, Informative

      Because the more lock-ins Microsoft has the harder it is for users to switch to alternatives.

    2. Re:OpenGL by I'm+Don+Giovanni · · Score: 3, Insightful

      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.

      --
      -- "I never gave these stories much credence." - HAL 9000
    3. Re:OpenGL by mcbridematt · · Score: 2, Interesting

      Why argue with an external body dominated by guys from a different side of the industry (cad/cam) just to add some capabilities to your platform?

      Many on Slashdot would say its to tighten M$'es dominance - true, but they are probably fed up with standards body bloat too - why let an idea slip due to bureaucracy at some working group when you can implement it now yourself and do the standards thing later when your customers FORCE you to.

      Interestingly DirectX adoption seemed to accelerate after NVIDIA tightened its market share in the early part of this decade as 'custom' OpenGL render paths for 3dfx and others disappeared (as the hardware vendors did) in games and were replaced with DirectX 6/7 paths.

    4. Re:OpenGL by novus+ordo · · Score: 1

      Actually, one can argue that the only reason why DX is successful is because of its submissions, or should I say acquisitions. Microsoft joined OpenGL ARB and all they did was stall the OpenGL with threats of patent infringement. That's all that was needed for them to take the lead. Any graphics developer will tell you what a fine API DirectX is.

      --
      "You're everywhere. You're omnivorous."
    5. Re:OpenGL by xtracto · · Score: 1

      The GP post is stupid. These trolls forget that Directx != Direct3D. And it is just after you have programmed something using DirectSound, DirectPlay and DirectInput and say something as SDL that you *understand* why cant "MSFT simple (sic) sbumit a proposal to extend OpenGL in an open way".

      Really, people please read more or do not comment. You only show that you are stupid.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    6. Re:OpenGL by ichigo+2.0 · · Score: 2, Informative

      Any graphics developer will tell you what a fine API DirectX is.

      I've used them both, and while OpenGL isn't a slouch, DX is a lot easier to use (especially in the shader department). Supposedly OpenGL has even that under control nowadays, so it's just a matter of taste, really (and performance, Ati's OpenGL drivers are still buggy).

    7. Re:OpenGL by Glock27 · · Score: 1
      I've used them both, and while OpenGL isn't a slouch, DX is a lot easier to use (especially in the shader department). Supposedly OpenGL has even that under control nowadays, so it's just a matter of taste, really (and performance, Ati's OpenGL drivers are still buggy).

      The performance comment cuts both ways. DirectX uses COM, which has overhead compared plain-old-C-function calling.

      There is also more to it than "taste". DirectX is one of the better mechanisms Microsoft has come up with to lock developers and titles into Windows. If you plan on writing a game, at least use an engine that supports OpenGL as well. You've increased your potential market, and done a little bit to promote choice in computing.

      BTW, NVIDIA's OpenGL drivers are rock solid, including the Linux flavor.

      --
      Galileo: "The Earth revolves around the Sun!"
      Score: -1 100% Flamebait
    8. Re:OpenGL by Anonymous Coward · · Score: 0

      I don't know, gee it's not like fragmenting the set of available APIs that do pretty much the same thing is an unnecessary burden for cross-platform developers or anything.. how's that for practicality? Though sure Microsoft would certainly LOVE to have this issue fixed their own way and see OpenGL disappear altogether.

  9. Drivers running in user mode by QuantumG · · Score: 0

    I wonder if nvidia and ATI will use this as reasons why they can't continue supporting Linux.. oh wait, the drivers already run in user mode on Linux!

    Hopefully it will just mean the X11 modules will get bigger and the kernel modules will get smaller.

    --
    How we know is more important than what we know.
    1. Re:Drivers running in user mode by Anonymous Coward · · Score: 0

      How do linux kernel modules run in user mode ?

    2. Re:Drivers running in user mode by mattyrobinson69 · · Score: 1

      In linux, the drivers run in kernel mode. You can write userspace non-root filesystems, but not device drivers.

    3. Re:Drivers running in user mode by Anonymous Coward · · Score: 1, Insightful

      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.

    4. Re:Drivers running in user mode by pe1chl · · Score: 2, Informative

      That may be true for the "usual" XF86/X.org driver, but the kernel module for accelerated NVIDIA cards is not a small module just to interface with the hardware.
      Else I find it hard to explain that it is over 4MB in size...
      (the typical driver module is typically a few tens of KB in size, up to a few hundred for very complex drivers)

    5. Re:Drivers running in user mode by QuantumG · · Score: 1

      Look, no-one knows what those modules do except the engineers at nvidia.

      That's the problem.

      --
      How we know is more important than what we know.
    6. Re:Drivers running in user mode by pe1chl · · Score: 1

      That sure is a problem, but in a playing field as we have now it is the only solution.
      Of course we can all dream about open hardware available at your store around the corner, developing just as quickly as closed spec videocards, but for now that just isn't happening.
      I prefer an affordable and fast videocard with today's interface connectors over a dream about some unrealistic device that may never appear.

      At least NVIDIA releases new drivers when new hardware or new Linux versions appear.
      There are already more than enough companies that "support Linux" by delivering some driver for an ancient RedHat release and never update it.

    7. Re:Drivers running in user mode by QuantumG · · Score: 1

      Losers. I remember when driver writers reverse engineered the hardware. Oh wait, that was only last week. OpenBSD developers reverse engineer hardware to write drivers all the time. Maybe one day they'll get bored with WiFi cards and SCSI adapters and take on the 3d card manufacturers. That'd be sweet.

      --
      How we know is more important than what we know.
  10. The most intersting part to me was: by Anonymous Coward · · Score: 0

    on the second page:

    "And then there's a lot of things about feature consistency in hardware implementations that allow developers to have an easier job of targeting a wider variety of platforms. That doesn't show up as any single feature, but it's a big deal to get agreement on what this common set of features is and it will be available everywhere."

    Glad to see portability is an issue. I hope I read that correctly

  11. 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.
    1. Re:DirectX & Antitrust by SpiffyMarc · · Score: 1

      DirectX is an API. Nobody forces the developers to use it.

    2. Re:DirectX & Antitrust by 10Ghz · · Score: 1

      Looking at how Microsoft plans to cripple OpenGL in Vista, I think that developers might not have a choice on the matter.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    3. Re:DirectX & Antitrust by Jugalator · · Score: 1
      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).

      Yes, but Windows is hardly a gaming platform monopoly. Consoles seem to be holding their ground pretty well, and many game developers these days simply give Windows the finger and makes pretty big profits.
      --
      Beware: In C++, your friends can see your privates!
    4. Re:DirectX & Antitrust by 91degrees · · Score: 1

      Not really. API specific graphics and sound are a small portion of the total game. It doesn't take that long to port to OpenGL or Sony's API.

    5. Re:DirectX & Antitrust by 10Ghz · · Score: 1

      Couldn't you just as well say that "Windows is not a gaming-monopoly, since we have lots of people playing real-life poker"? What makes you think that console is replacement for PC as far as gaming is concerned?

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    6. Re:DirectX & Antitrust by datafr0g · · Score: 3, Insightful
      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.

      --
      "Who says nothing is impossible? Some people do it every day!" - Alfred E. Neuman
    7. Re:DirectX & Antitrust by 10Ghz · · Score: 1

      because when you buy a Dell or some other OEM-machine, they will all ship with Vista? Most people get theor OS with their computer, and pretty soon those computers are going to be running Vista by default.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    8. Re:DirectX & Antitrust by Jastiv · · Score: 0

      I never even got xp after seeing what it was like.

    9. Re:DirectX & Antitrust by 10Ghz · · Score: 1

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

      And that is what they are doing with Vista, basically. In Vista, OpenGL is just a wrapper around Direct3D, and it takes about 50% performance-hit. Sure, vendors (NVIDIA etc.) could provide their own OpenGL-implementation, but that means that the spiffy 3D-desktop Vista has would not work anymore. In other words: Microsoft is making sure that OpenGL is as undesireable as possible in Vista.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    10. Re:DirectX & Antitrust by MadEE · · Score: 1

      Cripple OpenGL how, not including a generic driver? Video card manufacturers develop their own implementation of OpenGL in their drivers, and have to for years; there is not a whole lot of need for generic drivers that do not have all the extensions needed for the card. Crippled is running a generic driver.

    11. Re:DirectX & Antitrust by MadEE · · Score: 1
      Sure, vendors (NVIDIA etc.) could provide their own OpenGL-implementation, but that means that the spiffy 3D-desktop Vista has would not work anymore. In other words: Microsoft is making sure that OpenGL is as undesireable as possible in Vista.
      Could make custom drivers? They Do and have for almost as long as 3d accelerators have been around. There is no reason why card makers can not support both OpenGL and DX, they do now with out much problem. When you are using your desktop the spiffiness uses DX and when you play your game it uses OpenGL the only time this would be an issue is when running OpenGL in a window, something that isn't that popular in most games.
    12. Re:DirectX & Antitrust by Kjella · · Score: 1

      Because it's not illegal to achieve a monopoly, only to use the dominating position in one area (OS) to force out the competition in other markets (browsers, media players). In this case I'd say games are free to go with either DirectX or OpenGL on Windows - the games ship with the latest redistributable anyway so there's no particular "preinstall" advantage. That DirectX is winning and OpenGL is losing is from what I've understood mostly been on its own merits. Or at least that's what the developers of the last FPS I cared about said.

      --
      Live today, because you never know what tomorrow brings
    13. Re:DirectX & Antitrust by 10Ghz · · Score: 1

      "Because it's not illegal to achieve a monopoly, only to use the dominating position in one area (OS) to force out the competition in other markets (browsers, media players)"

      And through the dominance of Windows, Microsoft is also pushing DirectX. Why can they push DirectX, but they can't push Media Player or IE?

      "In this case I'd say games are free to go with either DirectX or OpenGL on Windows - the games ship with the latest redistributable anyway so there's no particular "preinstall" advantage"

      Except that on Vista, OpenGL is inherintly crippled, with vendor-ICD's or not.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    14. Re:DirectX & Antitrust by novus+ordo · · Score: 1

      Vista will NOT kill OpenGL.

      --
      "You're everywhere. You're omnivorous."
    15. Re:DirectX & Antitrust by Anonymous Coward · · Score: 0

      This was misleadingly reported (iirc by slashdot, amongst others) and is really nothing to worry about. Firstly it's the *generic* openGL driver, that no video card manufacturer uses anyway, preferring quite rightly to substitute one optimised for their hardware. Secondly yes, MS are implementing it as a wrapper around DirectX, but before you assume that this will "cripple" it consider that Transgaming do the same thing in reverse (DirectX -> OpenGL) and it works rather well, sometimes actually faster, even though they're having to constantly chase MS' fancy new features.

    16. Re:DirectX & Antitrust by Anonymous Coward · · Score: 0

      ...and what about CAD/CAM applications? They do all sorts of windowed OpenGL.

    17. Re:DirectX & Antitrust by asuffield · · Score: 1

      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 antitrust is fundamentally a reactive set of laws, not pre-emptive ones. Authorities weren't "concerned about Microsoft dominance", they were concerned that an actual business (Netscape) had been destroyed by Microsoft. It's not a crime unless big business gets hurt. Microsoft abusing their monopoly position isn't enough. Undesireable effects on the consumer are not enough.

      When Microsoft has used their monopoly position to shove Sony and Nintendo out of the gaming market, then they can start thinking about putting together an antitrust case. Of course, that won't do you much good.

    18. Re:DirectX & Antitrust by makomk · · Score: 1

      Perhaps. On the other hand, I read somewhere that Microsoft had developed a driver architecture that would make it easier for graphics card manfacturers to support OpenGL on Windows, so they wouldn't all have to have their own implementations of OpenGL (and some companies had even written drivers for it) when they dropped it and went with DirectX instead, which did roughly the same thing but in a more proprietary way. (Can't track down the information - sorry - but it was linked to by a Slashdot poster, so hopefully someone on here will know what I'm talking about...)

    19. Re:DirectX & Antitrust by Tim+C · · Score: 1

      Looking at how Microsoft plans to cripple OpenGL in Vista

      And how is that then? I know that they're not going to ship an accelerated library themselves, but nothing prevents your card manufacturer from shipping their own, exactly as they do now.

      *No-one* who cares about performance uses the OGL library that ships with Windows. If anything, it makes no sense for MS to expend any effort on it - any card capable of running OpenGL already has a far superior version supplied with it.

    20. Re:DirectX & Antitrust by penguinbrat · · Score: 1

      This brings up another thought I was having... One of the things M$ IS known for is using there monopoly power to change things and lock out their competitors. Their biggest one is Linux, and she relies 100% (excluding SDL) on OpenGL for the fancy and pretty graphics. All the video cards I have purchased over the years have always had to support the given subsystem (DirectX/OpenGL), NOT the other way around, otherwise is just wouldnt work right. From what I am understanding here, either this would free up a lot of work on the video card side (not having to keep up with subsytem API's and changes) and there for they would have more resources to devote to OpenGL - OR - they have engineered a way that would make it VERY difficult, if not impossible in the same driver, for the drivers to support the two different subsystems.

      Which leads to another question - is DirectX going to be such a huge part of the system that OpenGL will never be able to work right in Vista? And, if this subsystem is such an integral part of Vista, and there are 9 different versions of it, where #9(the most expensive) is where this subsystem is not disabled in anyway - will there be hacks for the basic versions of Vista to fully enable it?

    21. Re:DirectX & Antitrust by zoomba · · Score: 1

      There's a certain line that has to be drawn at some point where an OS feature isn't considered a monopolistic move. A web browser is a bundled application. A media player is a bundled application. DirectX is an API. It is a set of instructions on how the OS should talk to video hardware. Personally, I think this is a valid component to an Operating System. If someone decides they want to write a new sound device API, or a new input device API, should Microsoft then remove those core pieces from their OS for fear of being called on antitrust issues?

      Also, OpenGL isn't a commercial entity as far as I know. SGI sort of helps guide the project now, but it's turned into a community work more than a corporate one.

      Another bit is that it remains up to the developers which API to use. Many developers actually consider DirectX to be the superior of the two, easier to work with, and better supported. Some developers make OGL games and do quite well too (iD engine games), so obviously DX doesn't yet qualify as a monopolistic move.

      Now, in Vista, the entire model for the OS is changing. How hardware is handled, everything. For a time, this means that everyone's going to be trying to catch up and release new versions of their code to work with Vista. OpenGL will have to do the same. OpenGL 2.1 will come out to work equivalently under Vista eventually. It is not Microsoft's responsibility to work with everyone in the entire computing world to make sure their code isn going to work on the next version of Windows.

      There's nothing monopolistic in this case. It's an API for talking to hardware, which squarely belongs in the realm of the OS maker.

    22. Re:DirectX & Antitrust by makomk · · Score: 1

      This was misleadingly reported (iirc by slashdot, amongst others) and is really nothing to worry about. Firstly it's the *generic* openGL driver, that no video card manufacturer uses anyway, preferring quite rightly to substitute one optimised for their hardware. Secondly yes, MS are implementing it as a wrapper around DirectX, but before you assume that this will "cripple" it consider that Transgaming do the same thing in reverse (DirectX -> OpenGL) and it works rather well, sometimes actually faster, even though they're having to constantly chase MS' fancy new features.

      IIRC, it wasn't just the fact that it was a wrapper around DirectX that people were complaining about (though it does pretty much guarantee OpenGL will be at a speed disadvantage to DirectX), it was also that it was missing a lot of the more modern features of OpenGL (i.e. shaders), though I suppose they might've fixed that since then. Also, if the graphics driver substituted its own OpenGL driver, you lost all the fancy Aero features - apparently, it is now possible to do this and still have Aero fully-functional, but it needs new drivers and I'm not sure how well this will work yet...

    23. Re:DirectX & Antitrust by anzev · · Score: 1

      Basically, because Microsoft supports OpenGL as far as I know. So it's not something that is closed to competitors. In my opinion, it's the same with everything else Microosft does, it's good, it's friendly, lots of people use it, so more bugs are found. However, looking at the brower, you can see it was hard for a new one to enter but the game developers do have a choice. It's not their fault OpenGL doesn't support half the stuff DirectX does. Or that it's easier to program in one than the other. But they can use both, and they can deploy both to their largest market, Windows.

      The game makers, the one that accept the decisions over which platform they will use do not really care which technology they're using AS LONG AS it supports this and that, and this kind of shading, and that kind of shading, and as long as they can reach their largest market possible; which in all fairness is Windows users. Ok, so people use Linux, and people use Mac, and you also have to admit, a lot of us do, but the ones that play games, mostly don't. So why bother learning new technology? Why bother extending something to support something that something already has? I don't care what runs underneath when I'm playing a game. When I play a game (and I do so very very very rarely) I want it to play smooth and to work on Windows.

      Anyway, to go back on topic, I believe it's unfair to say that Microsoft can even dominate this market. Because there is no market to dominate. It would be ok to say so IF, and only IF Microsoft actually wrote games and set them as defaults on Windows and wouldn't allow you to install anything else. THEN, we could talk about Antitrust violation.

      Well, just my two cents.

    24. Re:DirectX & Antitrust by Anonymous Coward · · Score: 0

      This is how it works today too. Try running an OpenGL game on a video card that doesn't have OpenGL drivers. Of course, this is tough to do since none of the major manufacturers release DirectX drivers without including OpenGL drivers.

    25. Re:DirectX & Antitrust by 10Ghz · · Score: 1

      "And how is that then?"

      If the vid-card uses OpenGL, one of the major new features in Vista, the 3D-accelerated GUI will stop working.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
    26. Re:DirectX & Antitrust by Jthon · · Score: 1

      You are correct in that, but why choose Direct X over the cross platform OpenGL? It's actually pretty simple.

      DirectX supports more features out of the box. It turns out that while you can do anything with OpenGL that you can in DX many of the features are implemented as vendor specific OpenGL extensions.

      For developer's this means writing multiple code paths for more than one GPU, which they do some of with DirectX but OpenGL makes this worse. Of course this isn't the whole story. OpenGL has slowly been moving many of these features into the standard but the committee nature of the OpenGL ARB can make this a slow process.

      Of course Microsoft sit's on this board and probably helps keep this process as slow as possible. I have heard that when some new OpenGL features get suggested Microsoft does it's best to squash them to prevent competition with DirectX.

    27. Re:DirectX & Antitrust by snuf23 · · Score: 1

      "There's nothing monopolistic in this case. It's an API for talking to hardware, which squarely belongs in the realm of the OS maker."

      Yes, thank god we aren't back in the days of vendor APIs. Remember 3DFX glide?

      --
      Sometimes my arms bend back.
    28. Re:DirectX & Antitrust by Anonymous Coward · · Score: 1

      Uh, did I get it right that MS has locked down Windows so that you can only use Media Player and Internet Explorer? Gee. I didn't know it was that bad..

  12. The OS is the glue between HW and apps/games by bersl2 · · Score: 1

    Why is it that this glue is (ultimately) dictating to the materials what properties they must possess? That's a pretty backwards way of doing things IMO.

    Yeah, stupid metaphor. I tried, at least.

    1. Re:The OS is the glue between HW and apps/games by Abcd1234 · · Score: 3, Interesting

      That's the wrong way to look at it. The DX guys are, in essence, acting as the negotiators between the game developers and the hardware manufacturers. The game dev folks tell the DX people what they'd like, in terms of feature set. The DX people then work with the hardware manufacturers to implement those features. It really does make a lot of sense. The game developers get what they need, in terms of feature set and APIs. The DX folks then get to work with the hardware manufacturers to ensure that the required capabilities are available and relatively consistent across hardware vendors.

    2. Re:The OS is the glue between HW and apps/games by bersl2 · · Score: 1

      That negotiation can be done with an ARB as well.

    3. Re:The OS is the glue between HW and apps/games by Abcd1234 · · Score: 2, Insightful

      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.

  13. Historical retrospective? :) by B3ryllium · · Score: 1, Interesting

    I must be the only person who misread it as "DirectX 1.0", like we were going to get some sort of historical retrospective from The Man Himself, Alex St John, on the travesty that was 1.0 :)

    1. Re:Historical retrospective? :) by Anonymous Coward · · Score: 0

      There was never a DirectX 1.0. Their first gaming API was called WinG.

  14. So they... by Anonymous Coward · · Score: 0

    have DX10 that is vista only and m$ is still re-hacking old technologys to acomodate itself

    "ExtremeTech: Speaking to that point, we know that the desktop in Vista is drawn using DirectX 9. What happens if you have a DirectX 10 card? Does the desktop still use DX9, or does that switch over and use DX10?

    Blythe: It continues to use DirectX 9. ... At the same time, we were making some minor tweaks to DirectX 9 to accommodate new features that were needed to do the desktop. "

  15. 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.

    1. Re:What obligation? by kihjin · · Score: 0, Flamebait

      Your thought process is familiar... Oh, it sounds like Microsoft's marketing strategy.

      Microsoft's obligation is as an ethical business. Perhaps there is no legal binding which requires them to backport all their software, but they've been so legacy happy in the past! Why not now? Because they know that Vista is essentially worthless. Sure, it may have a better privilege system (Thanks UNIX!) and, well... honestly, I don't think anyone really knows for sure anymore.

      Microsoft users are going to wonder: Why do I need Vista?
      Microsoft's answer will be: So you can play Half-Life 4.

      --
      This slashdot-related signature is a stub. You can help kihjin by expanding it.
    2. Re:What obligation? by skiflyer · · Score: 1

      So blame Half-life 4 for using a technology that you claim is unecessary, not microsoft for providing it and letting people upgrade or not.

      By your logic they should backport the whole OS and upgrade XP users for free. Legacy happy goes in the other direction... and it sounds like they're going to be doing a whole lot of that this time too.

    3. Re:What obligation? by Haeleth · · Score: 1

      Microsoft's obligation is as an ethical business.

      So... by your logic, Apple, which breaks backwards compatibility to force an upgrade on an almost annual basis, must be the least ethical business ever, while Microsoft has been acting like a saint for the last 20 years?

      Sorry, I just don't see it.

    4. Re:What obligation? by Aceticon · · Score: 1, Insightful
      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


    5. Re:What obligation? by Tim+C · · Score: 1

      Sure, it may have a better privilege system (Thanks UNIX!)

      You do realise that NT has always supported a much richer privilege system than Unix, right?

      Now, it's true that a lot of third party developers ignored it and force you to run as admin for no good reason, but that doesn't mean it doesn't exist.

    6. Re:What obligation? by joranbelar · · Score: 1

      Not only that, but let's not forget that Microsoft is also releasing DirectX 10 for the Xbox 360. So gee, I guess it's trivial to ensure games can continue to be developed for MS's new pet technologies like Vista and the 360, but it'd just be too much of an unmonopolistic time waste for them to bother ensuring compatibility with Windows XP.

      Yeah. Nothing to do with lock-in at all.

    7. Re:What obligation? by seriesrover · · Score: 1
      I do agree. If one buys an "off-the-shelf" product then thats it - thats what you bought, assuming it does what is advertised. Its purely good business sense to provide patches (ie. security) from that point out. What legal obligation is there?


      Perhaps I should go to Land Rover and ask them to update my 1966 Series 2 with a new spanking engine?

    8. Re:What obligation? by spoco2 · · Score: 1

      they've been so legacy happy in the past! Why not now?

      Erm.... you've completely got it wrong there... Microsoft has always been about the NEW operating system supporting things that ran on the OLD operating system... not the other way around.

      How many games that you play on XP now run on 98?

      Any?

      Any?

      NO...

      Dear god, give them a break.

    9. Re:What obligation? by Synistar · · Score: 1

      Mod parent up! Since this obviously shows the massive flaw in their statements.

  16. MS says no to openGL by Anonymous Coward · · Score: 0

    DirectX10 and Vista also means Microsoft will drop support for OpenGL in Windows.

    If looking just D3D part of DirectX - OpenGL 2.0 just already provides more tricks, faster and now - not in forthcoming future like Vista, it seems gamers won't be much voting for Vista.

    1. 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.

    2. Re:MS says no to openGL by mkosmul · · Score: 1

      That still means running OpenGL will be so much of a hassle that people will actually be forced into using DirectX. If you can use it, but it disables most of the visible cool stuff plus it's an old version which only supports a subset of current capabilities, it could as well not be there at all.

    3. Re:MS says no to openGL by ichigo+2.0 · · Score: 2, Informative

      Did you actually read his post?

      new OpenGL ICDs may be written that works with Aero.

      That's the exact same situation that is in XP at the moment, graphics card manufacturers have an OpenGL ICD included in their drivers.

  17. Exactly by spoco2 · · Score: 1

    How many games support OpenGL these days? DirectX runs on Windows and also both XBoxes, so why the hell would they do anything in OpenGL?

    While they're at it, why don't they convert everything over to OpenOffice and hey, just give up on Windows and switch to Linux?

  18. I got the last edition of directx 9 SDK by CrazyJim1 · · Score: 0, Offtopic

    I got the best version of directx SDK that I'll need for a long while. I may even use it if I get motivated to code my 3d fighter.

    1. Re:I got the last edition of directx 9 SDK by hh10k · · Score: 1
      I got the best version of directx SDK that I'll need for a long while.
      I remember people saying the same thing about DX8 when DX9 came out.
  19. 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.
    1. Re:Finally ate their own words... by master_p · · Score: 1

      ...or surfing pr0n at the same time.

    2. Re:Finally ate their own words... by Anonymous Coward · · Score: 0

      David Cutler must be enjoying this. They've decided to return to the NT 3.1 model of user mode graphics drivers. Next thing you know, they'll add the POSIX subsystem back.

    3. Re:Finally ate their own words... by I_Jonny_I · · Score: 1

      You know what I wouldn't give for the functionality you mentioned above? I wasted 3 months of my life trying to hack a way around this flaw and then I realized I was actually supposed to deliver the software and I had wasted most of my time on a futile effort, and needed to restart the project from the ground up leaving out other useful features.

  20. It's an INTERFACE goddammit by Flyboy+Connor · · Score: 3, Insightful

    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.

    1. Re:It's an INTERFACE goddammit by Animaether · · Score: 1
      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.


      Whoa, hey, hold on. How is Microsoft trying to do anything here? okay, probably they are, but just let me address a point you're making...

      Then game developers will simply add an option "activate advanced DirectX 10 features" to show off the cool stuff

      If the game developers are indeed capable of designing a little checkbox, or dare I say it, radiobuttons for DirectX 9 and DirectX 10 support, then they are already all set, no? I presume that the functionality of this checkbox/radiobutton would be to -not- call DirectX 10-specific functions when the user has it unchecked/set to DirectX 9. And if indeed they can simply not call these DirectX 10-specific functions by knowing which they are (as they very well should), then...

      take DirectX 9, add the new calls, and let them return "sorry, I cannot do that"

      Is completely unnecessary and a waste of development time, now isn't it?

      Either a developer will continue to develop exclusively for DirectX 9 which should work under DirectX 10
      or they will develop exclusively for DirectX 10, check whether DirectX 10 is supported on the system, and kindly inform the user that the game won't run if it's not
      or they will develop for DirectX 10 and gracefully fall back to only using DirectX 9-methods if DirectX 10 is not supported, either by a hard-coded effort, or by testing the DirectX API and checking whether a certain function is made available - if it is, use DirectX 10 - otherwise use DirectX 9; hard-coding would execute faster but be more work to track in development.

      None of the above scenarios requires Microsoft to actually -add- those functions to DirectX 9 and then return an error value - worse yet, that would just make life more difficult as you'd need two checks - one for older DirectX 9 installations (calling results in a trappable error/checking results in knowing the function doesn't exist) and one for the newer DirectX 9 (calling results in an error response/checking results in knowing the function does exist - then having to call it anyway to check for an error response).
    2. Re:It's an INTERFACE goddammit by ponos · · Score: 1
      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.

      This is only possible if the changes are minor and a 1-1 mapping between functions is available. Reading the article, it seems that you can't just map DX10 to DX9 because they are too different, you need to emulate DX10 using DX9, which is another deal altogether. Put simply, it won't work.

      Enforcing DX10 doesn't just promote Vista upgrades, it also enables immediate cross-portability of PC titles to the XBOX360, which is probably another strategic goal (PS3 draws upon PS2, XBOX360 draws upon the PC). On the other hand, the solution of OpenAL + OpenGL and possibly DX9 or SDL for other services is now a more attractive alternative. Also, bear in mind that the development cycles are relatively long and don't expect upcoming hit titles to be designed for DX10. The first "true" DX10 games should appear in the market at least 6 months after Vista launch and they aren't likely to be hit titles (say Unreal 3).

      P.
    3. Re:It's an INTERFACE goddammit by ichigo+2.0 · · Score: 1

      WTH are you talking about? In what way does that change the fact that Vista drivers are incompatible with XP? Not to mention that DX10 requires support for (almost) everything in the spec, there is no DX9 level hardware running with DX10 level drivers scenario available as in previous versions.

    4. Re:It's an INTERFACE goddammit by Anonymous Coward · · Score: 0

      Then game developers will simply add an option "activate advanced DirectX 10 features" to show off the cool stuff

      Rather like how people with cards that don't support DX9 PixelShaders can do that?

      Oh, wait...

  21. unless... by m874t232 · · Score: 1

    It better not be called "X11"...

    Unless they actually mean it...

  22. 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'
    1. Re:Give me a break! by tyldis · · Score: 1

      Backporting and backwards compatibility are not the same things.

    2. Re:Give me a break! by DRM_is_Stupid · · Score: 1
      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.
      No one is saying that Microsoft is the only one that does this gimmick, we're just calling a spade a spade. By the way, Apple isn't dropping backwards compatibility for their PPC to Intel transition.
    3. Re:Give me a break! by Anonymous Coward · · Score: 0

      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.

      No, not everybody. Some people. Not all. There are many different opinions and points of view, even on slashdot. Why is that a bad thing?

      Actually, it would be better if there were more wide and varied contributions around here, rather than rehashes of the same old preconcieved ideas.

    4. Re:Give me a break! by Gentlewhisper · · Score: 1

      >>No one is saying that Microsoft is the only one that does this gimmick, we're just calling a spade a spade.
      >>By the way, Apple isn't dropping backwards compatibility for their PPC to Intel transition.

      OH RLLY? HOW CAN I RUN MY CLASSIC APPS ON X86 MACS?

      Stop drinking the koolaid for a moment and answer that.

    5. Re:Give me a break! by mrchaotica · · Score: 1
      didnt Mac did that when going from OS9 to OSX?, and from PPC to Intel?

      I suggest you read about "Classic" and "Rosetta," because you have no idea WTF you're talking about.

      --

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

    6. Re:Give me a break! by mrchaotica · · Score: 1

      There's a difference between dropping compatibility with stuff that's two generations back and dropping compatibility with current technology!

      --

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

    7. Re:Give me a break! by Taimoor · · Score: 1

      Easy, it's called SheepShaver... Uses SDL, compiles for basically all *nix systems. And, as a bonus, you get rid of all those crappy little quirks Apple introduced with their classic envrionment.

      Anyway, to be quite honest, MacOS 9 was a piece of shit from the start and anyone who still relies on it for any serious work deserves to be... I'll let you fill in the blank. (That said, I still use a 68k mac with 7.6.1 to handle IRC and various other small things... Viva la motorola!)

      Ta ta!

      --Nick

    8. Re:Give me a break! by I'm+Don+Giovanni · · Score: 1

      Let me know when Apple backports Spotlight to OSX 10.3 and earlier. That would be *much* easier than backporting DirectX10 to XP, yet you didn't bitch about Apple not supporting its Panther users, did you?

      --
      -- "I never gave these stories much credence." - HAL 9000
    9. Re:Give me a break! by mrchaotica · · Score: 1

      Bah, Spotlight is just an application. If you're going to get upset about something, get upset about Core [Image|Audio|Data].

      And that I will bitch about, because it's actually comparable to the DirectX 10 issue.

      --

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

    10. Re:Give me a break! by DRM_is_Stupid · · Score: 1

      You know what I meant to say, as the link supplied was pretty self explanatory.

  23. Re:No One Cares by Anonymous Coward · · Score: 0

    And you do suck

  24. Say what? by Inoshiro · · Score: 1

    By that logic, I should get a free copy of Windows XP because a computer I bought in 1995 came with Windows 95! After all, since DirectX stopped working on Win95 with version 8.0a, why not get a free upgrade to XP to get me past the hump?

    How about those poor souls with NT 4.0? Stuck at DirectX 3, I hear. Damn.

    Microsoft is a company out to make money. You're lucky they even give out software updates for free; their EULAs certainly go out of its way to specify that you have no guarantees that what you bought from them works, let alone any kind of continued support.

    So you can either pirate Vista (because MS activation is not an issue, but chances are you pirate the games too if you do this), pay for Vista anyway, or use something like Cedega or Wine to game under Linux.

    I wouldn't be surprised if Apple had some tricks up their sleaves related to this for OS 10.5, assuming they get their heads of out the sand with regards to the final form of entertainment, interactive video games, that they don't have included in Front Row.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:Say what? by TheRaven64 · · Score: 1
      I think the difference is that there is no overlap. Windows 95 kept getting DirectX upgrades after Windows 98 and even WinMe were released. NT 4 was stuck on DirectX 3, but most NT users didn't care about DirectX. Windows 2000 got DirectX updates after XP was released.

      I wonder how much this will hurt DirectX 10 adoption. If I develop for DirectX 9 (or OpenGL) then I have a much larger target audience than if I develop for DirectX 10, and this will probably be true for some years after the release of Vista. If OpenGL starts to include comparable functionality (a big if, considering how slow the OpenGL ARB has traditionally been), and companies like nVidia start releasing OpenGL 3.0 (or whatever) drivers for all of their supported platforms then we may see game developers starting to use OpenGL, and get a good fraction of cross-platform development for free. It may be that Microsoft will see the lack of an extensions mechanism in DirectX bite them quite hard.

      --
      I am TheRaven on Soylent News
  25. The bottom line is.. by BadassJesus · · Score: 2, Informative

    that DirectX 10 forces you to upgrade to Vista, because all the new shiny metal hardware like new GPUs will be made for DX10.

    1. Re:The bottom line is.. by Anonymous Coward · · Score: 0

      I am not sure it is going to work out like that. Game developers (who ultimately are the key on what gets used) are not going to start creating games that only work on DX10 (thus Vista) anytime in the next 2-5 years, as to do so would be to eliminate the vast majority of your market.

      The advances (if there are any, I haven't RTFA) to DX10 will not be used because most developers will still be working from a DX9 platform.

    2. Re:The bottom line is.. by Threni · · Score: 1

      > DirectX 10 forces you to upgrade to Vista, because all the new shiny metal hardware like new GPUs
      > will be made for DX10.

      What, you think that having just spent £1200 on a new pc and a decent graphics card I'm about to spend another £250+ or whatever on Vista, plus £300+ on another graphics card, just so I can take advantage of the slightly differently rendered triangles DirectX 10 offers?

      Think again.

    3. Re:The bottom line is.. by Emetophobe · · Score: 1

      Microsoft also forces developers to upgrade to a newer version of Visual Studio if they still use 6.0. If you're a game developer and use the latest DirectX 9 SDK (April 2005), visual Studio 6.0 no longer works, you need VC7 or newer (unless you want to do some ugly hacks, you can get it to work with Visual Studio 6). And this isn't even in Vista, this is XP that they are breaking support with Visual Studio 6 and DirectX 9.

      I wrote about it in a previous post.

  26. so.. by wwmedia · · Score: 1

    does this mean Duke Nukem Forever will take another few years to develop??

    1. Re:so.. by MrCopilot · · Score: 1
      does this mean Duke Nukem Forever will take another few years to develop??

      Yes, Yes it does.

      --
      OSGGFG - Open Source Gamers Guide to Free Games
  27. Will share the same fate with RDRAM, then by unity100 · · Score: 1

    Expensive products that are forcibly sold, do not sell.

    DDR was on the go, they said. RDRAM was the hype, they said. Yet in 6 months time all mobo manufacturers resumed ddr models.

    1. Re:Will share the same fate with RDRAM, then by NexFlamma · · Score: 1

      I dont believe your theory applies to Microsoft products.
      Or did you miss out on the last 15 year of technology?

    2. Re:Will share the same fate with RDRAM, then by unity100 · · Score: 1

      This is a too drastic and too obvious step for ms.

      The gaming crowd would be unwilling to go out and get a new os for just a few new effects to go with games. As they wont, the card manufacturers will oblige with them, as well as game studios. You cant risk your customers for the sake of microsoft after a level of risk, as much money microsoft may give you to comply with new standards. Also soon emulators, peripherals, add on cards etc would pop up if dx10 includes that much goodies to go with, and still meet the market demand.

      So no vista.

    3. Re:Will share the same fate with RDRAM, then by ichigo+2.0 · · Score: 1

      I think you do not understand the gaming crowd. On one side is the ones who pirate all their games, and on the other those who buy all their games. The ones who pirate will pirate Vista, those who buy will buy Vista because another ~70 bucks is nothing compared to the many years they will use it, not to mention the price of their hardware. So the end result is that gamers will upgrade, the small percent who doesn't is either too poor (in which case they don't need DX10 as it's only useful on new DX10 cards) or too dumb (some people might disagree, this is just my opinion) to get Vista.

      I don't really understand what your point about "Also soon emulators, peripherals, add on cards etc would pop up if dx10 includes that much goodies to go with, and still meet the market demand." is? Obviously there will be graphics cards that support DX10, but they are backwards compatible, NVidia and Ati won't stop making DX9 drivers for XP. Emulators would be slow and useless, and would have to emulate large parts of Vista (and in that case why not just install Vista on your computer?) to get DX10 on XP.

    4. Re:Will share the same fate with RDRAM, then by ichigo+2.0 · · Score: 1

      Intel said that DDR was on the go, and that RDRAM was the way to go. AMD and a lot of others thought Intel was smoking crack, and turns out they were right. I seriously doubt GPU manufacturers will stop making DX10 cards in 6 months, because even if Vista is never released the DX10 cards will still run all DX9 games a lot faster than any DX9 cards today.

    5. Re:Will share the same fate with RDRAM, then by unity100 · · Score: 1

      This is not a matter of compatibility. Like, say, transform and lighting issue. It contributed much to gaming experience when it came up, and we had to acquire new cards with new directx to enjoy it. If something like that happens, and it requires vista, people will find other ways.

  28. False Dichotomy by aepervius · · Score: 1

    Those are not the same people asking for backporting, and new feature. I request backporting because I am cheap ass and do not want to buy a new system, install it, loose time hunting driver and patch, just to play the new games. JUST.FOR.FREAKING.DIRECT.10.

    Other wants new feature because they want the new shiny toys, or search for any excuse to bash MS, or simply try to see if upgrading is interresting.

    --
    C. Sagan : A demon haunted world:
    http://www.amazon.com/gp/product/0345409469/
    visit randi.org
  29. 2 Possibilities: by Brown · · Score: 1

    1) More than one person comments on Slashdot!
    I know it's a shocking idea, that people may have differing opinions rather than following dogma; in a proper, well-organised society, such people would of course be 're-educated'.

    2) We like bitching about things.

    -Chris

  30. Welcome to Slashdot by Frightening · · Score: 3, Funny

    Apparently you are new here.

    The slashdot paradigm with respect to MS is that we(the FOSS geek community) are right, they are wrong. In the most extreme of cases (such as when MS does something correct) we are right, they are *trying*, but they are still ultimately evil.

    Please don't get any hopes up just because you have been modded insightful. This is only a gesture, after which you are pretty much screwed. Kiss your karma goodbye.

    Regards,
    -F

    1. Re:Welcome to Slashdot by xtracto · · Score: 1, Funny

      Hi Mr. 976489

      I am not new here.

      Sincerely

      Mr. 837672

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    2. Re:Welcome to Slashdot by EnglishTim · · Score: 1

      Feh.

      Kids these days!

    3. Re:Welcome to Slashdot by Frightening · · Score: 1

      Haha. Proprietory software people love numbers, eh?

    4. Re:Welcome to Slashdot by LarsG · · Score: 1

      It is at times like these that I regret forgetting the password to my first /. account. :)

      --
      If J.K.R wrote Windows: Puteulanus fenestra mortalis!
    5. Re:Welcome to Slashdot by xtracto · · Score: 1

      what was your first slashdot username?

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
  31. XP Games Obsolete? by Anonymous Coward · · Score: 0

    So now all the game makers will start using DX10 and we have to up grade to Vista to run the latest games. Of course Vista sucks more CPU so we need new Machines.

    The game makers should boycott this new stuff and insist that any new technology be compatible with XP.

  32. MMORPGs by Anonymous Coward · · Score: 0

    In keeping with our policy of providing you with the latest technology we are switching all games to DX10. Effective immediately you will only be able to connect to our servers if you are running Windows Vista and DX10. For your convenience we have arranged discount deals with the following vendors: ( list of vendors )

    This announcement will of course be preceded by discounted one or more year lock up deals for server fees. Sort of like Everquest did before they announced the DX9 switch and once the switch went in a large number of the people who took the deal couldn't play because their video card wasn't up to par. What is it going to be like when the whole system don't cut it? Welcome to the real world.

  33. Misread by Dersaidin · · Score: 1

    "The graphics card companies obviously play a huge role" First read that as: "The graphics card companies obviously on a huge pay role" :/

  34. Public notice for Slashbots: by Anonymous Coward · · Score: 0

    In the interest of not being hypocritical, please accompany all whines about DX10 not being backported to Windows XP with a whine about Quartz 2D Extreme not being backported to OS X 10.3.

  35. Simple Opinion.. by DoctorDyna · · Score: 3, Interesting
    I think, honestly, game designers are going to be the deciding factor. Microsoft can do whatever they want with versions, support, backwards compatibility and directx. If game designers don't want to develop for DX10, then they won't. I'm going to go out on a very thick limb here and say that DX10 will still run all the DX9 features. As long as the relationship stays that way, then there is no problem, and nothing to discuss! This is all completely moot. I'm 100% sure we've all seen games that "require" Windows XP. We're basically crying that Microsoft is going to do the exact same thing again that they have done in the past.

    The printing on game boxes that read "Requires Windows 95" "Requires Windows 98" and "Requires Windows XP" will soon have a brother. Big shock guys, there is going to be a "Requires Windows Vista"

    --
    Windows has more viruses because linux has more virus coders.
  36. Re:ZONK IS BEHIND TACO IN DIRECTXXX ANAL ACTION 37 by Anonymous Coward · · Score: 0, Informative

    For anyone interested try doing a lookup of the icann info for the anti-slash.org domain.

    Then try throwing the phone number back at google and see what you get.

  37. Re:Duh - but what's really going to happen? by pbhogan · · Score: 2, Insightful

    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.

  38. Re:Duh - confused =( by penguinbrat · · Score: 1

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

    I'm still on my first cup of coffee, which may be why I'm confused here - but I was under the impression that all the hardware up till now (IE: Vista) had to support the graphics interface, not the other way around where the graphical sub system had to support the hardware. Isn't this why you would see "Supports OpenGL/DirectX#!!!" on packaging of the given video card?

    If I recall correctly, Linux went through a major change in the module structure and there for all the drivers had to be re-written (IE: NVidia), but none of graphical subsystems had to (IE: OpenGL,SDL,etc..). Isn't this essentially the same thing?

  39. More info about new driver model by ipoverscsi · · Score: 1

    The largest reason DX10 will not be on XP is because of the new driver model. For more information about how it is substantially different than the driver model in XP, please see this MDSN blog:

    http://blogs.msdn.com/greg_schechter/

    This post in particular is particularly of interest as it explains the interaction of the new window manager with the new driver model:

    http://blogs.msdn.com/greg_schechter/archive/2006/ 04/02/566767.aspx

  40. DRM? by The+MAZZTer · · Score: 2, Insightful

    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...

  41. Oh geez. U so smart!! by Viewsonic · · Score: 1

    "You just take DirectX 9, add the new calls, and let them return "sorry, I cannot do that"."


    And then you end up with a black screen. Then what???

  42. What I'd really like to see... by Khyber · · Score: 1

    ...is a true universal standard. Remember back when we had Rendition Verite GL, nVidiaGL, ATiGL, MesaGL, GLide, PowerLab GL and Direct3D? Now, it's mainly OpenGL and D3D now. One of these two is going to win out, personally I'm hoping for OpenGL to be the absolute standard, not because I hate Microsoft, but because honestly I like having those extra few FPS. As for sound, I don't know what to think. AC97 is nice and all, but I'm still pretty much an SBLive user - gotta have all of those neat effects for my guitar that's run thru the line-in jack, not to mention the kX drivers (3rd party) work better than creative's OEM (The line-noise issue is a driver problem fixed in the kX audio drivers, the problem being an improper routing of sound channels and mixing.)

    --
    Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    1. Re:What I'd really like to see... by 99BottlesOfBeerInMyF · · Score: 1

      One of these two is going to win out, personally I'm hoping for OpenGL to be the absolute standard...

      DirectX == Windows only. Ergo, unless all other OS's die, OpenGL will remain. Thus, it is the only option for a real standard.

  43. Crappy analogy by everphilski · · Score: 1

    ... Games are not consumables (like detergent). You still have the products you already own, they will still work in either XP or Vista, and game designers can choose to use DX9 (or corelease). DX10 is just an API.

    1. Re:Crappy analogy by Aceticon · · Score: 1

      Actually games are a bit like ball-point pens: there's only so much fun you can have with a game before it ain't fun anymore, at which point you have to get a new one if you want to have more fun.

      In that sense, they work close enough like consumables the my metaphor in the post above works.

    2. Re:Crappy analogy by cskrat · · Score: 1

      Consumables, in the same sense as detergents and cheap ball-point pens, have the characteristic of being replaceable by a similarly functioning competitor. Some forms of software nearly meet this model; examples of such include office/productivity software, file compression utilities, image/artwork editors, compilers, webbrowsers and telecommunications software. This analogy is not broken by the mere fact that customers often prefer one brand or product line to another, such as prefering AutoCAD to RealCAD, since the analog to this exists in consumables as well, such as prefering Tide to All.

      Games, however, are an entertainment medium, and therefore different rules apply. Games, like movies, books and music, are charicteristcally unique from one another. For example, Harry Potter is a different experience than Lord of the Rings; even though both may share some traits, neither is a direct substitute for the other in that after experiencing one, the other is still a novel experience.

      As for the notion that the game is disposable, some may view a game as being the same sort of purchase as a movie ticket in that you pay your money, sit down and enjoy it for however long it runs and then that's the end of it. On the other hand, some may view it as being more along the lines of purchasing a movie on VHS/DVD/HD-Ray where you may view it just a couple times or you may view it a hundred times.

      A better analogy might be in cinemas that are required to upgrade their sound systems in order to be allowed to open with the newest action titles but still have the ability to play titles based on older formats. You, as a consumer may be required to upgrade to a newer version of Windows/DirectX in order to play Half-Life 4 but you will still be able to play the older Half-Life 2 on your WinXP/DirectX9.0c machine. This is no different from when you had to upgrade from WinME to WinXP in order to play Half-Life 2.

      Another analogy to consider since you seem to like washing machines:
      If Whirlpool develops a better suspension system for their 9300 Duet washing machine than they had on their 9150 (the 9300 is this year's replacement for the 9150), should they be required to support the customers that purchased a 9150 just last year by offering a free upgrade of the drum suspension? Should GM offer a free upgrade for all '06 Corvettes to give them the same fuel injection system that's in the '07s? Should Microsoft port new technology to an older operating system if there is no positive return on investment in doing so?
      A good answer to the above three is "No."

      But for the argument of responsibility to consumers I'm going to offer three examples that would be well answered with a "Yes."
      If the 9150 destroyed its transmission belts on a monthly basis, should Whirlpool recall the units and address the issue? If the '06 Corvette was shown to be likely to snap a tie rod connector on hard corners, should GM issue a recall to replace that mechanism? If a new exploit was discovered that allowed a malicious web site to wipe your hard drive, should Microsoft release a patch to fix the problem?

      Also, please remember that, in software, backwards compatability implies that you can run Office 6 on Vista but you can't run Office 11 on Win95.

      --
      My God! It's full of eval()'s.
  44. Is XP that old? by Peter+Bonte · · Score: 1

    Vista is not based on the new longhorn code but is a glorified XP, a lot of business apps and features get implemented in XP but not the ones for consumers. Also XP is not old, its not 5 years of age, its brand new, its the newest Windows currently available so you can't really compare it with an old linux kernel and the Mac OS. In fact its more comparable with WMA, QT, Quickdraw, OpenGL, ...

    1. Re:Is XP that old? by I'm+Don+Giovanni · · Score: 1

      "Vista is not based on the new longhorn code but is a glorified XP, a lot of business apps and features get implemented in XP but not the ones for consumers. Also XP is not old, its not 5 years of age, its brand new, its the newest Windows currently available so you can't really compare it with an old linux kernel and the Mac OS. In fact its more comparable with WMA, QT, Quickdraw, OpenGL, ..."

      First, Vista is based on Windows Server 2003, not XP.

      Second, try this on for size:
      Before Mac OS Tiger was released, the following could have been uttered by a malcontent such as yourself:
      "Tiger is not based on new code, but is a glorified Panther. Also, Panther is not old, it's not 5 years of age, it's brand new, it's the newest Mac OS currently available so you can't really compare it with an old linux kernel. SO THERE IS NO EXCUSE FOR APPLE NOT TO BACKPORT SPOTLIGHT AND GADGETS TO PANTHER!! APPLE IS FORCING UPGRADES!!"

      The above is true, but you guys ejaculated over the Tiger specs, without any demands that Apple backport Spotlight and Gadgets to Panther, which could've been done quite easily.

      The point is, 90% of new features in a new OS could be backported to the previous version of the OS, be that OS WIndows, Mac, Linux, or whatever. So why are you bitching that Microsoft isn't backporting everything to XP when you give Apple, et al, a free pass? And actually, Microsoft is backporting more of Vista's features to XP than Apple, et al, has ever done regarding their OSes.

      --
      -- "I never gave these stories much credence." - HAL 9000
    2. Re:Is XP that old? by snuf23 · · Score: 1

      "Also XP is not old, its not 5 years of age, its brand new, its the newest Windows currently available so you can't really compare it with an old linux kernel and the Mac OS."

      You're right! Windows XP isn't 5 years old. It's only 4 years 8 months old! Windows XP was first released on October 25, 2001,

      As for comparisons with Mac OS. When OS X was released NO OS X applications ran under Mac OS 9. Developement of OS 9 apps ceased and new software was developed for OS X. Any computers that couldn't run OS X were orphaned.
      If anything this is more restrictive than Vista. When Vista comes out SOME programs will be Vista only, but many will work on 2000, XP and Vista.

      --
      Sometimes my arms bend back.
    3. Re:Is XP that old? by Peter+Bonte · · Score: 1

      X10 isn't an 3P app or an OS, its more comparable with Apple's QuickTime and QT6 was available for Windows, classic and osX. The best thing you can compare X10 with is openGL. OSX also was a totally new UNIX based system so you have to give some credit here, osX at first wasn't always the best OS.

    4. Re:Is XP that old? by Peter+Bonte · · Score: 1

      Gadgets are .. um .. gadgets and yes Apple had no excuse not to implement it in Panther, a shareware app did the job. Who says we where happy with this? Spotlight couldn't be backported and as a matter of fact os9 more or less had this feature before osX so glad you brought this up. X10 is necessary for playing games, not some gadget.

    5. Re:Is XP that old? by snuf23 · · Score: 1

      Direct X 10 on Vista cannot be directly compared to just OpenGL. It involves a complete overhaul of the driver structure in Windows. Also Direct X covers more than just 3D graphics with elements such as DirectSound and DirectInput.
      Ripping out the old kernal mode driver structure is a pretty big change for Windows, I'm sure why people think it would just be simple to retrofit it to XP.

      --
      Sometimes my arms bend back.
    6. Re:Is XP that old? by Peter+Bonte · · Score: 1

      MS is again making it way to complicated :(

      If MS keeps there word then WinFS, Avalon and Indigo will be ported to the W2003 and XP systems, they can and want to do extreme ports for the business market but can't port a game API driver thats outside the kernal?

    7. Re:Is XP that old? by snuf23 · · Score: 1

      In case you haven't heard at least that plan for WinFS has been shelved.

      --
      Sometimes my arms bend back.
  45. The Death of DX10 by ivan256 · · Score: 1

    If they didn't remove DX9 support from Vista, game developers would be crazy not to continue writing DX9 games instead. What does DirectX 10 have to offer other than 0% market share for the forseeable future?

    1. Re:The Death of DX10 by PhoenixPath · · Score: 1

      Dx9 will be supported in Vista. It will be a seperate API than DX10, however.

      The issue here is that DX10 will not be released for Windows XP.

    2. Re:The Death of DX10 by ivan256 · · Score: 1

      The issue here is that DX10 will not be released for Windows XP. /me hands you a captain obvious hat.

    3. Re:The Death of DX10 by Anonymous Coward · · Score: 0

      Actually, your initial comment that elicited his reply was:
      "If they didn't remove DX9 support from Vista, game developers would be crazy not to continue writing DX9 games instead."
      /me hands you a learn to proof-read your posts hat. ;)

    4. Re:The Death of DX10 by ivan256 · · Score: 1

      It says exactly what I meant...

      I was not asserting that they *did* remove DX9...

  46. consoles? by deviceb · · Score: 1

    I stopped playing consoles when i was a teenager.
    MS does have a monopoly on games because of DX. -If you are playing any cutting edge games.. your playing them on Windows. It's sounding like this will become rock solid with dx10.
    They should be slapped with a antitrust lawsuit seeing how much money the gaming industry pulls in every year. The main reason besides grahics for myself using WinXP is gaming.. If i could ditch MS i would. Perhaps they know this is true for many people.

    I would support a antitrust case on this one.

    --
    Kill your TV
  47. 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.

    1. Re:This is slashdot... by mbourgon · · Score: 1

      Wow. It works! Microsoft and DRM. Come on, Karma!

      --
      "Sometimes a woman is a kind of religion, she can save your soul & set you free from all your sins" - Bad Examples
  48. Re:Duh - but what's really going to happen? by PhoenixPath · · Score: 1

    LMAO!

    Yeah...right...Cuz game developers *always* code to the lowest common denominator and *never* push the envelope to get better graphics/performance.

    And no OS / program / API should *ever* limit backwards compatibility in exchange for *current* compatibility, performance gains, stability, and ease of future improvements.... /Sarcasm

    Seriously, we've been backwards compatible long enough. The time to change to a better model and framework is long overdue. Providing compatibility would not only delay the project, but the cost, effort, and loss of performance and ease of future development on a far superior model would far outweigh any benefit.

  49. antitrust by Oblio · · Score: 1

    I wonder if Microsoft would have made this same decision (not backporting at least a skeleton DX10 to XP) if the DOJ antitrust case hadn't had the rug pulled out from underneath it.

    --
    Pax -- Ob
  50. Re:Duh - but what's really going to happen? by pbhogan · · Score: 1

    Lowest common denominator? Hardly. But game developers aren't stupid, and more importantly publishers aren't stupid. It doesn't help having the most cutting edge engine if most of your customers can't play the game. The usual decision is: pick the most widely used platform (right now that's XP) and push it to the limit. 95% of game development companies haven't pushed XP/DX9 to the limit yet. Within two or three years the most widely used platform will probably be Vista and then it's a different story. Of course some of the longer term development projects (2-3 years) might make that decision now with the future in mind and that's okay. Of course those are usually the ones who try to push the absolute limits of technology, but they're a minority. Seriously, how many games do you see out on the horizon that need what DX10 has to offer? A few. More importantly, I'm NOT saying DX10 should exchange backward compatibility for performance gain, technological advancement, etc. I'm just saying DX10 should support XP. Of course it wouldn't run quite as well on XP as it does on Vista, but that's okay. It means developers can write for the new platform without sacrificing the currently dominant platform, and when their game comes out it won't force people to upgrade. For most developers the slight speed hit won't matter. For the hard-core gamers and Carmack-esque developers out there, Vista will be there. Essentially Microsoft is forcing developers to spend alot of time writing their own abstraction layers which should be inherent in DX10 in the first place, which delays every major game in development instead of delaying DX10 slightly. Yay. Don't tell me Microsoft doesn't have the money or developers to throw at this project if they had really wanted to get it out in the same timeframe. Heck, they could have had an entire concurrent project team working on it with no impact on the main DX development effort. The entire multimedia framework of your operating system is more than enough justification for this.

  51. The downfall of DirectX? by Dachannien · · Score: 1

    The driving force behind adoption of DirectX 10 (or is that DirectX X) isn't Microsoft or the release of Vista. It's game developers, and more importantly, game publishers. If a game publisher sees that 10% of the home user Windows install base is Vista, 80% is 2000/XP, and 10% is earlier versions of Windows, the publisher is going to come to the conclusion that developing for DirectX 10 - and limiting themselves to the meager Vista install base - just isn't worth their time and money.

    Game aficionados may pay $60 for a game, but they're not going to pay an extra $100+ for the operating system just to play that game until there's a substantial base of games only available under the new OS (much like consoles sell better when there are a lot of games out for it). So, if Microsoft is really doing this to get people to laterally upgrade to Vista, that's not a winning strategy. The better strategy, if they're trying to achieve forced upgrades, would be for each subsequent version of DirectX to exclude the third-newest OS (in this case, Windows 2000) so that those users will upgrade, while the game publishers see the XP install base and opt to develop for the newest DirectX version.

    I say this ruefully, though, because I'm still using Win2k and have no desire to upgrade, because it works just fine for home use, without all the feature bloat that XP and especially Vista provide.

  52. Major misconception here? by PhoenixPath · · Score: 2, Insightful

    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.

    1. Re:Major misconception here? by jofi · · Score: 1

      > Does a new Linux kernel backport it's improvements to a previous kernel? Hell no. But the new kernel doesn't cost anything.

      --
      Blame the user, not the software.
    2. Re:Major misconception here? by Anonymous Coward · · Score: 0

      I call bullshit. Are you saying that new versions of IE that came out when Windows Me couldn't be installed in 98?

      What about Direct X 8/9 for Windows Me when Windows XP was out?

      I definately remeber quite a few XP features backported to Windows 2000 in SP4.

    3. Re:Major misconception here? by kaffiene · · Score: 1

      You are a moron.

      Microsoft have released several updates to DX which are substantial upgrades and have done this on existing machines.

      It's a fucking API. APIs are DESIGNED to provide functionality over a potentially changing base implementation. In JUST THE SAME WAY DirectX has ALWAYS done it and OPENGL does it RIGHT now.

      If you beleive that crock of shit in the article, you are seriously deluded.

    4. Re:Major misconception here? by PhoenixPath · · Score: 1

      You are a moron.

      Sorry. I simply cannot take anyone seriously after they start a post in such a sophmoric way. Enjoy your recess.

    5. Re:Major misconception here? by PhoenixPath · · Score: 1

      Absolutely *no* major changes needed to be made for the compatibility you mention. You are confusing backporting with backwards compatibility.

      Backporting support for DX10 to XP would require an absurd amoutn of work, effectively making the DX10 rewrite a complete waste of time.

    6. Re:Major misconception here? by PhoenixPath · · Score: 1

      No. You misunderstand. I am not talking about simply upgrading the linux kernel to the new version. I am talking about backporting the major improvements in the new kernel to an older version.

      This does *not* imply a version change.

      When you replace your Linux kernel, you do *not* modify the existing kernel to support major improvements in the new kernel.

      Well....unless you have no life, nothing of any value whatsoever to add to society, and no job. Of course...this *is* slashdot. I probably just nailed over half the userbase dead-on with that description.

    7. Re:Major misconception here? by kaffiene · · Score: 1

      Killer argument, you must be proud of yourself.

      I'm 35, and a veteran software engineer, by the way. But keep working on those ESP skills.

    8. Re:Major misconception here? by PhoenixPath · · Score: 1

      Thanks for the advice, mine to you would be not to be so juvinile when posting.

      AS for being proud? Well, I didn't respond in kind, so I guess I am.

    9. Re:Major misconception here? by kaffiene · · Score: 1

      Calling moronic comments moronic is not juvenile, it's just stating facts.

    10. Re:Major misconception here? by PhoenixPath · · Score: 1

      Oh, well...in that case...

      You're an idiot.

      You cannot stop for one second and think logically about what they are doing, why they are doing it, and why they are *not* caving in to these ridiculous demands. ...just stating facts.

  53. too late, there was already X10 ;^) by slew · · Score: 1

    young-ins, it's too late. there was already X10. ;^)

    X10 was the first popular version of the X-window system releaased back in '86, shortly redesigned and replaced by the first version of X11 that we know today...

    As I recall, some of the knocks against X10 was that it was slow, somewhat platform specific, kind of a resource hog and the protocol was not very backward compatible with previous versions... Hmm, that kindof reminds me of some other software ;^)

  54. Re:I *hate* when people make me do this: by Sleet01 · · Score: 0

    Erroneous should, of course, be spelled - this way, not ^ that way.

    --
    -- Let him who is without spelling error ignite the first flame --
  55. Re:Duh - but what's really going to happen? by PhoenixPath · · Score: 1

    I'm sorry, I gotta stop laughing. Give me a sec...

    Okay, I'm better now.

    What is stopping devs from writing for both DX9 *and* DX10? (Vista will support both)

    Why should MS backport elective technology to an old platform? Consider:

    Blizzard Develops Warcraft 1. Then, after a few patches and a long dev cycle releases Warcraft 2. Warcraft 2 improves graphics and network play. Did you hear *anyone* asking, no, demanding that Blizzatd update Warcraft 1 to support the improvements to Warcraft 2? No.

    I fail to see how this is *any* different, other than MS having, in the past, provided backwards compatibility. They never *backported* a version of DX to support a *new* version.

    Can you see the difference here?

  56. So, what does it have that OGL2 doesn't? by AndyS · · Score: 1

    OpenGL2 has this unified shading model

    I don't think it has tesselation on GPU (as far as I know)

    but what else am I missing? What other key features offered by D3D10 aren't supported by OpenGL and which are? Obviously companies are going to offer some extensions, but has anything been suggested?

    Just curious :)

  57. Re:Duh - but what's really going to happen? by pbhogan · · Score: 1

    What is stopping devs from writing for both DX9 *and* DX10? (Vista will support both) Absolutely nothing. You've just made my point. This is *exactly* what I'm saying is going to happen. That was the entire point of my first post (or do you not understand what an abstraction layer is?) But it shouldn't HAVE to happen. Are you a game developer that has had to deal with this? I am. I'm just putting forward my past experience with this issue. It's a matter of efficiency. One company could write one for their own product - or - hundreds of other companies have to write one for themselves. Ergo, one company could delay their product slightly (if at all) - or - hundreds of other companies have to delay their products with extra development and testing on multiple platforms and driver combinations, etc. I fail to see how this is *any* different, other than MS having, in the past, provided backwards compatibility. They never *backported* a version of DX to support a *new* version. A new version of DX still ran on the existing platform. That's the issue here, not the backwards compatibility of the library. All a user had to do in the past was download (or install from the game cd) the new DX runtime on their existing Windows installation, not run out and buy a new operating system and possibly upgrade their hardware in the process. I could be wrong, but as I recall when MS made the jump from Windows 98/ME/2000 to XP DirectX ran on all those platforms, probably a little better on XP, but it ran on old systems.

  58. Re:Duh - but what's really going to happen? by Anonymous Coward · · Score: 0

    Yeah, the difference is you're trying to compare a game to an operating system. An operating system is an entirely different animal than a game. An operating system has an entirely different purpose. To expect people to pay $200 for a new operating system, which implements ideas that are--quite honestly--not all that ground breaking, so they can play a $50 game is ludicrous.

  59. Microsoft Altruism by Doc+Ruby · · Score: 1

    why it will only be for Vista (and not for XP)


    To force XP users to upgrade to Vista. By requiring DX10 in new versions of Office with non-backwards-compatible file formats. How naive can you be not to guess that?

    I expect Vista to come complete with plenty of "DRM" features designed to kill Wine and other Windows emulators/substitutes. If people could use DX10 under Linux, we wouldn't be as locked into Microsoft's monopoly.
    --

    --
    make install -not war

    1. Re:Microsoft Altruism by Anonymous Coward · · Score: 0

      Has Microsoft stated Office required DX10? Are there no backward-compatible formats in office? Didn't think so.

      Geesh, quit trolling.

    2. Re:Microsoft Altruism by Doc+Ruby · · Score: 1

      "How naive can you be?" I asked. The answer: Anonymous born yesterday Coward naive.

      And stop calling me "Geesh". I'm not Geesh.

      --

      --
      make install -not war

  60. API's being extended - not broken. by Petersko · · Score: 1

    "Well, as someone already pointed out in another reply somewhere above, this is a FUCKING API. APIs should be designed NOT TO CHANGE when the internals change. So, either Microsoft still hasn't learned how to write a proper API, or they DELIBERATELY CHOSE to make it incompatible."

    Actually, my understanding is that API's are supposed to be extensible. I don't think they're dropping support for pre-DirectX versions from DirectX 10. Your older games should run fine. The original API's are not broken. They're extending the API, providing additional functionality that can be called upon should the software developer choose to do so.

    If they write the game to DirectX 9 standards, it'll run fine. And if the game companies want the widest possible adoption of their product, they'll do exactly that until such time as Vista is the prevalent OS.

    You're getting angry about the wrong thing.

  61. Microsoft broke Visual Studio 6.0 with latest SDK by Emetophobe · · Score: 1

    The latest version of the DirectX 9 SDK (April 2005) pisses me off. You can no longer use Visual Studio 6.0 with it, Microsoft forces you to upgrade to a newer version of Visual Studio. I downloaded the free Visual Studio 2005 Express Edition which is actually pretty good, but it still pisses me off that I can no longer use my legit copy of Visual Studio 6.0. The free express version doesn't come with a resource editor.

    It is possible to get the latest DirectX SDK working with Visual Studio 6.0, but it's a pain in the ass. Here is a website that goes into detail on howto get it working.

    Here are some of the steps you have to go through (involves installing/uninstalling multiple different DirectX SDK versions):

    1. Download the April 2005 DirectX SDK (scroll down the page to the "Older SDK Releases" section
    2. Download the April 2005 MS Platform SDK (scroll down the page and download PSDK-x86.exe)
    3. Go to Keith's site and download the April or June DirectX 9.0c D3DX Only Installer Download
    4. Assuming that you are using the Summer or October 2004 DirectX SDK, go to the Lib folder and copy the Dxerr9.lib and Dinput8.lib files to a temp folder.
    5. Uninstall the current DirectX SDK.
    6. Install the MS Platform SDK (assuming you don't already have the latest version installed)
    7. Install the April 2005 DirectX SDK
    8. Install the D3DX runtime files you downloaded from Keith's site
    9. Reboot
    10. Go to the Lib\x86\ folder where you installed the April 2005 SDK and backup the Dxerr9.lib and dinput8.lib files
    11. Copy the Dxerr9.lib and dinput8.lib files from your previous Summer 2004 or October 2004 into the \Lib\x86 folder.

    And here is the reason why DirectX is now broken with Visual Studio 6.0

    In the case of the Dxerr9.lib file, the reason for this is that MS compiled that library (don't ask me why they did this with only this file) with buffer overrun/security checking (as they do with all their .Net libs now, hence the reason VS6 no longer works with DX) and any library function which makes calls to that library (e.g. to DXGetErrorString9) will cause linker errors

    Also:

    In the case of the dinput8.lib file, you will get this error when compiling a debug app. For some unGodly reason, this file seems to contain corrupt and/or incorrect debugging information. So you will see something like this if you don't use the older version. Incidentally, when comparing these legacy files, in April 2005 SDK, MS decided to include versions that are older than those in the October 2004 Update. Don't ask.

    They broke Visual Studio 6 on purpose to force developers to upgrade to a more recent version of Visual Studio (with .net no doubt).. Luckily for a poor person (student) like myself, Microsoft offers free Visual Studio versions (Express Edition), which you can download here.

  62. The real reason. . . by kimvette · · Score: 2, Insightful

    why it will only be for Vista (and not for XP) is:

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

    --
    The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    1. Re:The real reason. . . by Anonymous Coward · · Score: 0

      Insightful? I intended my post to be a joke. It's obviously an off-the-hip cynical remark regarding the incessant delays.

  63. How about the people in front of DirectX 10? by froglover · · Score: 1

    Personally, I'd much rather learn about the people in front of DirectX 10. Nah, silly that Slashdot wastes time on Microsoft's branding-by-familiarizing operations. Of what use is it to anybody to know the people behind DirectX 10. Might as well know the people behind one's favorite shampoo or tire maker. "The People Behind Ajax Shampoo". Wow, gotta see it!

  64. Who really gets hurt? by Anonymous Coward · · Score: 0

    It's not all about "screwing the customer", forcing people to buy Vista to play games. What stands out is that MS is hurting developers with this move. Pioneering developers using the new DX10 get to deal with the bulk of their customer base hemming and hawing about buying Vista, and buying XP compatible games instead. By the time any reasonable number of Vista systems are sold/upgraded, those pioneers will be sitting in the bargain bin. Those early developers will also get slammed with support calls and returns from customers that are caught off guard by this sudden change in sale paradigms - instead of just demanding a reasonably recent computer, there's a hard line dividing the Pee Cee from the Pee Cee Three Six Oh.

  65. one question by Anonymous Coward · · Score: 0

    so with this directX10 it will be possible to run
    a game "on the desktop" without having a seperate window it is running in,
    and maybe even have it be transparent (so i can see the desktop while fragging
    monsters), plus so like doom in any resolution i chose, interactive rescaleable ...
    weeeh :)

  66. Wont be upgrading anytime soon by Some_Llama · · Score: 1

    I will "miss out" on DX10, and i guess that's fine, but i'm not an early adopter, sheesh I was running 98SE (stable mind you) until mid 2003.

    Making DX10 vista only is just a bad decision in my mind, I can see the advantages but they aren't enough to get me to early adopt, esp when the 3 year old rig i have now runs all of the latest games that are out and I understand XP enough to know the solution to any current driver/game/hardware problems. (and be IT support for the OS btw).

    SO to sum up, the parent makes a great point, i think it has some interesting parallels with the HD blu-ray war going on right now, just not enough to justfy upgrading as soon as it comes out.

  67. I know a troll when I see one, and that's no troll by NRAdude · · Score: 1, Insightful

    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.

    --
    without prejudice
  68. WE MUST DESTROY DIRECTX10 by AragornSonOfArathorn · · Score: 1

    Apologies to KOMPRESSOR

    --
    sudo eat my shorts
  69. Looks like Microsoft is thinking ahead... by Anonymous Coward · · Score: 0

    Are you ready for Doom IV?

  70. Hard-hitting Journalism at Extremetech by callott · · Score: 1

    The very first sentence of the article starts like this:

    "When DirectX 10 rocks your PC with the release of Windows Vista early next year,"

    I had to do a double-take to make sure I was reading the content and not an ad. (Although I'm not sure there's much difference between the two in this particular case.)

  71. It puts the X in XXX by Impy+the+Impiuos+Imp · · Score: 1

    Previous releases added programmer control APIs for not just 3D, but sound control, joystick devices, and eventually network gameplay. DirectX 10 continues the growth by adding APIs for DirectWaldo, the network control and tactile feedback via specialized electronic gloves, DirectRhinovision, or "Smell-o-vision" scent output devices, and DirectDildonics, for networked remote control of sexual stimulation devices.

    --
    (-1: Post disagrees with my already-settled worldview) is not a valid mod option.
  72. Re:Duh - but what's really going to happen? by PhoenixPath · · Score: 1

    A new version of DX still ran on the existing platform.

    Ah... You are under the impression XP will be considered 'the existing platform'. MS has already focused it's efforts on Vista. Vista will be 'the' existing platform.

    I could be wrong, but as I recall when MS made the jump from Windows 98/ME/2000 to XP DirectX ran on all those platforms, probably a little better on XP, but it ran on old systems.

    Not *all* versions ran on *all* operating system though. For Instance, just try installing DX9 on a Windows 95 machine, which *does* support DX8 :)

    Perhaps, though, Microsoft should have given this new API a different name. Calling it DirectX (even though it shares *no* functions with any other DX version) was probably a mistake, but...branding wins out. Perhaps DXe (enahanced) 1.0?

    Point being, this is new. It's not an upgrade, it's not the same API, in fact it's been rewritten from the ground up...*For* Windows Vista.

  73. Re:Duh - but what's really going to happen? by PhoenixPath · · Score: 1

    Not groundbreaking.

    Huh.

    I suppose this is a purely subjective conjecture. Arguing it with you would be pointless. I suppose I could simply mention Memory Heaps, moving the drivers from Kernel to User mode, Rewritting the Audio subsystem and, of course, rewritting DirectX from the scratch....

    But of course you would consider none of those groundbreaking.

    Also I seem to recall *many* games that would *only* operate in Windows XP. Not Windows ME, Not Windows 98,a nd Not Windows 2000....very shortly after XP came out. I am not the least bit doubtful that the very same thing will happen upon the release of Vista. Of course, people complained about having to pay for an OS upgrade to play a game then, as well.

    [sarcasm]

    I guess performance, features, stability, and security are just not all that important to gamers.

    [/sarcasm]

  74. Re:Duh - but what's really going to happen? by Anonymous Coward · · Score: 0
    I suppose this is a purely subjective conjecture. Arguing it with you would be pointless. I suppose I could simply mention Memory Heaps, moving the drivers from Kernel to User mode, Rewritting the Audio subsystem and, of course, rewritting DirectX from the scratch....


    Yeah, moving stuff out of kernel to userland mode is really ground breaking...stuff that was done by other OSs quite a while ago. Modularity in design isn't the least bit ground breaking...unless you're limiting yourself to the Windows world as M$ fans are wont to do.
  75. Re:Duh - but what's really going to happen? by PhoenixPath · · Score: 1

    Right. other OSes have done it for ages...MS doing it means nothing TO USERS OF THOSE OSES.

    It means a HELL of a lot to windows users.

    M-dollar fans? Never heard of 'em.

    *anyone* using windows should appreciate thet they are finally doing this. Not just their fans.

    Thanks for playing, but I'm not really into arguing with folks who see *everything* MS does as a "Bad" thing. Kind of pointless, like banging you head against a wall. You guys are worse than fanboys.

  76. Re:Duh - but what's really going to happen? by Anonymous Coward · · Score: 0

    Fanboys such as yourself?

    When did I say ANYTHING about it not being good for Windows users? I just said it wasn't ground breaking...and it's not. They're late through the gate. You apparently chose to infer from my statements that they aren't making progress. Not to mention, all the features that held some promise of being revolutionary were all either delayed or cut.

    I'd just like to point out that users of Windows would be in a bad spot if weren't for detractors of Microsoft. Afterall, if it weren't for Firefox and Opera, you'd still be stuck with IE 6.

    "Thanks for playing."