Tomorrow probably

Nice, probably tomorrow would be my guess too but it could be a later night (Local time for here in Sweden.) release too since it's already partially online though restricted. 🙂

IMO it will hit us Tonight, with some Bugs squashed. but i will stay on 17.9.3 + Vulcan from 18.1.1 😉 All in all i don't have any issues with this driver. I will try to Mod them some more in time, THX goes to Romulus_ut3 (yeah You MF 😀) for keepin' Repository updated. Also we have Chill for any game even with 17.9.3 (but you need to install 18.1.1 first) The File is the same (but i need to adjust settings manually by Notepad++) -> C:\Users\****\AppData\Local\AMD\CN\gmdb.blb [spoiler= Battlefield 1 in gmdb.blb looks the same as in Adrenalin] "amdId": 833, "appDisplayScalingSet": "FALSE", "appHistogramCapture": "FALSE", "arguments": "", "exe_path": "Y:\\Games\\Battlefield 1\\bf1.exe", "eyefinity_enabled": "FALSE", "framerate": [ { "bdf": 10496, "settings": [ { "featureId": 0, "featureValue": { "acFPSCurrent_": 70, -> here for Min FPS "acFPSEnabled_": 1, "dcFPSCurrent_": 70, -> here for Max FPS "dcFPSEnabled_": 1 } } ] } ], "framerate_enabled": "TRUE", "hidden": "FALSE", "image_info": "Y:\\Games\\Battlefield 1\\bf1.exe", "install_location": "", "installer_id": "", "lnk_path": "", "manual": "FALSE", "origin_id": -1, "overdrive": [ ], "overdrive_enabled": "FALSE", "profileCustomized": "TRUE", "profileEnabled": "TRUE", "steam_id": -1, "title": "bf1", [/spoiler][spoiler][/spoiler]

downloading now .

yeah it's live now. Radeon FreeSync may rapidly change between min and max range when enabled causing stutter in fullscreen games on single display system configurations. about time they fix it.

downloading now 🙂 yep works like a charm AMD rocks 😛

NvidiaFreak650:

yeah it's live now. Radeon FreeSync may rapidly change between min and max range when enabled causing stutter in fullscreen games on single display system configurations. about time they fix it.

I found a working solution for this also 😉 Turn OFF any V.Sync + Give 70/64FPS on my screen (70Hz BTW) or Disable Chill for some other games. But i can't do s..it about Those coruptions in SW BF2 in Space Assault battles (and mostly on Death Star map) yeah those triangles everywhere lolZ o_O

OnnA:

I found a working solution for this also 😉 Turn OFF any V.Sync + Give 70/64FPS on my screen (70Hz BTW) or Disable Chill for some other games. But i can't do s..it about Those coruptions in SW BF2 in Space Assault battles (and mostly on Death Star map) yeah those triangles everywhere lolZ o_O

Yeah I was doing that but they fix it now. https://i.imgur.com/cwW88PG.png

JonasBeckman Give Us comparison 😀 What Games profiles are Updated etc. I will know if it's worth to Install 18.2.1 then Revert to my 17.9.3 😉 (IMO SW BF2 is not fixed yet)

I just noticed this had been released, installed them and did the usual setting up and cleaning out the previous driver files. 🙂 So from the INF file we have: Driver is dated January 31st compared to January 12th for 18.1.1 Driver version 23.20.15017.3010 compared to 23.20.15015.1002 The [Manufacturer] line was incremented with a .1, not entirely sure what's that about. IE instead of NTamd64.10.0, it's NTamd64.10.0.1, Which also shows for the other categories in the INF such as instead of [ATI.Mfg.NTamd64.10.0] it's [ATI.Mfg.NTamd64.10.0.1] Also appears to be WHQL and signed by both AMD and Microsoft so all the mobile GPU entries are back in the INF again compared to AMD's beta driver releases. There's a couple of settings added for some of these GPU's too. [ati2mtag_Topaz_SoftwareDeviceSettings] HKR,, EnableAspmL1, %REG_DWORD%, 0 HKR,, EnableAspmL0s, %REG_DWORD%, 0 [ati2mtag_Polaris11_SoftwareDeviceSettings] HKR,,BDFFCC9810EFE6EFFD3E, %REG_BINARY%,62,2A,06,E0 (There were a few like this already, not really certain what this does due to it's name being indecipherable.) [ati2mtag_Polaris10_SoftwareDeviceSettings] HKR,,BDE8DC9820EFD7EFFD18, %REG_BINARY%,62,3D,06,E3 HKR,,BDE8DD9820EFD7EFFD10, %REG_BINARY%,62,37,06,E2 [ati2mtag_RemoveDeviceSettings] HKR,, DalFeatureForceLidOpen [Strings] AMD6863.1 = "Radeon Vega Frontier Edition" <- This is gone in this driver, no longer installs on Frontier GPU's as a result? Since there's so many variations of mobile GPU models it looks like there's been a lot of adjustments but as mentioned these entries are usually gone from AMD's beta driver releases and present in the full WHQL sets. And then the Atiapfxx.blb file. 🙂 Crossfire profile changes: Endless Enemies Sea of Thieves These two were updated. DXX profile changes: Autodesk Inventor Autodesk 3DSMax Fortnite These three were updated. Fallout4VR Final Fantasy 12 Zodiac Age These two were added. PXDynamic and HighPerfGPUAffinity: Assassin's Creed Origins Far Cry 5 Final Fantasy 12 Zodiac Age These three were added, Far Cry 5 also has a listing for Crossfire. (Which I think a previous comparison showed Far Cry 5 having a crossfire profile already.) Other changes? Assassin's Creed Origins DXX profile now also encompasses DiscoveryTourAncientEgypt.exe for the tour mode coming later this month.

I like to get my drivers early. Thank you.

From Reddit about the 100% GPU bug that someone mentioned. AMD_Kyle RTG Engineer - 5 hours ago: Hey just to let you know we do know about this issue - and it turns out to be pretty complex to resolve. As a workaround for now you can kill the AMDDVR process which should return the GPU utilization to the correct levels.

NvidiaFreak650:

yeah it's live now. Radeon FreeSync may rapidly change between min and max range when enabled causing stutter in fullscreen games on single display system configurations. about time they fix it.

I had the impression that this happened because I have a secondary 60Hz monitor and Windows 10 was messing up with the primary freesync monitor somehow since AMD never listed it as a known issue. Hopefully it is also fixed when playing videos in browser since it's where it sometimes happens for me.

first time problem ever, these drivers don't allow me to create usual Eyefinity setup. My monitors start flickering like crazy then system hangs until it's atikmpag BSOD. Already tried the usual DDU procedure but no go : (

Coming back from sleep mode still causes a crash.

LocoDiceGR:

From Reddit about the 100% GPU bug that someone mentioned. AMD_Kyle RTG Engineer - 5 hours ago: Hey just to let you know we do know about this issue - and it turns out to be pretty complex to resolve. As a workaround for now you can kill the AMDDVR process which should return the GPU utilization to the correct levels.

So after all they do care about you guys 😉 They need to do a lot of work for Vega now, priorities 🙄

Lurk:

first time problem ever, these drivers don't allow me to create usual Eyefinity setup. My monitors start flickering like crazy then system hangs until it's atikmpag BSOD. Already tried the usual DDU procedure but no go : (

Did you usde DDU in safe mode?

Eastcoasthandle:

Did you usde DDU in safe mode?

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html New update by the way.. 🙄 ChangeLog: -Added a safety measure that prevent DDU doing the registry cleaning and files/folders removal if a problem with the Windows SETUPAPI is detected. -Additional NVIDIA cleanup -Small fixes -Many translations updates from contibutors (Thanks)

LocoDiceGR:

From Reddit about the 100% GPU bug that someone mentioned. AMD_Kyle RTG Engineer - 5 hours ago: Hey just to let you know we do know about this issue - and it turns out to be pretty complex to resolve. As a workaround for now you can kill the AMDDVR process which should return the GPU utilization to the correct levels.

Is this something new?

Octopuss:

Is this something new?

Few drivers back. While it is 100% utilization. It is not full load. It was increasing idle power consumption of my Fiji from 15 to some ~45 Watts. If you are not using ReLive, then just rename mentioned binary and kill process to prevent it from starting. Because process will be reloaded after killing. And in some time it will again go to 100% utilization.