MSI Afterburner 4.6.0 Final

MSI Afterbur­ner ist ein Über­tak­tungs­tool für Gra­fik­kar­ten, dass trotz des Namens auch bei Nvi­dia- und AMD-Gra­fik­kar­ten von ande­ren Her­stel­lern funk­tio­niert und vom “Guru3D RivaT­u­ner Team” ent­wi­ckelt wur­de. Neben der Über­tak­tung bie­tet es Funk­tio­nen zur Über­wa­chung der wich­tigs­ten Ein­stel­lun­gen der Gra­fik­kar­te, zum Erstel­len von Screen­shots und Video­auf­zeich­nun­gen, sowie ein Over­lay in Spie­len. Afterbur­ner 4.6.0 Final bie­tet jetzt auch vol­le Unter­stüt­zung für AMDs Rade­on VII.


AfterBur­ner v4.6.0 final

  • Inclu­des full RVII sup­port, inclu­ding over­clo­cking (which was mis­sing in the pre­vious ear­ly b15 build).
  • Now you can use <Tab> and <Shift>+<Tab> keys to select next/previous point on the cur­ve. This fea­ture is use­ful for tho­se who pre­fer to use key­board <Up>/<Down> keys to fine-tune selec­ted point fre­quen­cy off­set ins­tead of adjus­ting the point with mou­se cur­sor. I’m not sure if many of you know that, but I’ll remind that you can also hold <Ctrl> while fine-tuning fre­quen­cy off­set with <Up>/<Down> keys to jump to the nea­rest fre­quen­cy value roun­ded to 10MHz
  • Now you can press <Enter> key to edit selec­ted point fre­quen­cy off­set from key­board. Alter­na­te­ly you may press <Shift>+<Enter> to spe­ci­fy abso­lu­te tar­get fre­quen­cy value, so the edi­tor will cal­cu­la­te desi­red off­set automatically
  • Slight­ly chan­ged key­board con­trol inter­face for AMD imple­men­ta­ti­on of V/F cur­ve edi­tor. Pre­vious­ly you could select P‑State and fine-tune fre­quen­cy with <Up>/<Down> or <Ctrl>+<Up>/<Ctrl>+<Down> keys or fine-tune vol­ta­ge <Left>/<Right> or <Ctrl>+<Left>/<Ctrl>+<Right> keys. Now both fre­quen­cy and vol­ta­ge are adjus­ted with <Up>/<Down> or <Ctrl>+<Up>/<Ctrl>+<Down> keys and vol­ta­ge or fre­quen­cy key­board input focus is selec­ted with <Page­Up> / <Page­Down> keys. Vol­ta­ge or fre­quen­cy key­board input focus is now high­ligh­ted by selec­ted point bright­ness on the cur­ve. Key­board input focus also affects new <Enter> / <Shift> + <Enter> func­tio­n­a­li­ty, allowing you to type in tar­get vol­ta­ge or fre­quen­cy in both off­set or abso­lu­te form
  • Simi­lar to NVIDIA imple­men­ta­ti­on, now you may also hold <Alt> when drag­ging V/F cur­ve point on AMD sys­tems. This will result in moving who­le cur­ve up/down while pre­ser­ving each point’s offset
  • Added undo/redo sup­port to voltage/frequency cur­ve editor: 
    • Now voltage/frequency cur­ve edi­tor is saving up to 1024 last sta­tes of the cur­ve during edi­t­ing and allows you to undo/redo chan­ges with <Ctrl>+<Z> or <Ctrl>+<Y> / <Ctrl>+<Shift>+<Z> keys
    • Undo histo­ry is dis­car­ded when you app­ly the cur­ve, for­ci­b­ly reread it from hard­ware with <F5> key or switch to dif­fe­rent GPU on mul­ti-GPU system
    • Num­ber of recor­ded undo/redo steps is dis­play­ed in squa­re bra­ckets in the edi­tor win­dow caption
  • App­li­ca­ti­on pro­per­ties dia­log win­dow is now dis­play­ed with top­most style when the pro­per­ties are acti­va­ted from detached moni­to­ring win­dow and “Always on top” mode is enab­led for it
  • NVIDIA Scan­ner com­pon­ents are updated to latest ver­si­on, NVML.dll issue should be addres­sed now

RTSS 7.2.1 

  • Slight­ly refac­to­red Direct3D and Vul­kan On-Screen Dis­play ren­de­ring code­paths due to imple­men­ta­ti­on of optio­nal offscreen ren­de­ring mode. This mode is cur­r­ent­ly dis­ab­led by default, it is reser­ved for future ver­si­ons as a code­ba­se for asyn­chro­nous On-Screen Dis­play ren­de­ring implementation
  • Chan­ged power user pro­tec­ted set­tings locking approach. Now power user set­tings (“Enab­le Cus­tom Direct3D sup­port” opti­ons and Vector2D On-Screen Dis­play ren­de­ring mode) are locked for enab­ling by default in the glo­bal pro­fi­le only, but you can still chan­ge them at app­li­ca­ti­on pro­files level
  • Now RivaT­u­ner Sta­tis­tics Ser­ver vali­da­tes Direc­tX run­ti­mes instal­la­ti­on at start­up and dis­plays warning mes­sa­ge if requi­red Direc­tX run­ti­me com­pon­ents are mis­sing. Power users may dis­able this warning mes­sa­ge as well as any pre­vious­ly exis­ting dia­gnostic warning messages dis­play­ed at RivaT­u­ner Sta­tis­tics Ser­ver start­up and enab­le silent start­up mode via the con­fi­gu­ra­ti­on file if necessary
  • Added user exten­d­a­ble exclu­si­ons list for desk­top win­dows noti­fi­ca­ti­on per­for­med during instal­la­ti­on and unin­stal­la­ti­on of sys­tem CBT hooks. Cur­r­ent­ly the only exclu­si­on in the list is Micro­soft Out­look pro­cess, which pre­vious­ly ten­ded to dis­play help popup win­dow on clo­sing RivaT­u­ner Sta­tis­tics Server
  • Ren­de­ring pipe­line flus­hing no lon­ger stays acti­ve if you enab­le scan­li­ne sync mode but dis­able frame­ra­te limi­t­ing sup­port with hot­keys from MSI Afterburner
  • Fixed mult­hi­threa­ded acti­ve busy-wait loop based frame cap­tu­re imple­men­ta­ti­on, which could pre­vent desk­top video­cap­tu­re from working in the pre­vious version
A few important notes for RADEON VII owners:
  • Core vol­ta­ge sli­der in MSI AB is sup­po­sed to be locked on RVII, that’s nor­mal and by design. On the pre­vious AMD GPUs the sli­der pro­vi­ded direct vol­ta­ge con­trol mode imple­men­ted via low-level access to SMC or vol­ta­ge con­trol­ler (sli­der posi­ti­on defi­ned eit­her full tar­get vol­ta­ge over­ri­de or P‑State inde­pen­dent vol­ta­ge off­set) and such vol­ta­ge adjus­t­ment form was requi­red becau­se nati­ve AMD driver’s vol­ta­ge adjus­t­ment ran­ge was too low. On RVII seri­es cards AMD dri­ver allows up to 1.2V over­vol­ta­ge (from default 1V) and vol­ta­ge con­trol is pro­vi­ded in MSI AB at voltage/frequency cur­ve edi­tor level. So sim­ply open the edi­tor (eit­her press VF edi­tor but­ton in the skin next to core clock sli­der or hit <Ctrl>+<F> key­board short­cut to open the edi­tor) and you’ll be able to adjust vol­ta­ge there.
  • Tem­pe­ra­tu­re limit sli­der is also sup­po­sed to be locked by design on RVII, it was a part of old AMD fan con­trol algo­rithm. It is gone with Adre­na­lin 2019 dri­vers fami­ly when fan cur­ve adjus­t­ment approach was intro­du­ced by AMD. So it is no lon­ger adjus­ta­ble in AMD dri­ver and sup­po­sed to be locked now.
  • Voltage/frequency edi­tor is allowing you to adjust fre­quen­ci­es and vol­ta­ges inde­pendent­ly for all 3 V/F cur­ve points (or 3 P‑States), howe­ver AMD dri­ver and RVII archi­tec­tu­re put some restric­tions on the cur­ve edi­t­ing approach. So the cur­ve will be cor­rec­ted accord­ing to the fol­lowing limi­ta­ti­ons when you app­ly it: 
    • You can adjust the fre­quen­cy inde­pendent­ly for the first and the last point only. Midd­le point fre­quen­cy can­not be adjus­ted inde­pendent­ly, fre­quen­ci­es are always line­ar­ly inter­po­la­ted from the first point to the last point. So if you try to adjust fre­quen­cy for the midd­le point, it will be cor­rec­ted accord­ing to inter­po­la­ti­on rule men­tio­ned abo­ve right after app­ly­ing new settings
    • Unli­ke the fre­quen­ci­es, you can inde­pendent­ly adjust vol­ta­ges for all 3 points
    • You can­not set fre­quen­ci­es and vol­ta­ges below the mini­mum (which is rather strict and very clo­se to default). This puts some limi­ta­ti­ons on lower P‑State downclocking/downvolting
    • 2 GPU tem­pe­ra­tures dis­play­ed by MSI AB hard­ware moni­to­ring modu­le are map­ped to edge and junc­tion tem­pe­ra­tures. 4 dis­play­ed VRM tem­pe­ra­tures are map­ped to core VRM, SOC VRM and 2 memo­ry VRM sen­sors. AMD’s fan cur­ve is using junc­tion tem­pe­ra­tu­re for their fan speed adjus­t­ment. I’m not sure if it is real­ly good idea becau­se it is sky­ro­cke­ting to 100C area pret­ty rapidly when GPU is busy, that’s actual­ly direct rea­son why RVII coo­ling is so loud by default. Oppo­sing to that, MSI AB’s soft­ware fan cur­ve imple­men­ta­ti­on is still using tra­di­tio­nal edge tem­pe­ra­tu­re sen­sor. Pro­bab­ly I’ll add an abi­li­ty to select input ther­mal sen­sor for soft­ware fan cur­ve adjus­t­ment in future ver­si­ons, but honest­ly I’m not sure if it worth the efforts
    • Cur­r­ent­ly AMD’s own GPU usa­ge sen­sor is suf­fe­ring from pret­ty bad 0%->100%->0% fluc­tua­tions. Simi­lar issu­es affec­ted some old GPUs in the past but it is much worse on RVII now. I belie­ve that it is what they mean with “Per­for­mance metrics over­lay and Rade­on Watt­Man gau­ges may expe­ri­ence inac­cu­ra­te fluc­tua­ting rea­dings on AMD Rade­on VII” in the driver’s known issu­es, so the­re is a hope to see a fix from AMD in future. I remind you that it is pos­si­ble to get rid of such fluc­tua­tions via enab­ling uni­fied GPU usa­ge moni­to­ring in MSI AB pro­per­ties, howe­ver this opti­on depends on Direc­tX GPU usa­ge per­for­mance coun­ter and this coun­ter requi­res OS and dis­play dri­ver WDDM ver­si­ons to match. Cur­rent AMD dri­vers are tar­ge­ted to WDDM 2.5 OS (Octo­ber Update), so this opti­on will only help you if you have 1809 OS ver­si­on instal­led. Other­wi­se you’ll see zero GPU usa­ge all the time after enab­ling it.



MSI Afterbur­ner 4.6.0 Final (Guru3D)