Radeon Software Crimson Edition 16.10.2 Download & Discussion

It may be that there is a whole lot of code that is written in just AVX (and AVX2 where it can be beneficial) and they haven't duplicated certain aspects of the code for older systems. It should also be a consideration that games that are optimised probably won't have SSE4.x or SSSE3/SSE3/SSE2 code if there are faster AVX instructions available for the same purpose. They would either have the game optimised and pre-AVX not being able to use it, or be slack and not optimise the game, which means support for you but lesser potential performance.

Main thing to remember is it's not as simple as flags, if there is no non-AVX alternative code it simply won't work. That is the whole purpose of the flags in the first place.

 

Yup, that fixed the problem.

Euxaristw, patriwth!

TY!:banana:

 

Good driver so far.
Runs GhostRecon: WildLands pretty good on Ultra/High + extended lights

 

Zen will be your friend

 

Surprised no one mentioned the new cards contained in these driver set up..

"%AMD7300.1%" = ati2mtag_R7000, PCI\VEN_1002&DEV_7300&SUBSYS_0B361028&REV_C8
"%AMD7300.2%" = ati2mtag_R7000, PCI\VEN_1002&DEV_7300&REV_C8
"%AMD7300.3%" = ati2mtag_R7000, PCI\VEN_1002&DEV_7300&REV_C9
"%AMD7300.4%" = ati2mtag_R7000, PCI\VEN_1002&DEV_7300&REV_CA
"%AMD7300.5%" = ati2mtag_R7000, PCI\VEN_1002&DEV_7300&REV_CB

AMD7300.1 = "AMD Radeon (TM) R9 Fury X"
AMD7300.2 = "AMD Radeon (TM) R9 Fury Series"
AMD7300.3 = "Radeon (TM) Pro Duo"
AMD7300.4 = "AMD Radeon (TM) R9 Fury Series"
AMD7300.5 = "AMD Radeon (TM) R9 Fury Series"

 

What wait? How are you playing that?

Alpha? Sign me up!

 

Which driver versions don't have the UVD bug?

Does uget work for file hoster sites? (mega, rapidshare, etc.)

 

It should depend case to case. On some sites that need you to have cookies to access direct links, you can get away by using the correct user agent on uget/wget, while others such as mega might require external tools to access links. My sugestion for uget was just for when you need a portable downloader for a link with resume support or multiple connections (not so important nowadays).

Since I noticed the idle bug in W10 1607 while using 16.8.2, IIRC the further I went back was to test 16.7.3 without success. Didn't bother to try older drivers, as it seems to have something to do with AU.

Edit: Confirmed driver versions.

 

With these drivers CFX on my 390s are not running well in BF1 on DX11...inconsistent FPS ranging from 30-120 at 1440p on Ultra settings. With CFX disabled the FPS stay smooth somewehere between 65-90. Also I have the flickering textures appering randomly in BF1, so I am staying of the CFX for now.
Mafia 3 runs the same like 16.10.1 drivers.

Cheers!:cheers:

 

PM Send
its an really GG, enjoyable as f.unk :biggun:

 

Same experience with 7970 CF. 1080p/120HZ, high details, sweetFX 2.0. GPU usage is bad like 66-98%. FPS is around 60-140fps

 

Why Vulkan 1.0.26? Now is 1.0.30

 

They usually don't upgrade immediately, Nvidia only just upgraded to 1.0.24.0 with their newest driver and AMD jumped to 1.0.26.0 with 16.9.x some time after the actual SDK itself had been released.

EDIT: Vulkan SDK website and info and their Github source code repository.
https://vulkan.lunarg.com/doc/sdk/1.0.30.0/windows/release_notes-1.0.html
https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers

EDIT: Extracted 1.0.30.0 from the SDK.
VulkanRT.rar
http://www73.zippyshare.com/v/jAJutqFv/file.html
(They're backwards compatible as such but I don't think the AMD driver supports higher than 1.0.26.0 but here's the newest one until 1.0.31.0 or whatever the next release version will be.)

 

This drivers causes Battlefield 1 to go blue when playing multiplayer, if you look down certain alley ways, or zoom through scope, some maps the entire screen turns blue, which then causes all windows to turn blue, its pretty much starts to turn areas of the video games into the void of unknown space....

I have not rolled back but I should to 16.10.1, I had zero issues with that driver or any driver before.

Blue just started with this driver.... I recommend not using this driver....

 

Like this? https://ru.reddit.com/r/Amd/comments/58jo02/bf1_greenblue_etc_screen_flickering_on_16101_16102/

 

Yup the screen will do that, and in scope. but kind of worse, when I zoom out of sniper rifle the windows in buildings will be bright blue and stay that way for duration of map... :3eyes:

Since I rolled back to 16.10.1 no more blue screens.:infinity:

They still need to fix the DXGI errors though. get it with all drivers and video cards.:bang:

 

- same here, the cards seem to love being revved up to max settings
- very smooth..

 

Mantle is F.unked up in these lol
Why Mantle is not working, also 16.10.1 & 16.9.2 from repository don't work.
Grrrrrrrrrrr :bang:

 

My experience with a Xeon x5470 is really impressive. Thief with mantle can be maxed out, DooM with vulkan as well (always above 90fps), both 1080p@75Hz.
I'll try DE:MD next week, but idk if it's properly optimized as on my rig nothing changes by switching apis.
The old rig:
x5470 4.2GHz (can go higher, 4.5 easy)
DFI P45 T2RS plus
8 GB DDR2 1066MHz
R9 290 DCU II OC (vRAM latency MOD)
Remember that on 775 chipset latencies must be tuned or your ghz means nothing.

 

Not for me with Fury X and Windows 10 (without AU).

I think a lot of errors in BF1 are caused by the Windows 10 AU, and the new WDDM and DXGI versions, which may be incompatible with the drivers somehow.