• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

CPR W3 on Hairworks(Nvidia Game Works)-'the code of this feature cannot be optimized for AMD'

Unfortunately the way Game Works is set up, it looks like it is intentionally designed to punish AMD.

For example hair works. 64x tessellation on hair when it looks just the same at 16x is not only a waste of performance on Nvidia cards, but done to punish AMD to the maximum.

Bad.

I’m all for providing devs with libraries to make our games better and more immersive. But I get the impression Nvidia are using this as a way to not only punish AMD, but to also make artificial conditions to push their latest line of cards.

It's very naughty.

---

On the flip side, should we be happy that this is happening as it is pushing the envelop of what Devs are trying to achieve in games?

Unless of course it's not set up to punish anyone, but just using the latest advancement in the current series of cards.

For example the 900 series is 3x faster at tesselation than the 700 series, hence the use of 64x tesselation in the witcher 3.

But these settings should be configurable in game. Is this not a Dev issue rather than Nvidia?

---

Also these practices are not anything new and this wont be the last time. This is how things operate in this industry.

This is why I will not be in the slightest suprised when it comes to light that the current 900 series and anything below will not have full hardware level support for DX12.

It's just not in Nvidia's interest. Think how many millions of GPU's they can sell when people relaise they need to upgraded for full DX12 support!

Maxwell does not have 3x the Tessellation of Kepler :p they are about the same if you normalise the shaders and clocks.

GCN 1.2 has over 2x the Tessellation of GCN 1.0 and 1.1, so the 285 should do well in W3 compared with the 280/X

 
Last edited:
Unfortunately the way Game Works is set up, it looks like it is intentionally designed to punish AMD.

For example hair works. 64x tessellation on hair when it looks just the same at 16x is not only a waste of performance on Nvidia cards, but done to punish AMD to the maximum.

How is it done to punish AMD cards, when the have a tessellation slider in their drivers that they can use to turn it down to boost performance, and get no visual impact ?

Nvidia are only punishing their own cards, as they don't have a tessellation option, leaving theirs stuck at max tessellation, so hindering their own peformance, as their only option to boost their performance, is to turn the Hairworks completely off, where as AMD, can run with Hairworks on, and boost their performance using it, by using the tessellation slider option in their drivers.
 
Last edited:
Well if they're punishing their own cards I certainly haven't felt it, then again I'm one of the idiots who bought their flagship :D
 
There's some pretty intelligent non-frothing at the mouth discussion going on about it on the Anandtech forums.

bowler484 said:
You hit the nail right on the head.

Nvidia should immediately stop allowing AMD hardware to run anything Gameworks related. If AMD users are getting extra features, it should be AMD creating them.

GTA is the perfect example of what could become of this. Both teams supported the developer with features and the game ran very well right out of the gate. As a PC gamer, we need more like this happening.

GTA proved with 100% certainty that the presence of Gameworks alone has virtually no effect on how AMD cards run the game when Gameworks is turned off despite what they've been telling us. If AMD is not getting game code because of Gameworks, how did they optimize GTA?

The Forbes author has been an AMD supporter for a long time and has called out Nvidia on numerous occasions for nonsense they pull. It's only right and fair that he does the same with AMD when it's deserved and in this case it is.

Watch Dogs was the poster child for Gameworks supposedly crippling AMD. HBAO+ and TXAA were the Gameworks tech in that one. GTA V has TXAA and PCSS. Why was one "crippled" and one not? Because AMD put the effort in with GTA that's why.

Does it not concern anyone that AMD talks about how Gameworks cripples them and calls out developers on it. Then magically they make up and the game gets fixed because AMD finally puts the effort in? Forbes noticed this and so have other sites.

The bottom line is AMD is purposely not optimizing anything Gameworks until the game is released. It's being done so people believe Gameworks is the one and only cause when it's not. It paints AMD and it's users as victims to make Nvidia look bad.

I implore you all to wake up and stop being AMD's pawn here. They are using you every bit as much as Nvidia is. We have one company that's become overly greedy because their success and another company that's not doing well so now they tell lies to try to win back market share.

bowler484 said:
And I'm stunned that you can't.

And it's not masochism, it's manipulation and you're falling for it.

In the past, we'd hear a bit about each company having issues with games that fell under the other one's banner. After a couple weeks, stories long gone and patches fixed stuff and it's all good or close to it.

Suddenly, one company that's losing market share and has no new product in the pipeline to win it back gets a couple tech news outlets to run the story that Gameworks is crippling them and they can no longer optimize starting with Watch Dogs. TXAA simply doesn't run on AMD cards so that's not it. HBAO+ is shown by multiple sites to have the same effect running on either camp's cards. So what exactly couldn't they optimize? Newer AMD drivers show gains being made in performance because once they got the point across, they put the time in and fixed it.

Now each time a Gameworks game gets released, we get the same old song and dance. Project Cars, AMD and developer have twitter war blaming each other. Then comments get retracted and they get to work optimizing for AMD. Why was this not done earlier so AMD users didn't have a bad experience? So AMD could blame Gameworks for that bad experience.

It's really funny how nobody will address GTA V use of Gameworks anywhere and how it ran fine for AMD right out of the box. Maybe, just maybe, because AMD actually worked with the developer before release.

The proof is there for those who want to see it.

ocre said:
Many people on this thread are gonna blow off what you are saying but there is a clear pattern. I really dont think many people have the guts to say what you have for fear of the push back.

I have seen enough lately that makes me wonder. It seems that part of AMDs plan could be to twist Nvidia advantages into something bad, evil, or awful. I dont want to get too far off topic and i will only touch on this. As an example, nvidia comes out with Gsync and AMDs response was fist to attack and downplay then manipulate. Just look at the name of their alternative technology and clearly you can see the psychological intent.

Back to your theory on gameworks, I was confused when people blamed gameworks for poor performance in watchdogs, AC untiy, etc. Yet the smear campaign seemed to take hold very well, at least on tech forums.
I just couldnt see how though. For most the big games, HBAO+ was the only gameworks feature that even ran on AMD HW.....yet the performance hit was not out of proportion on AMD cards. The hit was similar on both Nvidia and AMD cards.
Clearly, there was/is something else going on. It was not gameworks at all.

This is proven when, all of a sudden, several weeks after the game has launched AMD GPUs magically get a huge boost in performance. I think it was 40% increase for Unity. That is massive. But how? If gameworks was the issue, if HBAO+ was the issue, how did AMD get 40% increase in performance? I thought there was nothing they could do?

Obviously there was something that could be done.
When I brought up the fact that HBAO+ doesnt penalize performance a crazy amount on AMD HW, or that it doesnt even have to be used at all, that you can turn off completely....that the gameworks feature HBAO+ just cannot be responsible for the performance issues in those games, then you get met with a list of other mixed up reasoning. Like, AMD cant work with developers on gameworks titles, that Nvidia prevents them in their contracts.

These are interesting claims. A mixture of facts with fallacy, like all good conspiracy theories are. Nvidia does prevent developers from sharing gameworks code. This is stretched to become........the entire game. Nvidia doesnt allow developers to share HBAO+ or TXAA code and this is twisted to become something far far more sinister. If AMDs goal is to downplay or turn Nvidia advantages, this sure would be a great way to try to do it.

Ultimately, there is a huge problem with those claims. See the fact that AMD somehow manages to get up to 40% more performance down the road, it is completely at odds. Obviously AMD could optimize and gain performance on a gameworks game. They have done this, time and time again. Why do they wait till after the fact? It could be by design, as you suggest.

I think AMD does have a strategy and does try to down play/reduce the image of Nvidia advantages. I believe there is this very real matter of resources that all people can accept but the people might be blind to the smear campaign that i think is in full force. I believe both are guilty of smearing from time to time.
As for AMD purposely not optimizing just because it is a gameworks title, it might be a little more complicated. Perhaps resources are at play here as well. AMD may be taking a back seat and responding once they see how popular these games become. In the meantime, to save face it is gameworks and nvidia who gets the blame. Can we expect them to say, "well we only have so much money"

It is more than obvious that gameworks is a scapegoat. HBAO+ and TXAA had no hand in harming AMD performance in those games. Even without running gameworks features, the performance wasnt too strong. When Nvidia spends time on games they think are gonna be big, they maximize performance and optimize as much as they can. They do a lot of work before the game even comes out. So for a game like unity, this kind of work AMD done after the game launched. All the while, gameworks was blamed.

So basically i can see what you are getting at. There is little doubt in my mind, the pattern that plays out. I just dont know if i would say that AMD is waiting after a game launches to optimize in a plan to attack gameworks/nvidia. I propose a different reason.
 
and AMD and their loyal users arguing against it aren't biased?

That's why most of the time these discussions are pointless, completely unbiased viewpoints are very scarce.
 
As usual completely ignoring the proven cheating and pointless overtesselation/AA.

They've been caught once again and you're all twisting it around, dodging the issue, downplaying and misdirecting until the next anti-AMD news cycle comes along.
 
The old way of blocking AMD from using nVidia's proprietary techs had AMD users up in arms, NVidia make everything work on all platforms and AMD users are still not happy. Damned if they do, damned if they don't!
 
and AMD and their loyal users arguing against it aren't biased?

That's why most of the time these discussions are pointless, completely unbiased viewpoints are very scarce.

i duno, it can be pretty fun watching grown men acting like little boys
makes me feel all grown up! :)
 
As usual completely ignoring the proven cheating and pointless overtesselation/AA.

They've been caught once again and you're all twisting it around, dodging the issue, downplaying and misdirecting until the next anti-AMD news cycle comes along.

Nah, i think Bowler484 and Ocre are paid up members of the Tinfoil Hat Brigade, you can almost feel the conspiracy anger in those post, hilarious, i might befriend them. :D
 
Last edited:
As usual completely ignoring the proven cheating and pointless overtesselation/AA.

They've been caught once again and you're all twisting it around, dodging the issue, downplaying and misdirecting until the next anti-AMD news cycle comes along.

In the AMD CCC, the default option is AMD Optimized.
By CCC we can change tessellation level.

With an AMD driver, (That has the tessellation in Witcher 3 changed), then the over tessellation problem doesn't exist. A new driver issued by AMD by default wouldn't then have the tessellation problem.
 
AMD's fault it runs **** on Kepler too now.:D

@Martini, what % of AMD gamers know that hack works?:p

Irrelevant. "AMD Optimized" is the default option in CCC. A new driver issued by AMD would have a lower tessellation level (Hence the whole "optimisation") which would then be the base tessellation level for the game as rendered by an AMD card.
That doesn't absolve Nvidia of any wrongdoing (But no reasonable debate can ever take place, because of dat elephant in the room).
 
Back
Top Bottom