nvidiots on suicide watch https://www.youtube.com/watch?v=f

File: 005.jpg (216KB, 1024x683px) Image search: [Google]

216KB, 1024x683px

>>58318893

>GTX 1080 already gets 60FPS

AYYMDPOORFAGS CONFIRMED ON SUICIDE WATCH

File: Battlefront_02.png (43KB, 1302x1038px) Image search: [Google]

43KB, 1302x1038px

>>58318907

File: Battlefront_02.png (52KB, 1301x1469px) Image search: [Google]

52KB, 1301x1469px

>>58318907

http://videocardz.com/65343/amd-demos-star-wars-battlefront-on-ryzen-and-vega-at-ces2017

>The framerate was reportedly dropping to 57 FPS from time to time.
>Nvidia maintains 60+FPS all the time even on a DICE engine which is well known to be biased towards AYYMD

AYYMDPOORFAGS CONFIRMED ON SUICIDE WATCH

>>58319023
>videocardz.com
nuff said

>>58319023
Nolan?

>>58319023
>biased

>>58319023
>proof of completely opposite one post above

The CPU isnstill 3.4? They'd do better with a OCd quad core

>>58319175
it was vsync locked

>>58318928
DELET!!

>>58319195
> 57 FPS
> locked

>>58319195
Its a 4k monitor of course its vsync locked, they dont make higher refresh 4k screens yet

>being a fanboy

>>58318907
>>58318928
>>58318939
haha

immediately and thoroughly rekt

hehe

In the Vega demo they're showing gameplay walking a mostly empty map without any action going on at all

reviewers like
>>58318928
use a much more demanding sequences
>Using Fraps we recorded 60 seconds of gameplay from the training mission on Endor titled ‘Chase’. The benchmark begins once the Stormtrooper has mounted the speeder bike and takes pursuit.

So the FPS obviously isn't comparable

AMD as always cherry picking benchmarks

>>58319218
are you retarded? it's a ceiling. it's not fucking magic.

>>58319263
https://www.youtube.com/watch?v=WYWlnJ8dCLQ
This is the exact benchmark sequence that tpu uses. Doesn't take a genius to see that AMD's demo sequence is significantly easier to render

>>58318893
shit thread

t. AMDcuck

>>58319218
>not understanding basic tech
>posting on /g/
sounds about right

>>58319224
doesn't mean you can't run a game at higher fps

>>58319288
>>58319263
>this damage control
Nvidiots are literally holding back tears of BUTTfrustration.

>>58319288
it takes a special kind of retard to discredit the same map

>>58319313
But it's pointless

>>58319332
depends on monitor input lag, some 60hz TN panels have it very low(under 2ms) so shoving more frames eliminates delays

>using battlefront as a benchmark

>>58319327
Either you're trolling or you've never played the game before. Yes, its the same map. But there is a vast difference between strolling around in a circle vs flying through the map on the bike. More mem bandwidth will be needed to stream in all the textures and render geometry with the fast changing scene

It's just like when they demo-ed battlefront during the Ryzen demo where all they showed was a scene which was literally 90% empty space.

Can't really blame AMD since it's marketing's job to cast themselves in the best light possible. But I'm just saying that you should expect at least 10% less performance under real world gameplay/non cherry picked benches. Always keep in mind that AMD has a long history of over-promising and under-delivering.

>>58319424
holy shit who knew that! because we all know that canned benchmarks are actually the real deal eh

https://www.youtube.com/watch?v=G_n3wvsfq4Y

>AYYMD lies about Barcelona performance

https://scalibq.wordpress.com/2010/08/31/john-fruehe-amd%E2%80%99s-latest-and-greatest-liar/

>AYYMD lies about Turdozer performance

AROUND AYYMD, NEVER RELAX

>>58319469
nvidiot is so much into damage control that goes 10 years back to find a flaw

>>58319112
Bravo

>Unironically believing Vega is going to destroy 1080

My sides are in orbit.

>>58319149

""""""""""proof''''''''''''''''''''

>>58319149
>Every reviewer uses same methods and options of benchmarking

Subhuman Pajeet go drown in a holy river or something.

>>58319627
It will destroy a 1080. It probably won't destroy a 1080 ti.

>>58318893
>$600 for this
HOW CAN NVIDIA EVEN COMPETE

>>58319048
damage control

>>58318893
As long as AMD continues to have shit drivers and software, Nvidia will always BTFO AMD

>>58321583
Drivers ain't shit, but are feature rich and buggy.