Slashdot Mirror
AMD Previews DirectX 11 Gaming Performance
An anonymous reader writes "AMD invited 100 people up to their private suite in the hotel that Quakecon 2009 is being hosted at for a first look at gaming on one of their upcoming DirectX 11 graphics cards. This card has not been officially named yet, but it has the internal code name of 'Evergreen,' and was first shown to the media back at Computex over in Taiwan earlier this year. The guys from Legit Reviews were shown two different systems running DX11 hardware. One system was set up running a bunch of DX11 SDKs and the other was running a demo for the upcoming shooter Wolfenstein. The video card appears to be on schedule for its launch next month."
What?!? The standard always comes before the hardware, DX11 is an API and a (defacto) standard. We could go back to the OpenGL model with ARB extensions for new features that are implemented differently by each party until the standard catches up, but that was tough on everyone. It was tough on the hardware guys because they inevitably implemented features that didn't make it into the standard, it was hard on the standards body because they had to arbitrate between the different implementations to pick a winner, and it was hard on the software guys because they had to support the whole mess. It's a primary reason that DX won over OpenGL in the marketplace.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
How about they fix their win7 drviers for not-so-old but still great performing cards like the X1800 ? Nvidia customers are having a great time with win7 atm, and even Intel integrated graphics are performing better, but I've got several friends with less than 2 year old ATI cards that perform great, but have no real driver support with trashy, even BSOD drivers from ATI for win7.
At some point during this process, Microsoft takes a selection of OpenGL extensions - often including ones that vendors have proposed but not yet implemented - and says that the next version of Direct3D will require these. Vendors then implement whichever ones they didn't provide in their next generation hardware and stick a DirectX n+1 label on it.
I am TheRaven on Soylent News
Actually, it hasn't been this way since around 2003/2004. Essentially nVidia, ATI/AMD, Intel and a few other lesser known vendors sit down in league with Microsoft and decide what kind of features they will be able to implement in the next graphics hardware cycle. They then come up with the API and get feedback from the hardware vendors and work towards a final workable API. This is what we saw with Direct3D 9.0c, Direct3D 10, and Direct3D 11. OpenGL and the ARB has lagged way behind Microsoft and its partners, which is why the ARB was eventually disbanded and replaced by the Khronos Group. The Khronos Group kind of messed up OpenGL 3.0, they didn't implement half of the things they said they were going to do. As such, OpenGL 3.0 lagged quite a ways behind Direct3D 10. Fortunately, they've caught up, and OpenGL 3.2 is on par with Direct3D 10, but still a big step behind the new stuff in Direct3D 11. As such, Microsoft and it's partners are leading the pack here, and Khronos (and because most of Microsoft's Direct3D partners are also Khronos group members) is no playing the role of follower. You can be guaranteed that the next major revision to OpenGL to match Direct3D 11 almost exactly in features, as nVidia, ATI/AMD, et. al. don't want to deviate radically in their underlying hardware.
Yeah, there's a lot of idiots here who still think OpenGL is better than Direct3D. I doubt they'll ever change their opinions despite the fact that some of us are trying to force the facts down their throats. I'm by no means a Microsoft fanboy, I also use OS X and a couple of Linux distros at home and work, but you just can't argue with the fact that Direct3D 11 is better than anything else out there. Hands down. It's just a better API all around. I'm looking forward to moving towards implementing a Direct3D 11 renderer in our code base in the future. Currently our Direct3D 9 rendering code path is almost half the number of lines of code for our OpenGL ES 1.1 and 2.0 renderer implementations.
I wouldn't be surprised if you were all Microsoft-paid trolls and marketers that are placing your twisted spin on things and making people continue to believe in your garbage.
The hardware manufacturer talks to Microsoft. Microsoft talks to the hardware manufacturer.
This - surprisingly enough - turns out to be mutually beneficial.
I was totally with you right up to the mention of IE6. :P
Just because Windows XP can't run Direct3D 10/11 doesn't mean that Direct3D never supported geometry-shaders before OpenGL. Direct3D 10 had geometry shader support back in 2006, and it's what spurred the development of actual hardware that supported that feature set. It's true that nVidia had their GL_EXT_geometry_shader4 extension working back in 2007, but ATI/AMD NEVER supported it. It wasn't until OpenGL 3.2 was announced in August of this year that we actually got standardized support for geometry shaders, but the OpenGL 3.2 drivers from nVidia and ATI are still in beta.