my fwen using it no coil.. is cute and capable cards

the mem on gtx 970 make very minor to non effect on game... at end we all end user.. we need both company to compete with eachother and have same equal %% on market so they will not manipulate the price... e.g. gtx titan Z price of 3,000usd

acid.. if you girls looking like that pic of your profile i buy you VR...

so this test get me free VR porn content ? gosh is only reason i want to buy this.... !!

If you read AoTS preview from various tech sites you'll see their DirectX 12 and Asynchronous Shading performance decrease instead of increase as compared to DirectX 11. Nvidia been keeping quiet about it. The thread discussed about perhaps nvidia can't really do it because it lacks hardware scheduler (hence the reason why they could reduce a lot of power with the same 28nm lithography), can't really do parallel works because it was meant to do serial work and rely more on driver updates and CPU power to do it.

That's a lot of bull, It was problematic on the game that uses 4GB of VRAM even back then. It stutter like hell when accessing the last 0.5GB partition. When I buy 4GB 256-bit hardware I expects it to have that, not 3.5GB 224-bit with the last bit crippled. With more and more games eating VRAM good luck for all 970 user.

Furthermore it's either you are blind or what, nGreedia been gimping their Gameworks titles on AMD cards, remember Crysis 2 excessive tessellation on road divider and invisible sea under maps? What about Witcher 3 Hairworks? That doesn't include any other games like PCars and other PhysX games.

If that is my girl i probably already sold my gaming rig.

I get 9 when overclocked.

Yeah they lack hardware scheduler for DX12 async compute compare unlike GCN. Probably no problem with light load of async compute but will go haywire on moderate or heavy use.
Also their so call software implementation of Async-Compute kinda flaw because it's not really asynchronous since it depend on context switches.

IIRC Nvidia already fixed 3.5GB in most games by locking the slow 0.5GB partition

All these is moot point since all of them will upgrade to Pascal anyway.

Yes

I think they fixed it for the retail cards though you can't 100% fix a coil whine.

the fix is only for the furyX water pump.

Then we should probably ask one of the owner.

edthrax
Does your Nano have coil whine issue?

for the Nano don't have coil whine.. and I bump the fan speed quite high for the nano since I overclock the nano to 1050mhz..


since I am using Crossfire on my PC, I disable the ULPS so the nano is never off, so never notice any whine from cards in any part of my gaming

I would like to see the source of where did nvidia say thei fixed the GTX 970 fiasco.

That is one bold statement, not everyone is rich enough to upgrade within few femtosecond. Unless that is the mentality of the owner of the card to their beloved company

Sry, i meant "fixed" a.k.a workaround. My friends used to get bad frametime in Dying Light/Mordor but now not anymore, used around 3.3GB for the game exe and 3.7GB overall.

Well, that's the mentality i get from almost majority of them across several forums in the past years.

well not all of them seem to complain of what happened to kepler. Prolly they upgraded to big maxwell/maxwell anyway.

Crimson 16.2.1 is causing my R9 390 not run at full GPU clock speed
Anyone having the same issue?

on few game test yap spot about you mention... batman arkham knight 3xx mhz ja

not having any issues with my r9 290 with 16.2. is the card throttling?

I didn't have any issues with 16.2 either
Only after upgrading to 16.2.1 the issue surfaces

No, it's not throttling
If it's throttling, the speed would go to the max before it goes down
But in my case, it doesn't go to the maximum clock speed at all

ASUS R9 390 Strix
Playing Need For Speed 2015
With 16.2 it runs perfectly fine at 1050MHz
But on 16.2.1, it runs only in between 650MHz ~ 800MHz

Will revert to 16.2 afterwards
Wanna have dinner first

This post has been edited by sHawTY: Mar 5 2016, 08:12 PM

Hmm.. i'm on 16.2 + Vulkan5 driver. Everything work like it should.
Didn't test 16.2.1 because i read it only add Primal CFX profile.

Hi guys..is it good times now to sell r9 280x and waits for the upcoming amd gpu?

I'm back on 16.1 but still the same
It just won't go above 758MHz

I used DDU to uninstall 16.2.1 & then install 16.1
Damn 16.2.1, it screwed up everything

By the way, what's Vulkan5?

This post has been edited by sHawTY: Mar 5 2016, 10:39 PM