.......
bit-tech: How is AMD's support for Dirt 2 - where you give a lot of marketing, engineering support and bundling, different from Nvidia's support to Rocksteady with Batman? Nvidia is injecting its own IP into the game - in terms of PhysX, and the game's anti-aliasing method - and then protecting its own business interests, as both are Nvidia-only.
RH: The Rocksteady stuff is interesting from a number of perspectives. For starters, it's a DirectX 9 title so it doesn't push hardware terribly hard, and it certainly doesn't push any of the new capabilities. I won't deny it's a perfectly good game but in terms of using new hardware and using it hard - it doesn't - so it's not insanely exciting to us. However, I have one of my best engineers - one of my most pro-active engineers - and he was getting builds on a regular basis. We did talk to Eidos about the possibility of being a co-marketed title with us, however Nvidia decided it would - to use your phrase - inject its IP into it. It did this in two parts, one of which I've got I've got a reasonable amount of respect for and the other I frankly hold in complete contempt.
[Nvidia] put PhsyX in there, and that's the one I've got a reasonable amount of respect for. Even though I don't think PhysX - a proprietary standard - is the right way to go, despite Nvidia touting it as an "open standard" and how it would be "more than happy to license it to AMD", but [Nvidia] won't. It's just not true! You know the way it is, it's simply something [Nvidia] would not do and they can publically say that as often as it likes and know that it won't, because we've actually had quiet conversations with them and they've made it abundantly clear that we can go whistle.
However, PhysX is a piece of technology that changes the gameplay experience and maybe it improves it. What I understand is that they actually invested quite a lot, Nvidia put in a hefty engineering time and they tried to make a difference to the game. So, in that aspect, I have respect for it; it's a reasonable way to handle the situation given the investment in PhysX. Nvidia wanted a co-marketing deal and put forward PhysX, and Rocksteady and Eidos said, OK, as long as you do it - which they did.
The part that I totally hold in contempt is the appalling way they added MSAA support that uses standard DirectX calls - absolutely nothing which is proprietary in any useful sense. They just did ordinary stuff, a completely standard recommendation that they make and that we make to developers for how to do MSAA, and they put it in and locked it to their hardware knowing it would run just fine on our hardware. And indeed, if you simply spoof the vendor ID in the driver - which we and other people have documented - it runs absolutely fine on AMD hardware. There's nothing proprietary about it in that sense, nothing new. I think that's exceptionally poor.
What I could have done as the Developer Relations guy at AMD is say
"actually, what they're doing is a reasonable business investment and I'll do exactly the same thing for all the DirectX 11 code we are adding. We'll just go in an add it, and since I can't QA it on Fermi because all they've got still is a faked up board that they showed off recently, what I'll do is I'll lock it to our hardware." 
Morally I think that would be reprehensible, but from a business point of view I could argue in favour of it, but we think it's really the wrong thing to do and we've not locked a single line of DirectX 11 code.
That's the difference in the way [AMD] works - we work through enablement and open standards. [Nvidia] works through closed standards and disablement, which, to me is inexcusable; it's as bad as that..........
Bookmarks