Download: AfterBurner 4.6.0 Beta 11 (Build 14248)

#5629832

cryohellinc

2019-01-21 09:54

Thank you, team, for the continuous effort.

#5629833

SpajdrEX

2019-01-21 09:56

Thank you mr. Unwinder

#5629837

Fox2232

2019-01-21 10:06

I can't see lowest 2 frequencies in V/F editor due to my vBIOS having lowest frequency states as 300 and 450MHz (before editing default config values): VFCurveEditorMinFrequency = 500 VFCurveEditorMaxFrequency = 2500 VFCurveEditorMinVoltage = 700 VFCurveEditorMaxVoltage = 1250 Locking to certain point with does not currently work on AMD's side either (19.1.1 RX-580). But I kind of expect that since AMD's driver ignores voltages in vBIOS. And can't even apply manually set values in Wattman after each restart.

#5629840

tensai28

2019-01-21 10:14

I'm curious why the official site still only has beta 9? https://www.msi.com/page/afterburner Not a big deal just wondering how you get these.

#5629841

Unwinder

2019-01-21 10:21

Fox2232:

I can't see lowest 2 frequencies in V/F editor due to my vBIOS having lowest frequency states as 300 and 450MHz: VFCurveEditorMinFrequency = 500 VFCurveEditorMaxFrequency = 2500 VFCurveEditorMinVoltage = 700 VFCurveEditorMaxVoltage = 1250 Locking to certain point with does not currently work on AMD's side either (19.1.1 RX-580). But I kind of expect that since AMD's driver ignores voltages in vBIOS. And can't even apply manually set values in Wattman after each restart.

So? Do you offer all the rest to see this unused clock range and make clock adjustment more troublesome (due to having more MHz per screen pixel) to match your vBIOS limits? That’s why you have a possibility to edit it. On : it is more than clearly reflected in the release notes that it is currently not supported for AMD cards.

#5629845

Fox2232

2019-01-21 11:10

Unwinder:

So? Do you offer all the rest to see this unused clock range and make clock adjustment more troublesome (due to having more MHz per screen pixel) to match your vBIOS limits? That’s why you have a possibility to edit it. On : it is more than clearly reflected in the release notes that it is currently not suppirted for AMD cards.

I would offer something else. AB is already reading default values. It may adjust this value based on that (1st time it is run or detects new GPU). I am pretty sure that AMD's side for now can appreciate seeing 200MHz more on low side than 500MHz above 2000MHz mark. (Which one can maybe achieve with new Radeon 7.) And while it may look like I did not read release notes. I did. And it would be much clearer if it involved in relevant text. As that's how it is depicted in AB 4.3 version for nVidia. (Place where I did read actual shortcut for opening V/F interface.) Thank you for implementing those things for AMD. But when main chunk of actual information is in much older part of document, do not expect that AMDs users will know and identify everything and connect all the dots scattered over dozen of pages immediately. (I know, it is a change long, not feature manual showing all relevant information to certain feature in one place.) If following text: "Voltage/frequency editor window is now available on AMD GPUs." included "+" And "P-States locking functionality is not implemented yet" included "", it would be much more clearer and allow AMD users much more quickly close 2 year gap in experience with given feature. = = = = There is the thing I would like to ask for and I know that you may get some flak for it. It is feature table and checkbox for AMD/nV/intel showing if it is implemented. because every time you introduce something new to AMD what nVidia's side already has, there is something people see in nV notes that may or may not be available to them. Currently I saw that stability testing for nV. And I did not found if it is hidden somewhere... I'll be looking through release notes till I find it or conclude that it is not for AMD (, yet). Which it seems it is not. For me that table would provide very valuable information. Saving a lot of time. In total, it may be tens of thousands hours saved across the globe. (And you very likely have that already as you track your project.)

#5629846

cryohellinc

2019-01-21 11:11

tensai28:

I'm curious why the official site still only has beta 9? https://www.msi.com/page/afterburner Not a big deal just wondering how you get these.

It's not guru3d team responsibility to update MSI Website. I am certain that new builds are sent towards MSI, however, it's up to MSI website admin/ marketing team to update the content.

#5629848

Fox2232

2019-01-21 11:27

As of the V/F editor values. They are applied upon restart... which is something Wattman fails to do miserably. That's one additional big annoyance AB solves for us on AMD's side. @OnnA : No more need for OverdriveNTool.

#5629850

Unwinder

2019-01-21 11:30

tensai28:

I'm curious why the official site still only has beta 9? https://www.msi.com/page/afterburner Not a big deal just wondering how you get these.

Those are DEVELOPMENT betas I provide for testers, they are not intended to be widely distributed and available anywhere besides Guru3D. They were not even intended to be in news or in main Guru3D downloads, but since some clickbait sites and "newsmakers" started constantly monitoring RTSS development thread and leaking development beta download links (and this way giving huge load to secondary servers where it was hosted) betas started publishing in news section (and hosted on the servers with higher bandwidth) now. Probably due to this reason we'll see less frequent beta updates now 🙁

#5629856

cryohellinc

2019-01-21 11:53

Unwinder:

Those are DEVELOPMENT betas I provide for testers, they are not intended to be widely distributed and available anywhere besides Guru3D. They were not even intended to be in news or in main Guru3D downloads, but since some clickbait sites and "newsmakers" started constantly monitoring RTSS development thread and leaking development beta download links (and this way giving huge load to secondary servers where it was hosted) betas started publishing in news section (and hosted on the servers with higher bandwidth) now. Probably due to this reason we'll see less frequent beta updates now 🙁

Time to switch to Alpha versions. 😉

#5629859

tensai28

2019-01-21 12:04

Unwinder:

Those are DEVELOPMENT betas I provide for testers, they are not intended to be widely distributed and available anywhere besides Guru3D. They were not even intended to be in news or in main Guru3D downloads, but since some clickbait sites and "newsmakers" started constantly monitoring RTSS development thread and leaking development beta download links (and this way giving huge load to secondary servers where it was hosted) betas started publishing in news section (and hosted on the servers with higher bandwidth) now. Probably due to this reason we'll see less frequent beta updates now 🙁

Okay I see. I was just wondering. Thank you for letting me know.

#5629865

Unwinder

2019-01-21 12:31

Fox2232:

I would offer something else. AB is already reading default values. It may adjust this value based on that (1st time it is run or detects new GPU). I am pretty sure that AMD's side for now can appreciate seeing 200MHz more on low side than 500MHz above 2000MHz mark. (Which one can maybe achieve with new Radeon 7.)

V/F editor is abstract from hardware and unified for NV and AMD GPUS, the limits cannot be made hardware specific that easily in the current implementation. So it is targeted at native Pascal/Turing frequency/voltage range (with some extension to cover Vega frequency/voltage range as well).

#5629878

KBDE

2019-01-21 13:53

Thanks Unwinder, very much appreciated 🙂

#5629896

Fox2232

2019-01-21 14:37

Unwinder:

V/F editor is abstract from hardware and unified for NV and AMD GPUS, the limits cannot be made hardware specific that easily in the current implementation. So it is targeted at native Pascal/Turing frequency/voltage range (with some extension to cover Vega frequency/voltage range as well).

I get it, but you are reading those actual values. If lowest power state says 150MHz and highest 850MHz for something like old HD 5850... (1st time GPU is detected, AB could guess meaningful values.)

#5629939