they should make gpu ram upgradable just like mobo, slot in ram as much as u like hahahaha

But what I find more interesting is sometimes a stable OC for unigine is still unstable for games, despite stress tested with unigine.

hi want to ask is 850W enough for crossfire 2xR9 290x? thanks

hmm so for best SLI / xfire setup it's best to get 1000W instead? CPU will take up alot of power? i5 3570k but i foresee to upgrade in future. thanks

1000W should be safe, otherwise i think 1200W is just overkilled and waste of money. correct me if i'm wrong. thanks

...........so.....the rebranded hawaii 390x.....water cooling + 8pins and 6pins PCIE power connector?
In addition to extra VRAM and higher GDDR5 clock speed (6Gbps instead of 290x original 5Gbps).......I think AMD also 'overclock' the gpu core to the maximum possible amount.....
Power consumption is going high for sure, sigh.....lack of delta color compression(not like hawaii gonna need this because its memory width is quite large)

-.- Feature wise, I still think maxwell GTX 980 or 970 (even with 3.5gb fiasco) is a better purchase. Example, hybrid HEVC 8bit DXVA decode, color compression, lower driver overhead (hope amd can improve its driver overhead), lower power consumption compared to upcoming extra overclocked 390x.

No idea what the hell amd is doing, two of my R7 260X sitting there doing nothing because no 'working' crossfire profile for GTA V, Project Cars and Witchers 3.

GTA V = weird blocky black checker board pattern on bottom right of screen.
Project cars = need to use modded driver dll from windows 10 preview for better performance.
Witchers 3 = followed all AMD knowledge base solution to reduce flicker, still flickering hard especially at watery area.

Mantle 'push' Microsoft? No such thing.
DX12 is already in development long before AMD announced its Mantle initiative.
Beside, the so called Mantle low level is kinda useless because Catalyst driver cpu overhead.

DX development doesn't take one year to finish, it takes several years for testing suitability, acceptability and feasibility.
I think Mantle kinda rushed to the market. If you take a look on the mantle documentation, it is kinda......messy and feel rushed.
Really wonder how DICE is able to use the mantle renderer.

Mantle is destined for failure in first place.
Reason, AMD has somehow low discrete gpu market share.
For console argument;
PS4 dev tool uses PlayStation Shader Language (PSSL).
Xbox One on the other hand uses DirectX HLSL with dx 11.2 API.

We don't expect Sony to support mantle or microsoft to use its competitors API, no?

Reason for people saying some documentation from mantle is similar to dx12 documentation?
Simple, AMD contributed some of the code to Microsoft to review and included in DX12. It is not copying.

Pretty much you have never tried Mantle before & just take whatever you read in the internet as 100% accurate. The whole point of Mantle is to reduce CPU overhead & it does work.

........I think you confused about something.

Allow me to elaborate;
First thing first, you need to differentiate between driver and API.
Easier if I grab some definition from wikipedia.

1) In computing, a device driver (commonly referred to as a driver) is a computer program that operates or controls a particular type of device that is attached to a computer. A driver provides a software interface to hardware devices, enabling operating systems and other computer programs to access hardware functions without needing to know precise details of the hardware being used.

I was talking about AMD catalyst driver overhead.

2) In computer programming, an application programming interface (API) is a set of routines, protocols, and tools for building software applications. An API expresses a software component in terms of its operations, inputs, outputs, and underlying types. An API defines functionalities that are independent of their respective implementations, which allows definitions and implementations to vary without compromising each other. A good API makes it easier to develop a program by providing all the building blocks. A programmer then puts the blocks together.

Mantle and DirectX are API.

Now, DirectX 9 - 11 are known to have some API overhead. The purpose of Mantle and upcoming DirectX 12 is to reduce/optimize the API overhead by making low level access available. And yes, as you said, Mantle successfully reduce the API cpu overhead.

Next, the second part is the DRIVER cpu overhead. This is the section AMD has its worst. Compared to nvidia driver, the issue of AMD catalyst driver overhead in dx9 - 11 game is quite serious.
You can find more about it at guru3d forum. http://forums.guru3d.com/showthread.php?t=398858

When AMD released its R9 285 (unofficially known GCN 1.2), even when using Mantle renderer, there was some performance issue. This was solved after AMD optimized R9 285 driver overhead later.

Edit: some grammer and wording mistake.

Can somebody help me to explain the stuff to kizwan?

EDIT: Formatting.

Hard to see anyone running AMD processor and pairing it up to enthusiast Radeons. Basically The issue of CPU overhead is moot when running on Intel processor.

Dunno why ppl until dai dai wanna argue driver overhead on CPU, just go buy 8 core Xeon, kaotim

That's why I believe the discussion about driver/api overhead is slightly moot without an understanding of the underlying principles of computer engineering.

Hey guys, everytime AMD catalyst says to update
it says current version
14.10.1006
and the update is version 14.201.1008.
But after update the version stayed the same like nothing changed why is that happening?

i realized the problem. AMD catalyst didnt provide updates for windows 8 64bit.
they only provide updates for windows 8.1. which is odd.

If i install the driver from windows 8.1 will it cause issues?