#5616962

mtrai

2018-12-13 14:40

https://imgur.com/1wuhhbT

#5616963

mikeysg

2018-12-13 14:42

Umm, not out yet methinks. I tried the link, plus went to the AMD website, not available yet.

#5616966

mtrai

2018-12-13 14:48

mikeysg:

Umm, not out yet methinks. I tried the link, plus went to the AMD website, not available yet.

Hilbert has them linked now.

#5616968

Hilbert Hagedoorn

Administrator

2018-12-13 14:49

Updated and mirrored @ Guru3D 😉

#5616969

mikeysg

2018-12-13 14:50

mtrai:

Hilbert has them linked now.

Hmmm, all I get is the link to the 18.12.1.1 driver, which I've had installed a while back.

#5616973

mikeysg

2018-12-13 14:55

Okay, after a few refreshes, I finally got the 18.12.2 download link.....

#5616981

Alessio1989

2018-12-13 15:08

What the hell are AMD doing with drivers? Still no SM6.1 barycentric semantics, although every GCN hardware is perfectly able to support them (in fact they support barycentric semantics on consoles and on pc with AGS).

This release is not compatible with Microsoft® PIX. For Microsoft® PIX support with Radeon Software Adrenalin 2019 Edition please click here.

Sparse Support is Enabled Sparse support relaxes the requirement to have memory allocated and bound to resources prior to being used. It also relaxes the requirement for the bound memory to be contiguous and for the memory bindings to be immutable.

Two years to get tiled resources working (again) on khronos vulkan? Really?

#5617012

DLD

2018-12-13 15:49

"This is the new Adrenalin 2019" A letter to AMD: "Dear AMD, we've been consuming too much adrenalin lately, so it made us think we're already deep into the year 2019. Shell we try a little insulin for a change? Marry Christmas and Happy New Year! Your customers, from the first half of December 2018"

#5617023

mikeysg

2018-12-13 16:08

Just a headsup, if you have MSI AB (or other 3rd party util like this) and after you've installed this driver, check to see if your custom fan speed is working or not. I'd to uninstall this driver because not only did custom fan in AB not work with this driver, it seemed to mess up my card's (gigabyte RX VEGA 64 Gaming OC) own fanspeed. Couldn't even run Heaven benchmark for a few seconds (during which temp went straight up) but even when temp hit 60C, the fans on my card didn't spin (I actually took a look at the physical card, as well as the sensor on GPUZ). when temp hit 69C after mere seconds into the benchmark, I'd had to quit. Yes, the fan was spinning but pretty slowly given the temp which exceeded 70C.

#5617027

vbetts

Moderator

2018-12-13 16:12

Works no issue with RDV64. Have not tested any games yet, but fan curve is still there.

#5617041

DeusEXMachina

2018-12-13 16:27

No auto-tunning for porlaris....:(:( well, old school overclock to rescue 🙂:):)

#5617217

Agonist

2018-12-14 02:15

No VSR on my 21:9 with my Fury X. I really wanted 5k 21:9 but up too 3840x1620 70hz works with CRU for me. So I do not know what the limitation with VSR is in the driver. Even 3840x1620 60hz worked on my R9 290x when I had it using CRU. I really want 5k for DX10/11 older titles since only geodasoto works with DX9. I really was wanting a Vega 56/64, but the VSR 21:9 5k makes it really tempting to just give in and get one.

#5617345

Exodite

2018-12-14 11:27

robbo247:

Anyone else have clocklock or overvolt issues with this driver as my card locks to state 7 after running 3dmark and overvolts too 1.292 which is very worrying.

I've only run ~90 mins or so of 3DMark testing (primarily Time Spy) while I'm migrating my settings fully to WattMan but so far I haven't experienced anything like that on my Vega 56. Certainly a couple recoveries from pushing the card too hard but that was expected. 🙂