>bought a R9 390 because Sup Forums said it was future proof and will only get better with updates
>R9 390 and Fury X all but forgotten by AMD and all new updates tend to break more than they fix.
I feel ashamed that I fell for the AMD FINEWINE meme.
Never again, Nvidia only from now on.
Other urls found in this thread:
reddit.com
imgur.com
forums.geforce.com
forums.geforce.com
eu.battle.net
eu.battle.net
eu.battle.net
us.battle.net
us.battle.net
forums.geforce.com
twitter.com
The 390 performs really well at 1440p I myself have one what were you expecting?
>on par with a 980 Ti
Best of luck with your long-term Nvidia purchase. :^)
wut? 390 aged pretty decently. fury doesn't have enough RAM but that was obvious.
Are you retarded? The R9 390 beats out the 980 in most games now.
>Wattman crashes and is useless
>Overwatch crashes often
>Relive is too buggy
i agree
why is the rx 570 beating fury's?
>Lying on the internet
GTX 980 Ti DESTROYS R9 390X and GTX 980 is faster than AYYMD HOUSEFIRES GARBAGE
>fury x below 980
lol
>dx11
op i'd advise you to read reddit.com
>Fury X has worse geometry performance than Polaris RX 470. It's actually such an imbalanced design with way too much shader power but so little graphics (triangles & rasterization) power.
>Then it's got a gimped 4GB which just doesn't cut the mustard in these new games with their huge textures.
>The combination is bad.
>What we do see is that Hawaii based GPUs like the 390/X still perform very strong today, often around 470/480 level, and it's due to it's 8GB and more balanced design.
also
> break more than they fix.
you breaking shit isn't amd breaking shit.
>hurr i have to use one driver!
forums.geforce.com
spend a day and read through all nvidia offical forums. you'll soon release they're both shit.
>hurr i didn't have issues on nvidia in the past!
great anadoctal evidence. again, read through the forums, especially:
forums.geforce.com
and you'll see people complaining about long standing issues they have and new issues they didn't have before.
>Overwatch crashes often
nvidia users have the render device lost crashes as well.
eu.battle.net
eu.battle.net
eu.battle.net
us.battle.net
us.battle.net
forums.geforce.com
i can go on
the most likely problems are high tessellation and high VRAM consumption. Fiji should be less affected by tessellation than older cards, but also has less VRAM, so it could run into an entirely different bottleneck on the same game.
Polaris basically doubled raw geometry throughput compared to Fiji (hence basically quadrupled compared to most pre-Fiji cards), added some advanced primitive-discard logic to further ease pressure on it, and is commonly available with 8GB VRAM. I think Vega takes more steps in the same direction.
Meanwhile, many games are still being written according to NV's optimisation guidelines; a legacy of existing game engines, material libraries, middleware and "GPU gems" books that doesn't change overnight even if the market does. The 900 and 1000 series GeForces have somewhat excessive geometry/tessellation performance, so those guidelines basically say "use as much tessellation as you like to smooth your silhouettes out, it doesn't cost anything". They of course say nothing about the performance hit on older (but still relevant) GCN cards.
AMD's response has been in part to incrementally improve geometry/tessellation performance in successive GCN revisions (double, then double again), and also to work around excessive tessellation requests through driver profiles; this is what "AMD Optimised" means for several tweakables in Radeon Settings. However, driver profiles are explicitly not available in DX12 or Vulkan; AMD is very deliberately shifting responsibility for game performance to the game developer, which is fine by me. AFAIK this strategy is working, in that DX12 and Vulkan games tend to run well on AMD hardware.
Fine Wine technology.
Fury X below GTX 980.
Fury X owners BTFO.
Because the game uses more than 4GB VRAM. This kills the Fury.
but the RX 570 uses 4GB as well, and not only that it's GDDR5.
see
...
nvidia offical 388.13 GAME READY
>Issues and updates:
>-Some TVs EDID reports incorrect support for 12bpc or 10pbc colors format but can't actually support this format. Starting with Windows 10 Fall Creators Update, the OS now configures by default the display to its highest reported capability requesting the driver to send 12bpc or 10bpc format where it was using 8bpc in the previous release resulting in color corruptions. To avoid this issue, manually configure your display to 8bpc.
>-Using power monitoring in GPU monitoring tool causes FPS microstutter
>-Graphics corruption in Tom Clancy's The Division with R387 drivers
>-NVIDIA custom color settings are reset on reboot/cold boot after upgrading to Windows 10 Fall Creators Update on some systems
...
Shills on Sup Forums? No way /s
really if people just took the time to read nvidia offical forums you'll quickly see nearly the same shit amd users bitch about, nvidia users bitch about.
THE ONLY DIFFERENCE is amd users tend to be more cry babies and bitch everywhere where nvidia users will bitch on the offical forums but that's it.
then go off and tell people nvidia is the best thing since slice bread while leaving pic related on the forums bitching to nvidia about their shitty drivers.
its really odd actually.
...
...
...
As someone who uses both Nvidia and AMD GPUs frequently both have issues but AMDs is generally more unstable and results in crashes, either in game or the Crimson Relive GUI. GeForce Experience is shit but the control panel works well and Nvidia Inspector is nice as well. Nvidia's proprietaty drivers on Linux perform well but are more unstable due to Linux devs not being able to integrate it as well though.
if you bought it after rx 480 was released, you're a dumbass.
Why have you updated if update gets it broken?
no your dumber if you got the GTX970 at anytime after 2016.
...
...
>didn't fall for the poojet amdrone shilling and got myself a gtx980.
you should sell it to miner and get 1070