[Extremetech] Nvidia’s GameWorks program usurps power from developers, end-users, AMD

Page 8 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Lonbjerg

Diamond Member
Dec 6, 2009
4,419
0
0
I (and others) already answered that Lonbjerg - that's what the whole article in the OP is about - ,you just avoided recognising it.

No, you keep saying that, but gives no documentation.

Like I quoted before:
"What can be asserted without evidence can be dismissed without evidence."
 

SiliconWars

Platinum Member
Dec 29, 2012
2,346
0
0
I wish you were just as fast in documenting your other claims :whiste:

First of all, nobody mentioned APEX or PhysX so why you are is just a smokescreen.

Second, this is about Gameworks, which I and others have already shown the article in question with various references as to why it disallows AMD from optimising. You just fail to recognise it.

Pretty sure this forum is English (American) only.

Really? Got proof of that?
 
Last edited:

96Firebird

Diamond Member
Nov 8, 2010
5,743
340
126
Complete FUD, AMD has no fault in BF4's engine issues.

Just like Nvidia has no fault in WB's decision to not work with AMD on Batman, or Crytek's tessellated ocean in Crysis 2, or any other faults people blame on Nvidia with no basis.

Nobody likes a hypocrite...
 

SiliconWars

Platinum Member
Dec 29, 2012
2,346
0
0
Just like Nvidia has no fault in WB's decision to not work with AMD on Batman, or Crytek's tessellated ocean in Crysis 2, or any other faults people blame on Nvidia with no basis.

Nobody likes a hypocrite...

I wonder if you even know the difference between deliberate hobbling and just having a broken engine?

Read - DICE employee explains why Battlefield 4 is “buggy”

“When a code that’s not “thread-safe” executes on multiple sources, it’s a coincidence if it works or if it crashes. All the codes become “timing dependant” and different hardware combined with different background processes and OS’s, have different timing. “
Unfortunately, if you have a certain CPU and you run a certain OS and at the same time you run a certain background process, you could get “bad timing” more often than other people, Timing that will cause the game to crash or other bugs.
Now try to explain why this is even remotely anything like Nvidia's over-tessellated jersey barriers and hidden water in Crysis 2. Or missing AA from Batman (only on AMD), or massively over-tesselated mountains in HAWX 2, or etc etc etc.
 
Last edited:

sontin

Diamond Member
Sep 12, 2011
3,273
149
106
The fun part is:
At least these games actually run on AMD hardware.

Tomb Raider was straight broken and AMD compared their hardware with an broken nVidia DX path for performance numbers.

But whatever. I know AMD would never pay a developer like Eidos to sabotage a game for a huge group of gamers.
 

SirPauly

Diamond Member
Apr 28, 2009
5,187
1
0
I repeat. The performance is not important. The problem is blocking AMD optimizations in DirectX.

No surprise that the same people that says mantle been close to AMD is bad for the gamers are OK with this.

I was one of the posters that agreed with Richard Huddy and Repi in 2011. I have nothing against proprietary based on innovation and improved gaming experience potential!
 

96Firebird

Diamond Member
Nov 8, 2010
5,743
340
126
Now try to explain why this is even remotely anything like Nvidia's over-tessellated jersey barriers and hidden water in Crysis 2. Or missing AA from Batman (only on AMD), or massively over-tesselated mountains in HAWX 2, or etc etc etc.

My post went over your head, not surprising.

What I am saying is, you have no proof that Nvidia was involved with the poor AMD showing in these games. You have absolutely no proof. Just like there is no proof AMD is the reason DICE's game is broken.

Is that clear enough for you? I am not sure if you are being deliberately thick-headed or what...
 

SiliconWars

Platinum Member
Dec 29, 2012
2,346
0
0
Lol yeah no proof that in games that Nvidia paid millions for just had huge amounts of over-tesselation even on hidden and completely flat objects, no AA implementation on AMD cards and AMD disallowed from doing optimisations in.

You could always try applying Occam's Razor. If after that you come to the conclusion that all that was just "sheer coincidence" then it's pretty clear who's being thick-headed.
 

Lonbjerg

Diamond Member
Dec 6, 2009
4,419
0
0
Lol yeah no proof that in games that Nvidia paid millions for just had huge amounts of over-tesselation even on hidden and completely flat objects, no AA implementation on AMD cards and AMD disallowed from doing optimisations in.

You could always try applying Occam's Razor. If after that you come to the conclusion that all that was just "sheer coincidence" then it's pretty clear who's being thick-headed.

I am still lacking documentation from you...FYI.
 

BallaTheFeared

Diamond Member
Nov 15, 2010
8,115
0
71
Lol yeah no proof that in games that Nvidia paid millions for just had huge amounts of over-tesselation even on hidden and completely flat objects, no AA implementation on AMD cards and AMD disallowed from doing optimisations in.

You could always try applying Occam's Razor. If after that you come to the conclusion that all that was just "sheer coincidence" then it's pretty clear who's being thick-headed.

Indeed, Occam's Razor... AMD killed Battlefield.

BF3 no AMD, no problem.

BF4 AMD, series dies.

Occam's Razorizored.
 

SiliconWars

Platinum Member
Dec 29, 2012
2,346
0
0
Let me help you with Occam's Razor balla.

Company A

Works very closely with development on BF3 and BF4
Both BF3 and BF4 show performance respective of each cards true placing.
BF4 is broken
DICE say the reason BF4 is broken is down to the new multi-threading engine with certain CPU's and OS's.

Occam's Razor says - "BF4 is broken because DICE *$^% it up."

Company B

Works very closely with development on various Ubisoft titles
Many of these titles have performance results that are not respective of the cards true placings, ie a 770 being almost as fast as a 290X.

Or say stuff like this -

hawx2.png


Where the competing cards are twice as fast on Nvidia.

Then you have features being disallowed ie AA (funnily enough with the same company again? How can that be??), and AMD's attempts to optimise the game being refused.

Occam's Razor says "Company B and some of their partners are dirty rotten scoundrels".

You see balla, the simplest explanation based on the evidence.
 
Last edited: