Recent content by Kwee

Just click on the source, mate, i'm not going to take your hand and show you what it's going on. If you don't want know, then be my guest. http://img4.hostingpics.net/pics/489141lestroissinges3.jpg

The first tool i used for determinate if the Async Compute work or not wasn't Ashes Of Singularity. It was a tool developped just for testing Async Compute. After that only i test Ashes Of Singularity which show a regression on performance. Many tools was tested after that like D3D12NBodyGravity.

http://imgur.com/Xr0Jhjo AMD presentation June 2016, Async Compute retired in GCN 1.0 in April.

Margin of error is about between 0,5% and 2% max. Gain from Async Compute is between 7% and 10% on R9 270X, 5% and 7% on R9 280X(Maybe more with the same drivers as R9 270X). Async Compute implementation in Ashes is very light. Sure not that...

http://ithardware.pl/testyirecenzje/czy_amd_rzeczywiscie_wykastrowalo_gcn_1_0_z_async_compute_weryfikujemy_doniesienia-1425-1.html https://community.amd.com/message/2765237 https://community.amd.com/message/2765216

I spent all night installing every drivers between 16.3.1 and 16.9.2. The break point is the driver 16.4.2(released in April). After this driver no more Async Compute on GCN 1.0. So Nixxes was aware that Async Compute was not active on GCN 1.0. They released Async Compute patch for Rise Of The...

It's a driver issue, not a game issue.

I see a lot of misunderstand since i post my finding. In a first place, i started to search why GCN 1.0 was not supported in Rise Of The Tomb Raider last patch. When Maxwell was accused to not support Async Compute, someone create a program for testing Async Compute. It worked on GCN 1.0, 1.1...