Another thing: AMD could of been more pro-active to get TressFX in there and had years to try -- to offer TressFX after they did see the performance of HairWorks is silly considering nVidia likes x64 tessellation factor and their nVidia's hardware has an advantage. It's like AMD was surprised or are they going to use this as another example to attack nVidia's competitive advantages -- developer relations and GameWorks?
If AMD placed more focus on getting TressFX in there, show how efficient it may be over GameWorks/HairWorks, more open than GameWorks -- that would garner some very positive attention and awareness instead of whining and offer how unfair it is.
AMD had an opportunity to showcase their talents and vision if they were more proactive with TRessFX instead they are too late, complain and attack.
If you watched that Twitch video, and were keen on the development process of the Witcher 3, you would know that CDProjecktRed from around a couple years ago were showing off Hairworks on wolves in use cases, showing they've already committed. Gameworks compensation and integration is now probably a contractual obligation.
Then from the Twitch video, and how this game was developed, final code for Hairworks was delivered from Nvidia and integrated into the main game branch a couple months before shipping. It doesn't sound like even CDProjektRed had source code access to this.
Before this code, AMD was running just fine, probably Kepler too. After this code and with GOLD print press copy a month away. The performance rears it's ugly head. AMD offers TressFX at this point but CDProjecktRed knows it's too late and says no.
From the Downgrades, to the console catering development, and lying up till release, CDProjektRed were in over their heads and are as much to blame as either AMD or NVidia.