AMD Radeon Adrenalin Edition 18.1.1 Driver download

Eastcoasthandle

2018-01-25 21:48

DanEVO7:

I Have a good installation of Windows. I always do. I only use it for gaming so it's clean. And it does perform very well. Much much better from when i bought it. Through the years, both Microsoft and AMD, did improve many things and to be honest i'm amazed by the improvements i have seen up until now. Especially performance. Now.. back on benches. I run Assetto bench 2 times GM Enabled/DFO Unticked: POINTS: 15120 FPS: AVG=103 MIN=30 MAX=143 VARIANCE=2 CPU=74% GM Disabled/DFO Ticked: POINTS: 15257 FPS: AVG=104 MIN=43 MAX=143 VARIANCE=1 CPU=75%

That's a huge difference in min's. Game play has to be much smoother with GM Disabled/DFO Ticked. What are you getting with GM Enabled/DFO ticked?

#5514328

DanEVO7

2018-01-25 21:58

Eastcoasthandle:

That's a huge difference in min's. Game play has to be much smoother with GM Disabled/DFO Ticked. What are you getting with GM Enabled/DFO ticked?

GM Enabled/DFO Ticked: POINTS: 15161 FPS: AVG=103 MIN=27 MAX=145 VARIANCE=2 CPU=75% GM Disabled/DFO Unticked: POINTS: 15422 FPS: AVG=105 MIN=74 MAX=124 VARIANCE=0 CPU=74% Best combo is windows default it seems for Assetto

#5514330

Eastcoasthandle

2018-01-25 22:03

DanEVO7:

GM Enabled/DFO Ticked: POINTS: 15161 FPS: AVG=103 MIN=27 MAX=145 VARIANCE=2 CPU=75% GM Disabled/DFO Unticked: POINTS: 15422 FPS: AVG=105 MIN=74 MAX=124 VARIANCE=0 CPU=74% Best combo is windows default it seems for Assetto

Indeed! GM Disabled/DFO Unticked looks to offer the best results for Assetto for you. Although I'm not sure if that MS default. I thought it was GM Enabled and DFO Unticked. But I get what your are saying. Looks like MS is getting their optimizations straight on certain games with your target PC Setup. Since Assetto needs all the "Horse Power" that your PC can give it appears to be the reason why it scored the highest out of the other 3 configs. It also appears you didn't have any background processing issues. So having GM enabled was no benefit to you. That makes sense Very interesting indeed. Thanks for your hard work in this!

#5514331

OnnA

2018-01-25 22:03

^^ Yup as i said earlier. Best to have it on default, and only thinker the Tick/un-tick DFO === Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\GameBar] "ShowStartupPanel"=dword:00000000 "GamePanelStartupTipIndex"=dword:00000003 "AllowAutoGameMode"=dword:00000001 "UseNexusForGameBarEnabled"=dword:00000000 ===

#5514334

DanEVO7

2018-01-25 22:14

OnnA:

^^ Yup as i said earlier. Best to have it on default, and only thinker the Tick/un-tick DFO === Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\GameBar] "ShowStartupPanel"=dword:00000000 "GamePanelStartupTipIndex"=dword:00000003 "AllowAutoGameMode"=dword:00000001 "UseNexusForGameBarEnabled"=dword:00000000 ===

I'll try your reg settings tomorrow. Now it's bed time GN and happy settings hunting guys!

#5514359

Eastcoasthandle

2018-01-26 00:04

Here is what I got with current drivers and Forza 7 built in benchmarking app at 1440p. MLAA enabled through Crimson. 4 Runs each for a total of 16 runs. Max and averages were within 2 fps on all runs. However, I noticed deviations in Minimums. So, I used minimums to obtain the following averages: Game Mode Off, Full Screen Optimization Off....................72.425 FPS <--min's Game Mode Off, Full Screen Optimization On....................72.375 FPS <--min's Game Mode On, Full Screen Optimization Off....................72.05 FPS <--min's Game Mode On, Full Screen Optimization On....................70.25 FPS <-min's For me having Game Mode Off and On, Full Screen Optimization On created the most stutter. There was no noticeable performance gain with Game Mode Off, Full Screen Optimization Off. However, the animations of characters, Racing, etc is smoother.

#5514635

DanEVO7

2018-01-26 21:40

OnnA:

Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\GameBar] "ShowStartupPanel"=dword:00000000 "GamePanelStartupTipIndex"=dword:00000003 "AllowAutoGameMode"=dword:00000001 "UseNexusForGameBarEnabled"=dword:00000000 ===

Tried these settings on Assetto and the results: POINTS: 15401 FPS: AVG=105 MIN=8 MAX=144 VARIANCE=0 CPU=75%

#5514643

AlleyViper

2018-01-26 22:03

AC's bench is really unreliable for the min FPS value because of a dip that can happen right at start, giving you those very low numbers on a instant that won't reflect in the avg.

#5514736

Jackalito

2018-01-27 12:12

OnnA:

Side note: ATI Tech. driver Team is working Hard to give us rewrited & revamped Drivers for New API & OS Win_X All is Digital now and very very fast (look at Latency), of course we need to wait until they finish all Radeon GPUs lineup 🙄

Thanks for the heads up! But I don't understand what you mean exactly by "all is digital now" Could you share more details about that? Thanks 😉

#5514756

DanEVO7

2018-01-27 15:37

AlleyViper:

AC's bench is really unreliable for the min FPS value because of a dip that can happen right at start, giving you those very low numbers on a instant that won't reflect in the avg.

Yeap... I know that. But i always get almost the same results. That is: GM Disabled/DFO Unticked: POINTS: 15422 FPS: AVG=105 MIN=74 MAX=124 VARIANCE=0 CPU=74% (min fps always around 74 and max always around 124) And Onna's reg settings: POINTS: 15401 FPS: AVG=105 MIN=8 MAX=144 VARIANCE=0 CPU=75% (same thing. min always around 8 and max always around 144)

#5514758

AlleyViper

2018-01-27 15:48

Sometimes you just need to start the bench twice and that very low min will go away. As an example, I usually let it run once until it passes Les Combes (sometimes a stutter can happen there the first time, probably for some car LOD switching), then restart it for a full run (or 2-3 to avg). Usually the very low dip on the first run goes away, so its easier to compare results. I guess the min shouldn't be taken as anything useful, because it doesn't happen while the benchmark is actually running (while driving the lap).

#5514918

OnnA

2018-01-28 16:51

In SW BF2 HBAO Full is Fixed now, in Death Star (Starship mode) are corruptions in DX11.1 Game runs poorly with DX12 ON BF1 DX12 don't start at all (some DX error pops up), DX11.1 w/SweetFX working like a charm tho. Exclusive DX12 Titles working like never before 😛 (FH3/FM7) Rest of my Games performs quite good. Im still more into 17.12.1 WHQL (good preformer, nice Features) or 17.9.3 WHQL (good performer but WDDM 2.2, All is working w.o. Problems) IMHO WDDM 2.3 is still not Fully Ready in any driver. WDDM 2.2 Driver is still way to go if you need Solid Ones. (Install 18.1.1 then 17.9.3 on it to have all profiles ready for upcoming Operational WDDM 2.3 driver) as for Chill, not every game is Chill Ready. Some games gets flicker fest ! for those Turn OFF Chill, leave only FPS Cap for FreeSync Edit.2 Just Played some DeusEx MkD DX12 & ME:Andromeda DX11.1 -> Just Awesome, so smooth (Chill range 64-70) I have 18.1.1 WHQL still installed, some tinkering and it's Fine (only fine) Ok 18.1.1 summarized. Ne01 Out 😎

#5514940

Eastcoasthandle

2018-01-28 18:08

^^ "BF1 DX12 don't start at all (some DX error pops up)" I can confirm this. I can get into the menu but if I start a actual game it freaks out. Never had that before.

#5514946

Pyrage

2018-01-28 18:39

OnnA:

In SW BF2 HBAO Full is Fixed now, in Death Star (Starship mode) are corruptions in DX11.1 Game runs poorly with DX12 ON BF1 DX12 don't start at all (some DX error pops up), DX11.1 w/SweetFX working like a charm tho. Exclusive DX12 Titles working like never before 😛 (FH3/FM7) Rest of my Games performs quite good. Im still more into 17.12.1 WHQL (good preformer, nice Features) or 17.9.3 WHQL (good performer but WDDM 2.2, All is working w.o. Problems) IMHO WDDM 2.3 is still not Fully Ready in any driver. WDDM 2.2 Driver is still way to go if you need Solid Ones. (Install 18.1.1 then 17.9.3 on it to have all profiles ready for upcoming Operational WDDM 2.3 driver) as for Chill, not every game is Chill Ready. Some games gets flicker fest ! for those Turn OFF Chill, leave only FPS Cap for FreeSync I have 18.1.1 WHQL still installed, some tinkering and it's Fine (only fine) Ok 18.1.1 summarized. Ne01 Out 😎

At least for me, BF1 always had issues with dx12. Whenever I use it, i'll get massive stutters when I join a match, that may or may not go away after a few minutes. I'm still waiting to play a dx12 game that works flawlessly in dx12 mode.

#5514999

Eastcoasthandle

2018-01-29 01:39

OK, I have to admit, I haven't used the Relive recording feature since November. Having said that with this version of Crimson the OSD for MSI Afterburner is pixeled 😕. Is this by design? Is there a way to turn off OSD pixelation? Why would that be an option? o_O https://image.ibb.co/i6GmeG/pixelation.jpg

#5515328

Romulus_ut3

2018-01-30 04:18

Just my opinion: The ReLive performance metrics come with an added performance hit. You're better off using MSI Afterburner instead.

#5515392

Krteq

2018-01-30 10:15

That IS MSI Afterburner OSD 🙄

#5515393

LocoDiceGR

2018-01-30 10:17

Romulus_ut3:

Just my opinion: The ReLive performance metrics come with an added performance hit. You're better off using MSI Afterburner instead.

o_O

#5515420

Romulus_ut3

2018-01-30 11:57

Krteq:

That IS MSI Afterburner OSD 🙄

LocoDiceGR:

o_O

Ooops. Sorry fellas. It was really late when I saw the post and I just had a quick glance at the image, and saw all the texts in red and thought it was the AMD ReLive OSD. I don't have this issue with MSI AB and the Adrenalin 18.1.1, but that doesn't mean it doesn't exist. But what I said regarding the ReLive performance OSD Metric isn't untrue in anyway.

#5515433

LocoDiceGR

2018-01-30 12:38

Romulus_ut3:

But what I said regarding the ReLive performance OSD Metric isn't untrue in anyway.

Same goes with every 3rd party program.