Hmmm.... EIDOS out, CAPCOM in.

Is this game even available/supported outside of, i assume, Korea?

Wasn't this a Nvidia benchmark earlier? So now they've partnered with AMD instead?

Wasn't this a Nvidia benchmark earlier? So now they've partnered with AMD instead?

Probably because of shize hairworks not being efficient enough, not surprised there..

Probably because of shize hairworks not being efficient enough, not surprised there..

Your saying this based on what?

Your saying this based on what?

witcher 3

witcher 3

Tomb Raider

:o Sweet, found a guide to register for MHO but not sure if I want to do it. I've got so much time invested on MH 3 on the Wii U.... It's also in Chinese, and I do not understand Chinese! There is at least an english patch being worked on. 😀 It is free, woohoo! Reviews of the beta so far have said that you can buy items, but it's not a pay to win title.

Tomb Raider

You're right. TressFX works great in TR 2013! Even in a nVidia card. I still prefer this technology over hairworks. :007:

Tomb Raider

I am sorry, the tressfx implementation in tomb raider is in every way better then hw implementation in The Witcher 3.

I am sorry, the tressfx implementation in tomb raider is in every way better then hw implementation in The Witcher 3.

Interesting How much % drop did you have in both titles with hair only enabled on main character ?

You're right. TressFX works great in TR 2013! Even in a nVidia card. I still prefer this technology over hairworks. :007:

Tomb Raider initially launched with a 7970 beating a GTX Titan at the highest settings, despite every other game the Titan often outperforming the 7970 by about 25-30%. Nvidia worked with Crystal Dynamics to fix the issue and the game was patched: http://www.pcgamesn.com/tombraider/tomb-raider-patch-improves-nvidia-performance-and-tressfx-hair Because unlike AMD, Nvidia didn't cry about everything like Richard Huddy does. They just went to work and fixed the issues. TressFX, despite being enabled on only one character, often hit performance by 25% across both vendors in Tomb Raider. Nvidia Hairworks hit is roughly the same on Nvidia, 25% in Witcher 3. On AMD it was a lot more, like 50% until AMD update their driver profile. Now it's closer to 30%. Except it's enabled across multiple actors in the game as opposed to TressFX, which is just one. In Farcry 4, the Hairworks performance hit it was the same across both vendors with Fur enabled, about 7%. It's possible that now, with the newer versions of TressFX its more optimized. But there is literally no basis that "Hairworks is not efficient enough". The only concrete example we have is Witcher 3, which hits between 25-30% across multiple characters vs TressFX in Tomb Raider that also hit 25% but on a single character.

Tomb Raider initially launched with a 7970 beating a GTX Titan at the highest settings, despite every other game the Titan often outperforming the 7970 by about 25-30%. Nvidia worked with Crystal Dynamics to fix the issue and the game was patched: Because unlike AMD, Nvidia didn't cry about everything like Richard Huddy does. They just went to work and fixed the issues. TressFX, despite being enabled on only one character, often hit performance by 25% across both vendors in Tomb Raider. Nvidia Hairworks hit is roughly the same on Nvidia, 25% in Witcher 3. On AMD it was a lot more, like 50% until AMD update their driver profile. Now it's closer to 30%. Except it's enabled across multiple actors in the game as opposed to TressFX, which is just one. In Farcry 4, the Hairworks performance hit it was the same across both vendors with Fur enabled, about 7%. It's possible that now, with the newer versions of TressFX its more optimized. But there is literally no basis that "Hairworks is not efficient enough". The only concrete example we have is Witcher 3, which hits between 25-30% across multiple characters vs TressFX in Tomb Raider that also hit 25% but on a single character.

Actually nvidia did make a big deal out of TressFX when TR was released. The complaint was "nvidia wasn't given access to source code until two weeks prior to release" which was proven false later via some emails between nvidia and TR (nvidia telling porkies). The irony here is nvidia complaining about two weeks when AMD have nothing (no Gameworks code ever) to work on. :banana: :bang:

Actually nvidia did make a big deal out of TressFX when TR was released. The complaint was "nvidia wasn't given access to source code until two weeks prior to release" which was proven false later via some emails between nvidia and TR (nvidia telling porkies). The irony here is nvidia complaining about two weeks when AMD have nothing (no Gameworks code ever) to work on. :banana: :bang:

Uhm you forgot one major detail, it was the FINAL gamecode. (the stated that , and aplogised to the Nvidia owners). thats basicly what always goes wrong when AMD or Nvidia have poor performance. Somehow people only want to hear what they want to hear though, so no matter what its always their fault.

Actually nvidia did make a big deal out of TressFX when TR was released. The complaint was "nvidia wasn't given access to source code until two weeks prior to release" which was proven false later via some emails between nvidia and TR (nvidia telling porkies). The irony here is nvidia complaining about two weeks when AMD have nothing (no Gameworks code ever) to work on. :banana: :bang:

... This is the response Nvidia gave as to why the game wasn't performing well:

"We are aware of performance and stability issues with GeForce GPUs running Tomb Raider with maximum settings. Unfortunately, NVIDIA didnt receive final game code until this past weekend which substantially decreased stability, image quality and performance over a build we were previously provided. We are working closely with Crystal Dynamics to address and resolve all game issues as quickly as possible,"

Professional, to the point, no nonsense. In contrast here is AMD's response to essentially the same issue:

"We've been working with CD Projeckt Red from the beginning," said Huddy. "We've been giving them detailed feedback all the way through. Around two months before release, or thereabouts, the GameWorks code arrived with HairWorks, and it completely sabotaged our performance as far as we're concerned. We were running well before that... it's wrecked our performance, almost as if it was put in to achieve that goal."

Also the source code for TressFX specifically wasn't put out until weeks after Tomb Raider shipped. The only thing Nvidia had was closed binaries pre-launch. And yet they still handled it fine without a giant **** show. Edit: This isn't even the first time AMD has done this either. With Project Cars it was the same thing. AMD moaned about Nvidia intentionally hampering performance and yet the Project Cars dev asked AMD and offered them Keys to the game and AMD never responded. S2 Games was the same way. Back when they shipped the first Savage they were a small indie company. They went to both Nvidia/AMD(ATi) at the time for help. ATi ignored them while Nvidia helped them get the game working on both Nvidia and ATi hardware. Ars had a decent OP-ED about their behavior lately: http://arstechnica.co.uk/gadgets/2015/09/amds-outspoken-plucky-underdog-routine-is-doing-more-harm-than-good/ Edit: I like AMD. I like what they are doing with their hardware, and I think they are going to come out strong in 2016. Their early effort with HBM is going to pay off with HBM2/Polaris and I think Zen is going to bring their CPU division back to form. I like their software efforts too. I think their open approach will eventually yield good results, not only with their graphics library stuff, but even with their API/Vulcan. I even put my money where my mouth is and invested in their stock, not much, ~$3000, but still it's something. That being said, I don't care for the incessant circle-jerk surrounding Gameworks and Nvidia. Most of it isn't based in any real logic, it's just nonsense. And it's usually by the same few people. I don't mind slight fanboyism. I'll admit myself I'm definitely slightly team green, only because my last 3-4 cards have been them. But if you're going to do it, at least do it like Fox or Lane does, they might have a slight biasism but it's based in reality and they bring up good points with detailed information. Not "because of shize hairworks not being efficient enough"

... This is the response Nvidia gave as to why the game wasn't performing well: "We are aware of performance and stability issues with GeForce GPUs running Tomb Raider with maximum settings. Unfortunately, NVIDIA didnt receive final game code until this past weekend which substantially decreased stability, image quality and performance over a build we were previously provided. We are working closely with Crystal Dynamics to address and resolve all game issues as quickly as possible," Professional, to the point, no nonsense. In contrast here is AMD's response to essentially the same issue: "We've been working with CD Projeckt Red from the beginning," said Huddy. "We've been giving them detailed feedback all the way through. Around two months before release, or thereabouts, the GameWorks code arrived with HairWorks, and it completely sabotaged our performance as far as we're concerned. We were running well before that... it's wrecked our performance, almost as if it was put in to achieve that goal." Also the source code for TressFX specifically wasn't put out until weeks after Tomb Raider shipped. The only thing Nvidia had was closed binaries pre-launch. And yet they still handled it fine without a giant **** show.

Normal, in 2013, TressFX was keep secret untill the 27.02.2013 ... 1 week before the launch of TR 2013 for showcase it, in real condition.... It was a secret for everyone, public or not and speciallly for their competitor... You wanted they send a mail to Nvidia 6months before, for tell them they was developp TressFX ? lol. As for the sdk, it have been put online in may 2013.. but the problem was allready fixed as CD and Nvidia have worked for optimize the game and Nvidia release a driver way before may 2013.

Normal, in 2013, TressFX was keep secret untill the 27.02.2013 ... 1 week before the launch of TR 2013 for showcase it, in real condition.... It was a secret for everyone, public or not and speciallly for their competitor... You wanted they send a mail to Nvidia 6months before, for tell them they was developp TressFX ? lol.

No, I don't want them to send an email. All I'm saying is that Nvidia handled the issue from PR level significantly better than AMD did with Gameworks. They didn't directly attack AMD. They just said they are working on it and going to fix it. And they did. AMD on the other hand cried about Gameworks, in both Witcher 3 and Project Cars. And in both cases they were able to resolve the issue but not without the nonsense first.

No, I don't want them to send an email. All I'm saying is that Nvidia handled the issue from PR level significantly better than AMD did with Gameworks. They didn't directly attack AMD. They just said they are working on it and going to fix it. And they did. AMD on the other hand cried about Gameworks, in both Witcher 3 and Project Cars. And in both cases they were able to resolve the issue but not without the nonsense first.

Nearly every game released under TWITMP program or using gamework have been a catastroph on AMD gpu's since yeaaars... The first time, i think nothing, the second time its an hazard, after more than 10games, its a constant.. I dont want to enter an endless discussion about it, as it is completely offtopic, and thats just my opinion.

Because unlike AMD, Nvidia didn't cry about everything like Richard Huddy does. They just went to work and fixed the issues. TressFX, despite being enabled on only one character, often hit performance by 25% across both vendors in Tomb Raider. Nvidia Hairworks hit is roughly the same on Nvidia, 25% in Witcher 3. On AMD it was a lot more, like 50% until AMD update their driver profile. Now it's closer to 30%. Except it's enabled across multiple actors in the game as opposed to TressFX, which is just one. In Farcry 4, the Hairworks performance hit it was the same across both vendors with Fur enabled, about 7%.

I can't believe in you. Even nvidia claims that's a driver's fault and it was updated too fast. The bug's fix cames with a driver's update, not a game patch. https://www.rockpapershotgun.com/2013/03/07/nvidia-apologises-for-crummy-tomb-raider-performance/ I can't link driver's problem with TressFX's performace like you is trying to do.

Your saying this based on what?

Lots of hairworks titles in the past.. And it was the same with MOH benchmark as soon as that furry cat appeared. TressFx2.0 is much better or now @ v3.0.. Ps. Sometimes you're defending nv a bit too much, like a true fanboy 😛 no pun inteded.