Latest MSI Afterburner Betas & Updates

Page 1 of 19 12311 ... LastLast
  1. Cliff S's Avatar
    Posts : 22,295
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       01 Jul 2017 #1

    Latest MSI Afterburner Betas & Updates


    Click image for larger version. 

Name:	image.png 
Views:	103 
Size:	237.6 KB 
ID:	183393

    MSI Afterburner 4.5.0 RC
    Download page

    Changelog:


    Version 4.5.0


    • Minimum, average, maximum, 1% low and 0.1% low framerates are now displayed in On-Screen Display with special text formatting tags introduced by new RivaTuner Statistics Server. The tags are allowing On-Screen Display clients to display independent benchmark statistics simultaneously for multiple running 3D applications instead of displaying foreground 3D application statistics only
    • Improved default MSI Cyborg White skin. Monochrome on / off states of fan speed auto button were hardly identifiable before, they are more contrast now
    • Added power user oriented restore points system. Experienced users may use new /backup and /restore command line switches to create multiple named restore points containing full backups of MSI Afterburner’s settings (including hardware profiles and custom hardware monitoring plugin configurations) and restore settings from any previously created restore point if necessary
    • Improved hardware monitoring module:
      • Improved built-in performance profiler. Now you may enable “Show profiler panel” option is the context menu of hardware monitoring window to see an additional panel with detailed per-sensor polling statistics in hardware monitoring window status area. Polling statistics visualizes information about the slowest polled sensors with maximum polling time, so power users can easily identify problematic sensors eating most of CPU time on each polling period (e.g. abnormally slow GPU power sensor in some versions of NVIDIA drivers)
      • Improved correction formulas support. Now in addition to “x” variable representing current data source the formulas may also use sibling data sources. For example, you may use “x – “RAM Usage”” correction formula for “Pagefile usage” (commit charge) data source to subtract RAM usage from displayed value
      • Fixed incorrect tracking markers rendering on the graphs dynamically added to hardware monitoring module
      • Fixed incorrect tracking markers rendering when monitoring ring data buffer is full
      • Added experimental support for Intel i7 and i9 7XXXX LGA2066 CPUs
      • Added CPU package power monitoring for Intel CPUs
      • Minimum sampling interval for CPU usage calculation has been reduced from 1000ms to 100ms
      • Original RivaTuner’s monitoring history fragment selection and selected fragment processing functionality is back! Now you may hold <Shift> and press left mouse button on initial desired position in hardware monitoring window to begin fragment selection, then drag mouse cursor to desired final position and release left mouse button to select a fragment. The following functionality is available for selected fragments:

    • When the fragment is selected, minimum and maximum displayed values are estimated within selected fragment only. This feature can be used if you don’t need the global minimum and maximum values, estimated during whole monitoring session, and wish to see local minimum and maximum values estimated within some shorter period of time (e.g. during benchmark application runtime only).
    • When the fragment is selected you may use the context menu of any graph to set tracking marker into the local minimum or maximum position within the selection. This feature can be used to automate the process of identifying and visualizing the moments of reaching peak values (e.g. peak GPU temperature) on desired fragments
      • Improved monitoring plugins architecture:

    • Added plugin descriptions to plugins selection window
    • Added new SetupSource API function allowing you to configure the plugins. This function is allowing you to customize the plugins either globally from plugin selection window (e.g. configure whole list of data sources exported by each plugin) or customize desired data source only directly from corresponding graph properties window (e.g. change network download rate units from MB/s to KB/s). SetupSource function usage is demonstrated in SDK in updated AIDA64 and PerfCounter plugins
    • Added new GetHostAppProperty API function allowing the plugins to retrieve various properties from the host application (i.e. MSI Afterburner), e.g. retrieve GUI color scheme specific to the currently selected skin. GetHostAppProperty guru function usage is demonstrated in SDK in updated AIDA64 and PerfCounter plugins
      • Improved monitoring plugins:

    • Now the plugins store user customized and built-in default configurations in separate files, so your custom plugin settings won’t be lost on new version install
    • Added configuration GUI for AIDA64, HwInfo and PerfCounter plugins. Each plugin’s user interface is allowing you to edit the list of sensors exported by each plugin, export full list of available sensors to a text file, customize each sensor’s properties or reset plugin settings to defaults
    • Improved PerfCounter plugin:
      • Added support for performance counters with non-localized names (e.g. “GPU Engine” under Windows Fall Creators Update)
      • Added support for dynamic data sources. Dynamic data sources are not validated during creation, such sources are allowed to export no data until some condition is met (e.g. “CPU usage” performance counters specific to some target process export data only when the process is running)

    • Improved SMART plugin:
      • Added airflow temperature SMART attribute support for Intel/Samsung SSDs.

    • Added new CPU plugin:
      • The plugin fully duplicates MSI Afterburner’s built-in CPU temperature monitoring implementation (with the only exception of AMD Ryzen codepath, which cannot be open sourced due to NDA) and shows third party plugin developers how to implement low-level CPU specific sensors in plugins using CPU MSR registers and PCI configuration space access API

    • Added new GPU plugin:
      • The plugin shows third party developers how to extend MSI Afterburner’s GPU monitoring functionality and implement own GPU specific sensors in plugins using GPU enumeration and identification API. The plugin is demonstrating implementation of D3DKMT GPU performance counters providing unified vendor agnostic per-engine GPU usage, dedicated and shared memory usage monitoring

    • Fixed issue in context help system, which could cause the tooltip to flicker when it was displayed below mouse cursor
    • RivaTuner Statistics Server has been upgraded to v7.1.0



    RTSS v7.2.0: Guru3D RTSS Rivatuner Statistics Server Download v7.2.0 Final


    • Added On-Screen Display performance profiler. Power users may enable it to measure and visualize CPU and GPU performance overhead added by On-Screen Display rendering. Two performance profiling modes are available:
      • Compact mode provides basic and the most important CPU prepare (On-Screen Display hypertext formatting, parsing and tessellation), CPU rendering and total CPU times, as well as GPU rendering time (currently supported for Direct3D9+ and OpenGL applications only)
      • Full mode provides additional and more detailed per-stage CPU times.

    • Improved built-in framerate limiter:
      • Fractional framerate limit adjustment functionality is no longer power user oriented, now you may specify fractional limit directly from GUI
      • Now you may click “Framerate limit” caption to switch framerate limiter to alternate “Frametime limit” mode. New mode allows you to specify the limit directly as a target frametime with 1 microsecond precision
      • Added alternate framerate limiting mode, based on synchronization with display rasterizer position. Now you may synchronize the framerate to up to two independent scanline indices per refresh interval. Combining with power user configurable scanline wait timeout and graphics pipeline flushing options, those settings provide experienced users vendor agnostic ultra low input lag adaptive VSync, half VSync or double VSync functionality on any hardware
      • Added power user oriented idle framerate limiting mode. Unlike traditional framerate limiting mode, idle framerate limiting mode is only affecting inactive 3D applications running in background. Idle framerate limit is specified as a target frametime with 1 microsecond precision. Idle framerate limiting mode helps to reduce power consumption when you minimize some heavy 3D applications and switch to other processes

    • Various On-Screen Display optimizations and improvements:
      • Added adjustable minimum refresh period for On-Screen Display renderer. The period is set to 10 milliseconds by default, so now the On-Screen Display is not allowed to be refreshed more frequently than 100 times per second. Such implementation allows keeping smooth animation when On-Screen Display contents are being updated on each frame (e.g. when displaying realtime frametime graph) without wasting too much CPU time on it
      • Added alternate GPU copy based Vector2D On-Screen Display rendering mode implementation for Direct3D1x applications. New mode provides up to 5x Vector2D performance improvement on NVIDIA graphics cards, however it is disabled on AMD hardware due to slow implementation of CopySubresourceRegion in AMD display drivers
      • Vector2D rendering mode is now forcibly disabled in Vulkan applications on AMD graphics cards due to insanely slow implementation of vkCmdClearAttachments in AMD display drivers
      • Revamped geometry batching and vertex buffer usage strategy in pure Direct3D12 On-Screen Display renderer (currently used in Halo Wars 2 only)
      • Added Vector2D rendering mode support to pure Direct3D12 On-Screen Display renderer
      • Optimized On-Screen Display hypertext parsing and tessellation implementation
      • Optimized state changes in OpenGL On-Screen Display rendering guru implementation
      • Improved implementation of On-Screen Display rendering from separate OpenGL context (profile compatibility switch used in certain OpenGL applications, e.g. Pyre) on AMD graphics cards
      • Optimized state changes in Direct3D1x On-Screen Display rendering implementation
      • Solid rectangles and line primitives in Direct3D8 and Direct3D9 On-Screen Display rendering implementations are now rendered from vertex buffer instead of user memory
      • Improved OpenGL framebuffer dimensions detection when framebuffer coordinate space is selected
      • Increased static vertex buffer size for Vulkan and pure Direct3D12 renders to increase amount of primitives rendered in On-Screen Display in a single pass

    • Improved desktop duplication based desktop video capture implementation ( Windows 8 and newer OS versions):
      • Now desktop video recording sessions do not stop on display mode switch or on switch to exclusive fullscreen mode. Such approach allows you to start capturing video on desktop then launch some 3D application and create a video file containing both desktop and 3D application’s video streams
      • Improved video capture API allows video capture frontend applications (e.g. MSI Afterburner) to force desktop or 3D application video capture modes in addition to default mixed desktop/3D application capture mode
      • Now desktop capture is using multhithreaded active busy-wait loop frame capture instead of timer driven frame capture in order to improve frame timing precision and resulting video smoothness. The previous timer driven frame capture can be enabled via configuration file if necessary
      • Decreased desktop duplication timeouts in order to improve RivaTuner Statistics Server GUI response time under certain conditions during desktop videocapture sessions in timer driven frame capture mode

    • Improved SDK:
      • Improved RTSSFrametimePipeSample sample. Now the sample demonstrates frametime pipe connection for applications running with both full administrative and limited user rights
      • Improved NVENC plugin. Added NVIDIA 416.xx drivers family support. The plugin was recompiled with newer NVENC encoder API headers, because NVIDIA stopped supporting legacy v4 NVENC API in release 416 and newer series drivers. Due to this change NVENC plugin no longer supports pre-release 358 NVIDIA drivers

    • Fixed On-Screen Display rendering in wrong colors when Vector2D mode is selected and Direct3D1x applications use 10-bit framebuffer
    • Fixed Vulkan fence synchronization issue, which could cause GPU-limited Vulkan applications to hang due to attempt to reuse busy command buffer
    • Active busy-wait loop in the framerate limiter module is now forcibly interrupted during unloading the hooks library to minimize the risk of deadlocking 3D application when dynamically closing RivaTuner Statistics Server during 3D application runtime
    • Improved CBT hooks uninstallation routine to minimize the risk of deadlocking 3D application when dynamically closing RivaTuner Statistics Server during 3D application runtime
    • Improved validation in OpenGL On-Screen Display rendering routine to minimize the risk of crashing OpenGL applications
    • Changed OpenGL cleanup routines to improve compatibility with OpenGL applications using multiple rendering contexts (e.g. GPU Caps Viewer)
    • Improved synchronization in 32-bit API hook uninstallation routines
    • Added timeout to API hooks injection in CBT hook handler. The timeout is aimed to reduce injection related CPU overhead on some systems, related to high mouse polling rate combined with keyboard/mouse hooks installed by third party applications
    • Interoperability D3D10 page flips on some systems are now filtered by framerate calculation module in OpenGL/Vulkan applications
    • Hook engine is now using alternate double jump x64 hook trampoline to improve compatibility with third party 64-bit On-Screen Display applications
    • Added compatibility profile switch for hooking IDXGISwapChain::ResizeBuffers via VTable instead of hotpatching
    • Added hook epilogs support to 32-bit VTable hook handler
    • Fixed instance checking implementation in 64-bit RTSSHooksLoader and EncoderServer helper applications
    • Added exclusion profile for Forza Horizon 4. Please take a note that On-Screen Display is currently not supported in this game due to its protective system limitations
    • Forcible graphics and compute queues synchronization is now disabled by default for Vulkan applications presenting frames from compute queue (AMD Vulkan rendering codepaths in DOOM and Wolfenstein II : The New Colossus). Due to this change, On-Screen Display will be invisible in those games on such platforms by default. Experienced users, understanding and accepting that On-Screen Display rendering will cause performance penalty, may re-enable it with PresentFromCompute profile switch
    • Added tri-state skinned buttons support in the skin engine
    • Updated profiles list



    Additional Link: Add a UWP exclusion to MSI Afterburner's OSD
    Last edited by Cliff S; 30 Oct 2018 at 10:34.
      My ComputersSystem Spec

  2.    01 Jul 2017 #2

    I believe with version (the beta 12 at least) you can enable ingame graphing for RTSS OSD . Im stil on 4.3 till i have time to fiddle with the new version
      My ComputerSystem Spec

  3. Cliff S's Avatar
    Posts : 22,295
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
    Thread Starter
       21 Sep 2017 #3

    Post from unwinder on Monday:
    Hehe, I'm rather satifsied with new beta development progress and beta 17 with new functionality is around a corner Small preview of upcoming functionality:

    RTSS 6.7.0 beta 1 | Page 36 | guru3D Forums


    And from yesterday:
    Hehe we go, one more preview of new beta functionality. New task scheduler and alarm thresholds in action:
    RTSS 6.7.0 beta 1 | Page 36 | guru3D Forums
      My ComputersSystem Spec

  4.    23 Sep 2017 #4

    nice :) ill have to have a play with it myself :)
      My ComputerSystem Spec

  5. Cliff S's Avatar
    Posts : 22,295
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
    Thread Starter
       23 Sep 2017 #5

    Some important security information that was posted from Unwinder(the developer of RTSS Riva Tuner Statistics Server):

    From yesterday 22-Sep-17
    And now some sad news. MSI digital signature, which we used to locally sign RTSS betas here (and this way make it BattleEye and EAC friendly) just expired, which means that it can no longer be used to sign new RTSS beta builds. Renewed MSI signature is more secure and due to that is cannot be used to sign anything outside MSI HQ, so I cannot locally sign future RTSS betas with it too. Building any beta (which I release on daily basis sometimes during testing) inside MSI is not an option too. So newer beta versions will not work with EAC and BattleEye enabled games, but at least we'll be able to sign official RTSS releases inside MSI.
    We're still thinking how to improve the process, but be ready to the worst case (i.e. only official releases signed) too.
    RTSS 6.7.0 beta 1 | Page 37 | guru3D Forums

    Then from today 23-Sep-17
    Guys, a few posts above I mentioned sad code signing related problems caused by expired MSI code signing certificate. I'm happy to declare that we seem to have found a solution. While MSI are still actively trying to get it possible for me to use their renewed signature here, the final result and ETA are rather unpredictable. I wanted to cover our backs and avoid delaying new beta launch and making you wait because of it, so I decided to purchase my own alternate code signing certificate and use it in meanwhile. It was a tough weekend, but I'd really like to thank StartCom code signing certificate provider for their extremely fast service, the process of personal verification and issuing the certificate took just about 24 hours, normally it takes much much much much longer. So since the next beta I'll be signing RTSS with it my personal signature instead of MSI signature. Yes, it will take some time (weeks?) for EAC and BattleEye to adopt to and whitelist new signature, but once it is done - everything should be smooth with future RTSS betas.
    RTSS 6.7.0 beta 1 | Page 37 | guru3D Forums
      My ComputersSystem Spec

  6. Dude's Avatar
    Posts : 12,538
    Windows 10 Pro X64
       23 Sep 2017 #6

    Thanks for sharing Cliff, I have been following that and wondered where it would go
      My ComputerSystem Spec

  7. Cliff S's Avatar
    Posts : 22,295
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
    Thread Starter
       25 Sep 2017 #7

    4.4.0 beta 17 up for grabs: RTSS 6.7.0 beta 1 | Page 38 | guru3D Forums

    The major key features of new release are:

    - Hardware monitoring plugins support, now you can monitor more data out of box and can create your own sensors and share your work with community
    - OSD layout editor. Now you can customize modern OSD layout in details
    - Improved programmable critical thresholds in hardware monitoring module. Now you can configure you system to play sound alarm or perform emergency actions (e.g. downclock GPU, boost fan speed or even power down the system) when some monitored parameter reach critical value



    Full changes list (comparing to beta 16) includes:
    - Added thermal offsets for CPU temperatures displayed on AMD Threadripper CPU family
    - Original RivaTuner’s task scheduler functionality is back! Now you may define optional minimum and (or) maximum thresholds for any graph in hardware monitor module to track the most critical hardware health parameters, to be notified on reaching a critical threshold and to program some emergency actions (e.g. system shutdown) to be performed in this case:
    o User defined thresholds are displayed on each graph to allow you to control each parameter safety zone visually
    o When the threshold is reached blinking warning icon is displayed in top left corner of monitoring window and in Logitech keyboard LCD if graph LCD display mode is selected
    o When the threshold is reached you can see the name of graph triggering the alarm in hardware monitoring status line
    o When the threshold is reached background of the graph triggering the alarm is highlighted with color to allow you to identify it visually
    o When modern On-Screen Display layout is selected, parameters triggering the alarm are highlighted by color in On-Screen Display to allow you to identify it easily
    o You may enable option alarm sound notification to be played when the threshold is reached
    o You may configure MSI Afterburner to launch any external application when the threshold is reached. This feature allows you to implement many different scenarios, e.g. perform emergency system shutdown or apply safe profile with reduced overclocking, maximized fan speed etc. In addition to selecting any custom external applications, built-in predefined applications browser allows you to select some common typical usage scenarios, such as command line based MSI Afterburner profile activation or system shutdown
    - Original RivaTuner’s user extendable hardware monitoring plugins architecture is back! Now you may extend the list of hardware monitoring data sources with built-in or third party plugin modules, develop your own plugins to provide support for custom hardware sensors and share your work with community, and many more:
    o The plugins can use full set of MSI Afterburner’s low-level hardware access functionality: enumerate GPUs, access GPU registers, enumerate GPU I2C buses and access I2C devices, access CPU MSR registers, access IO ports and PCI configuration space registers. This way you can easily create your own plugins providing hardware monitoring functionality for any custom hardware. You can also create the plugins for importing OS-specific or third-party software specific performance counters into MSI Afterburner
    o Open source SDK, demonstrating hardware monitoring plugins development principles to third party programmers. The SDK includes the following open source plugins:
    + SMART.dll – demonstrates HDD SMART attributes readback and HDD temperature monitoring
    + PerfCounter.dll – demonstrates the principles of importing native OS performance counters into MSI Afterburner. The list of imported performance counters includes but not limited to hard drive usage, hard disk read and write rates, free disk space on system partition, network download and upload rates. You may also add any other performance counter visible to OS (e.g. disk queue size or some specific process CPU usage) via editing the plugin configuration file
    + AIDA64.dll – demonstrates the principles of importing sensors from AIDA64 application via shared memory interface. The list of imported performance counters includes but not limited to motherboard temperature, CPU socket temperature, CPU fan speed, CPU voltage, CPU package power, +3.3V, +5V and +12V voltages. You may also add any other sensors available in AIDA64 via editing the plugin configuration file
    + HwInfo.dll - imports sensors from HWiNFO32/64 application via shared memory interface. The list of imported performance counters includes but not limited to motherboard temperature, CPU socket temperature, CPU fan speed, CPU voltage, CPU package power, +3.3V, +5V and +12V voltages. You may also add any other sensors available in HWiNFO32/64 via editing the plugin configuration file. Please take a not that the plugin is not open source per HWiNFO developer request
    - Added ability to define a hotkey for hardware monitoring logging start and stop
    - Now the path to hardware monitoring logs supports macro names:
    o You may use new %ABDir% macro in the path to specify relative path to current MSI Afterburner installation directory. This macro allows you to use logging if you are using portal installation and start MSI Afterburner from removable drive
    o You may use new %Time% macro in the path to make hardware monitoring sessions to be stored in unique timestamp-named log files instead of single multi-session log file
    - Changed hardware monitoring properties layout, the controls have been reordered a bit to give more compact and convenient look to the properties
    - Improved multiple selection functionality:
    o Now you may hold <Shift> key when clicking a checkmark next to a graph name in the list of active hardware monitoring graphs to enable or disable all graphs at once
    o Now you may hold <Shift> or <Ctrl> keys to select multiple items in the list of active hardware monitoring graphs. The following functionality is available for multiple selected hardware monitoring graphs:
    + When multiple hardware monitoring graphs are selected, you may hold <Ctrl> key when changing graph specific On-Screen Display, Logitech keyboard LCD and tray icon related properties (e.g. “Show in On-Screen Display” property) to change it synchronically for all selected graphs
    + When multiple hardware monitoring graphs are selected, you may hold <Ctrl> when clicking a checkmark next to a graph name in the list of active hardware monitoring graphs to enable or disable all selected graphs at once
    - RTSS updated to version 7.0.0 beta 29. RTSS related changes were documented before.
      My ComputersSystem Spec

  8. Dude's Avatar
    Posts : 12,538
    Windows 10 Pro X64
       26 Sep 2017 #8

    Thanks for the heads up @Cliff S

    Last edited by Dude; 26 Sep 2017 at 18:48.
      My ComputerSystem Spec

  9. Cliff S's Avatar
    Posts : 22,295
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
    Thread Starter
       02 Oct 2017 #9

    New Afterburner beta
    MSI Afterburner 4.4.0 beta 18
    See first post for download link and changelog
      My ComputersSystem Spec


  10. Posts : 15
    Windows 10 and Mac OS X
       03 Oct 2017 #10

    Thank you thank you thank you! After 5 hours of morning work getting MSI Afterburner to run on Win 64 professional, my new gaming rig running Ryzen finally this version runs! Thank you once again.
      My ComputerSystem Spec


 
Page 1 of 19 12311 ... LastLast

Related Threads
Hello everyone, I've got two bsod this week caused by ntoskrnl.exe so I followed this guide to find which driver is: WinDBG - The Basics for Debugging Crash Dumps in Windows 10 Windows 10 BSOD Tutorials After using the !analyze -v command it...
MSI Afterburner 4.3 Final is out in PC Custom Builds and Overclocking
108091 MSI Afterburner 4.3.0 Final/Stable Download
Latest Win10 Updates in Windows Updates and Activation
I got KB3176936 on 8/24 and the Regedit edit to PaintDesktop quit working even though it was correctly set. I got KB3176938 today and PaintDesktop also will not work even though set as directed. I have a reason to have it showing, more than 1...
Latest Win 10 Updates !!! in Windows Updates and Activation
Anyone had fun today with 10 updates? They went into my pc this morning and since then its taken me an hour and a half to get to the point where I can type this. The pc booted up, no image. Had to reset to default Samsung flat screen to get...
Viewing Latest Updates in Windows Updates and Activation
How can you view what updates have been installed in Windows 10? If something goes wrong or doesn't work correctly, I would like to know what caused it.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 14:39.
Find Us