Holy fuck they approached CPR to add TressFX
two months before the game went gold?!
And from this article:
http://arstechnica.co.uk/gaming/201...s-completely-sabotaged-witcher-3-performance/
So they not only didn't approach CPR to add TressFX during the years of the game's development, but they also aren't able to optimize from binaries like Nvidia can? Why do they keep blaming it on source code if Nvidia doesn't even use it for their optimizations?
And how come AMD/ATI's tessellation performance has been so shitty for so many years?
Not sure anyone is taking away the blame AMD gets for not having TressFX in. Chances are, hairworks and tressFX could have both been in there to do the same thing on each card (or even, TressFX chosen over hairworks since it works so well on NVidia cards) if AMD came to them even in the middle of last year. AMD has a PR problem, and a real problem in that it brings things up a bit later than NVidia, who gets their word and tech in from closer to day one.
It's why NVidia crushes AMD in getting full feature sets so often. AMD has to learn from that, as it is a perfectly acceptable thing to do.
I think the problem really is - without the source code, how do you know what to alter? NVidia may not alter the source code for their optimizations, but obviously the source code is running, and the stuff they do alter is to improve how that source code runs. So sure, the code itself may not get altered and they totally adjust something different, but that something different makes the source code run even better. Without knowing exactly how that source code functions, since AMD can't look at it, they cannot make proper adjustments. Essentially, they have to guess. "Adjust this - does it run better now? No? How about this? No? Okay, now this? etc."
They are literally shooting in the dark, hoping it suddenly runs better off guess work. Having the source code isn't just about having the ability to edit that code and make it run better on your hardware, it;s about understanding everything that code is doing, so you can adjust other areas of your drivers and tech to run that code more efficiently. So sure, NVidia's fire back seems sincere on the surface, but reality is that they may not need to touch that code, but they know what that code is doing. AMD does not. Guess work leads to inferior ability to adjust. TressFX, as poorly managed as it has been from a PR stand point, is right there, so NVIdia can see what it does, how it does it, and adjust.
Reality is, we're running in two different approaches to the market and yes, AMD and Nvidia are both making mistakes. The problem most have with Nividia is how they are trending. They are slowly making things proprietary. This means you HAVE to get Nvidia hardware for certain things, and that's just the start - eventually, entire games could require their hardware. It's like saying when you browse the internet, you can only watch videos on half the websites out there in HD on Project Spartan, and in SD in FF and everything else. Then, over time, suddenly those videos in 5 years ONLY play on Project Spartan. Then, the entire website only loads on it. Meanwhile, the other browser users are left out.
PC has always been about open source. NVidia is choosing to stop doing that because they have a strangle hold and they know AMD is not marketing right. They are trying to force them out of the market.
Obviously, AMD is successful enough to not be in a out of market situation, but people are going to prefer open source versus proprietary. AMD has a lot of work to do - and I applaud them for HBM - really hoping they stay on top of that tech now that they have a head start. They failed to do so with GDDR5, they need to do it with HBM. But that's just a start. AMD has their hands in a lot of cookie jars. They should really start pulling an NVidia and absolutely NAIL one of the avenues they are in, THEN trickle that down to the rest.