UPDATE: I know that some of our readers, and some contacts and NVIDIA, took note of Huddy's comments about TressFX from our interview. Essentially, NVIDIA denied that TressFX was actually made available before the release of Tomb Raider. When I asked AMD for clarification, Richard Huddy provided me with the following statement.

"I would like to take the opportunity to correct a false impression that I inadvertently created during the interview.

Contrary to what I said, it turns out that TressFX was first published in AMD's SDK _after_ the release of Tomb Raider.

Nonetheless the full source code to TressFX was available to the developer throughout, and we also know that the game was available to NVIDIA several weeks ahead of the actual release for NVIDIA to address the bugs in their driver and to optimize for TressFX.

Again, I apologize for the mistake."

That definitely paints a little bit of a different picture on around the release of TressFX with the rebooted Tomb Raider title. NVIDIA's complaint that "AMD was doing the same thing" holds a bit more weight. Since Richard Huddy was not with AMD at the time of this arrangement I can see how he would mix up the specifics, even after getting briefed by other staff members.

END UPDATE

AMD recently brought back Richard Huddy in the role of Gaming Scientist, acting as the information conduit between hardware development, the software and driver teams and the game developers that make our industry exciting.

Richard stopped by the offices of PC Perspective to talk about several subjects including his history in the industry (including NVIDIA and Intel), Mantle and other low-level APIs, the NVIDIA GameWorks debate, G-Sync versus FreeSync and a whole lot more.

This is an interview that you won't want to miss!

(PS - sorry, but if you missed the live stream, you missed out on your chance to win some free hardware! Don't miss out in the future: sign up for our live stream mailing list at http://www.pcper.com/subscribe)