BallaTheFeared
Diamond Member
- Nov 15, 2010
- 8,115
- 0
- 71
I (and others) already answered that Lonbjerg - that's what the whole article in the OP is about - ,you just avoided recognising it.
recognising, that's not even a word!
I wish you were just as fast in documenting your other claims :whiste:
Pretty sure this forum is English (American) only.
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...
“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. “
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.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.
Really? Got proof of that?
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.
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.
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.
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.
I'd love to see you guys argue about coke vs pepsi complete with bar graphs and stuff

