Download: Radeon Software Crimson ReLive 17.2.1 driver
Click here to post a comment for Download: Radeon Software Crimson ReLive 17.2.1 driver on our message forum
JonasBeckman
New branch, 16.60.xx instead of 16.50.xx might be some larger changes in this driver then though that's just a guess.
EDIT: The usual atiapfxx.exe -r -sys -s test.xml dump and comparison.
There's a list of what I assume is OpenGL extensions or definitions.
GLSLMaxGsVerts <- Removed
w2Iju7zxQh <- Added
For Crossfire profile flag changes the following games were changed or added.
For Honor <- Changed
Battle Field 1 <- Changed (Yeah it's listed as "Battle Field" in the driver.)
Prey <- Added (2017 version of the game.)
Resident Evil 7 <- Removed?
Various changes to (Linux? Mac?) OpenGL game properties.
(Gnome Shell, CS:GO, Metro Last Light, Deus Ex Mankind Divided, No Man's Sky though that one actually uses OGL even on Windows)
EDIT: For Honor has a DX12 profile as well, interesting.
(Scimitar Engine is mentioned, which one was that again? from Prince of Persia??)
EDIT: Found profiles for Sniper Elite V4 and Halo Wars 2 too.
(Not specifically DX12, just game profiles.)
PrMinisterGR
Any chance of gathering these awesome posts of yours in one place, so that we can see them per driver?
Kaarme
Maybe I should finally bite the bullet and try these Relive drivers. I'm not overclocking my video card nor using any third party software to configure it, nor do I have multiple video cards or even multiple screens, just a single 60Hz one. I should be as safe as one can ever be with a 390, now that AMD is starting to discriminate that generation.
JonasBeckman
Kn00t had a really good overview of driver profile changes and additions even going into the .dll files but it hasn't been updated in a while, I could try to search trough the earlier driver topics for well I forgot when I started doing this but probably somewhere for the 15.x drivers though I don't know how well the search engine will work since I think it only ever displays the first ten pages worth of hits but I can certainly try to do a more cohesive list of updated profiles.
Unfortunately I don't have much insight into what some of these actually mean though I suppose no-one outside of AMD or Nvidia's driver development teams would far as that info goes so while it's possible to see what a Crossfire profile has been changed from it's difficult to say how well the profile works and what it works for since if I were to guess each of the "bits" in that Crossfire flag has some sort of meaning.
0x23,0x00,0x00,0x01,0x00,0x00,0xFF,0xFF,0x48,0x00,0x00,0x00,0x17,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x22,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x05,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x06,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x13,0x00,0x00,0x00,0x04,0x00,0x00,0x00,0x1C,0x00,0x00,0x00,0x60,0x00,0x00,0x00,0x35,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x36,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0xFF,0xFF,0xB4,0x01,0x00,0x00,0x08,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x18,0x00,0x00,0x00,0xC0,0x01,0x00,0x00,0x03,0x00,0x00,0x00,0x74,0x00,0x00,0x00,0x00,0x03,0x00,0x00,0x80,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x28,0x08,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xD8,0x01,0x00,0x00,0x03,0x00,0x00,0x00,0x72,0x00,0x00,0x00,0xFE,0xFF,0xFF,0x1F,0xFE,0xFF,0xFF,0x1F,0xFF,0xFF,0xFF,0xFF,0x28,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xE0,0x01,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x06,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xE8,0x01,0x00,0x00,0x03,0x00,0x00,0x00,0x8E,0x01,0x00,0x00,0x00,0x10,0x00,0x00,0x80,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x28,0x08,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xF0,0x01,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x4B,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x28,0x08,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0xF8,0x01,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x64,0x00,0x01,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x28,0x08,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x00,0x02,0x00,0x00,0x03,0x00,0x00,0x00,0x8E,0x01,0x00,0x00,0x00,0x10,0x00,0x00,0x00,0x08,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x28,0x08,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x08,0x02,0x00,0x00,0x05,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x0A,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x06,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x26,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x26,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x26,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x21,0x00,0x00,0x01,0x02,0x00,0xFF,0xFF,0x00,0x00,0x00,0x00,0x03,0x00,0xFF,0xFF,0x04,0x00,0x00,0x00,0x00,0x00,0x00,0x00,
True
That's a lot of flags, 00 and 01 might be as simple as on and off but then there's like what, some 100+ "bits" in total ranging from 0x00 to 0xFF (255?) heh yeah that's probably close to impossible to unravel.
(Hah so yeah small wonder it takes the developers time to implement Crossfire/SLI support for DX12 games now that it's more on their end of the GPU support side though then again low-level API's might allow for some easier access and utilization with multi-GPU support as well.)
Then there's the DXX "blob" flags too on top of that.
0x22,0x00,0x00,0x01,0x00,0x00,0xFF,0xFF,0x10,0x00,0x00,0x00,0x13,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x55,0x00,0x00,0x00,0x01,0x00,0x00,0x00,0x01,0x00,0xFF,0xFF,0x6C,0x00,0x00,0x00,0x02,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x35,0x00,0x00,0x00,0x00,0x10,0x00,0x00,0x00,0x10,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x48,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x80,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x35,0x00,0x00,0x00,0x00,0x20,0x00,0x00,0x00,0x08,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0x48,0x00,0x00,0x00,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0xFF,0x08,0x00,0x00,0x00,0x88,0x00,0x00,0x00,0x00,0x0A,0x00,0x40,0x28,0x00,0x00,0x00,0x00,0x0A,0x00,0x40,0x28,0x00,0x00,0x00,
But at least having a overview of updated Crossfire profiles or just new game profiles in general could be useful too. 🙂
Occasionally there's also upcoming games listed in these files though it's usually in some form of engine name or project name and not the direct game name or final name of the game exe.
For example, guessing it's a work name for IDTech, DOOM perhaps or maybe the engine in general.
I like this one added in I think it was 17.1.1
Anyways I'll see if I can't find a way to compile most of my earlier posts into something a bit more manageable, at least for the game profile changes. 🙂
Agonist
LMFAO this crap again.
Its a 3 1/2 year old chip just about. Its gonna get aged, and lack new features but serious, AMD has a much better track record of keep optimizations for older cards then nvidia.
Since 16.2.2 2nd update, my 290x in rig #2 has had zero issues with ReLive drivers.
Kalel83
This driver causes grass to flicker in ESO.
Had to rollback.
Crazy Serb
Optimizations we cant use because their drivers bugs basic functionality on these older cards. And the only reason why these optimizations applies to all gcn cards is because they all work in completely same way. Even efficiency is not improved on architectural level since 1st gen gcn (reason why pitcairn was rebranded 2 times).
Just because there are people like you, I hope they will make some bug for fury when vega comes out, because fury wont be needed anymore
AlleyViper
Waiting for the form to be updated to report once again on the UVD bug.
PrMinisterGR
It's not crap.
OnnA
CRU don't work (custom resolutions don't work)
Before Login -> strange Colours appears for a moment.
This driver is very fresh IMO, they change something big here 🙂
Hmm too much changes to describe here.
For now reverted to WHQL 17.1.2, need more time to set things up here.
Good news that Old AMD-Catalyst-15.11.1Beta-Nov14 working with it NP.
So we have All Options Panel in this also.
Greets 🤓
PS.
Please check 3Dmark + API Test + Some Game tests.
Virs
Happened to me too, that's a shame.
theoneofgod
Just tried it too. Grass is flickering like mad 😀
moaka
Here api test 17.2.1 vs 17.1.2 vs 16.11.4
http://www.3dmark.com/compare/aot/191737/aot/191777/aot/178885#
My best dx 12 Api test with 17.2.1 , nice improve to dx11 draw calls per frame with 17.x but better dx 11 draw calls per second with 16.x
Tested many times with the same results .
17.2.1 tested on BF1 run like a charm .
OnnA
Yup, on my side also.
But CRU don't work for me, and i have after Boot up 1600:1200 85Hz
now every time i need to set it to my 1920:1440 74.2Hz
Tested on 1050/570 -42mV +8POW
API Test 17.2.1 :
DX11 ST = 1 050 081
DX11 MT = 1 051 756
DX12 = 14 836 813
Mantle = 13 236 489
17.1.2 Feb6 ReLivE WHQL:
DX11 ST = 956 949
DX11 MT = 902 345
DX12 = 13 521 641
Mantle = 13 221 416
So it's best of the best for my config, hmm where is my Zen? :3eyes:
moaka
Oh nice ! Yeah need to see it 🙂
BugMeister
- fabulous performance here..
- brilliant!!
..I'll get me coat..
:lurk:
THEAST
Oh, look, a fix for GCN v1.0; we should celebrate! O_O
Any comments on compatibility with MSI Afterburner for old GCN cards?
ObscureangelPT
What compatibility?
It's working in here..
THEAST
AMD's half-broken porting of OCing API for older GCN cards to the latest API that results in erratic behavior with memory overclocking not only in Afterburner and other third-party tools but also Wattman which has also been confirmed by Unwinder.
Rambo
didn't you touch sliders? :banana: OSD works great but sliders (for me anyway) are getting my PC out. Had to OC by wattman.
