| Page 1 of 1 |
|
|
|
| Back to top |
|
 |
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
|
| Back to top |
|
|
|
|
 Posted: Fri, 11th Oct 2013 13:05 Post subject: |
|
|
No, that B is the CPU stepping (which is something else). The core stepping is G0 (old model would be B3). My problem is that i dont know how to change the tjmax in msi afterburner
ASUS TUF B550M-PLUS | RYZEN 5600x | RTX 3060TI | 16GB DDR4
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
|
|
| Posted: Fri, 11th Oct 2013 20:03 Post subject: |
|
|
with my case closed aida was showing 44-idle 64-gaming while afterburner is showing 54-idle 74-gaming. way too high but fuck it i'll just stop worrying. worst case scenario my cpu will fry in a year or two and i'll just buy another one as its only 60-70$ anyway
ASUS TUF B550M-PLUS | RYZEN 5600x | RTX 3060TI | 16GB DDR4
|
|
| Back to top |
|
|
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
| Posted: Wed, 27th May 2015 09:58 Post subject: |
|
|
4.1.1 is out.
http://forums.guru3d.com/showthread.php?t=399426 / http://www.guru3d.com/files-details/msi-afterburner-beta-download.html (Scroll down to the bottom for the download link to 4.1.1 final.)
| Quote: |
Revision history - Version 4.1.1
Added core voltage control for reference design NVIDIA GeForce GTX TITAN X series graphics cards
Added core voltage control for reference design NVIDIA GeForce GTX 980 Ti series graphics cards
Now core voltage control via NCP4206 is unlocked on reference design NVIDIA GeForce GTX 690, NVIDIA GeForce GTX 780 and
NVIDIA GeForce GTX TITAN series graphics cards when extended MSI voltage control mode is selected
Added new third party voltage control mode. Traditionally we provided voltage control on reference design graphics cards or on custom design MSI graphics cards only. However, rich set of PWM controllers supported by MSI Afterburner core allows implementing voltage control on many third party custom design graphics cards as well. With this version we introduce original concept of user extendable voltage control mode, allowing experienced users to get access to programmable MSI Afterburner core, get access to full range of voltage controllers supported by it, create custom hardware database and program MSI Afterburner to provide voltage control on many third party custom design graphics cards. Third party voltage control mode requires populating and downloading third party hardware database, please visit MSI Afterburner discussion forums to help adding your custom design cards to the database or download the latest database version.
Fixed bug causing application to crash when “layered with alpha” skin composition mode is selected, application is minimized to system tray and properties are accessed via the context menu of detached monitoring window
Improved hardware monitoring module:
Added negative temperatures monitoring support for NVIDIA GPUs
Fixed extended CPU family and model detection to address issue with incorrect maximum junction temperature (Tjmax) detection on some Intel CPUs
Now power users can override the maximum junction temperature (Tjmax) via configuration file if necessary
Added temperature monitoring for AMD Family 10h – 16h micro architecture CPUs. Please take a note that this functionality is currently experimental and disabled by default. Power users can unlock AMD CPU temperature monitoring via [CPUHAL] section in the configuration file if necessary
Added correction formulas support. Now you can apply a custom correction formula to any data source in hardware monitoring module. Correction formulas can be useful to apply temperature offsets to custom temperature sensors if necessary (e.g. set formula to “x+20”), display effective memory clock instead of base clock (e.g. set formula to “x*2”), display per-GPU memory usage instead of total memory usage on Crossfire systems (e.g. set formula to “x/2”) and many, many more.
Hardware Monitoring Log file format has been upgraded to v1.5 to provide correction formulas support.
Added “CPU load” graph to multicore CPUs. The graph is displaying the average CPU load across all CPU cores.
Added “CPU temperature” graph to thermal monitoring capable multicore CPUs. The graph is displaying the maximum CPU temperature across all CPU cores
o Added connection retry counter to Logitech LCD monitoring module. Now MSI Afterburner stop trying to connect to Logitech LCD after some failed connection attempts instead of trying to connect to it in endless loop. Retry counter implementation is aimed to bypass the problem with GDI resource leak in Logitech LCD API, which could cause application to crash after some period of time when output to LCD is enabled on the system with no Logitech LCD connected to it
Added dynamic output format for min / max limits displayed on the graphs. Now MSI Afterburner uses integer output format for limits if the range between minimum and maximum limits is greater than 1, otherwise it uses floating point output format
Improved skin engine:
Added support for altered USF skins obfuscation scheme used in most recent versions of third party overclocking tools
Drastically reduced load time for obfuscated USF skin files (*.UXF). Now MSI Afterburner open obfuscated skin files roughly 10 times faster than the previous version
Reduced skinned GUI initialization time due to cached access to the skin header
Added support for negative GPU temperature indicators in all skins supplied with application
Multimedia timer resolution is no longer hardcoded to 10ms. The resolution is now adjustable and set to 16ms by default to reduce timer interrupts related CPU load at the cost of losing some smoothness in GUI animation. Power users can override timer resolution via the configuration file if necessary
Updated kernel mode driver provides new IOCTLs for safe access to PCI bus required for temperature monitoring on AMD CPUs
|
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 27th May 2015 10:12 Post subject: |
|
|
Added negative temperatures monitoring support for NVIDIA GPUs 
Fixed extended CPU family and model detection to address issue with incorrect maximum junction temperature (Tjmax) detection on some Intel CPUs 
Now power users can override the maximum junction temperature (Tjmax) via configuration file if necessary
| Lutzifer wrote: | | and yes, mine is only average |
|
|
| Back to top |
|
|
|
|
| Posted: Mon, 21st Sep 2015 01:38 Post subject: |
|
|
Now that there are *some* DX12 titles out (not necessarily utilising DX12 features, but definitely using the D3D12 renderer) I hope Afterburner/RTSS gets updated to support the OSD soon. EVGA Precision supports DX12 now :\
|
|
| Back to top |
|
|
|
|
| Posted: Mon, 21st Sep 2015 13:42 Post subject: |
|
|
| sabin1981 wrote: | | Now that there are *some* DX12 titles out (not necessarily utilising DX12 features, but definitely using the D3D12 renderer) I hope Afterburner/RTSS gets updated to support the OSD soon. EVGA Precision supports DX12 now :\ |
Not many people who value such info and are avid gamers use one screen anymore, I see no benefit for OSD other than it can cause lag and issues in gaming when its much easier to just have the graphs out on part of another screen.
OSD along the likes of overdraw with steam ui etc have been more a hinderance to gaming than a helpful tool. |
|
| Back to top |
|
|
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
| Posted: Mon, 21st Sep 2015 15:48 Post subject: |
|
|
|
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
| Posted: Mon, 21st Sep 2015 16:09 Post subject: |
|
|
I forgot about one other thing, it could be that he's still waiting on MSI to provide him with new hardware so he can add official support for the Fury (And now also Nano) GPU's before releasing the next version of the Afterburner program, last I heard MSI hadn't sent or didn't want to send him the requested hardware which I guess was due to the low supply amount available, it's still not available in any larger quantities from shops here and the Nano is probably rarer still.
EDIT: Looks like he might be active again, there's a few posts from around the 7th to 14th September though nothing new about a upcoming release.
|
|
| Back to top |
|
|
Frant
King's Bounty
Posts: 24592
Location: Your Mom
|
| Posted: Mon, 21st Sep 2015 17:04 Post subject: |
|
|
Throughout the years he's had a googolplex of repeated simple nonsense questions that are already answered in nailed threads and the FAQ etc. with people attacking him over and over again. That made him quite sick of dealing with the support side of MSI Afterburner (which he did freely).
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn!
"The sky was the color of a TV tuned to a dead station" - Neuromancer
|
|
| Back to top |
|
|
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
| Posted: Mon, 7th Dec 2015 14:12 Post subject: |
|
|
4.2.0
http://www.guru3d.com/news_story/download_msi_afterburner_4_2.html
| Quote: |
Revision history for MSI Afterburner v4.2.0:
• Added AMD Fiji graphics processors family support
• Hardware abstraction layer architecture has been revamped to allow implementation of voltage control via direct access to GPU on-die voltage controllers (e.g. AMD Fiji SMC) in addition to previously supported external voltage controllers connected to GPU via I2C bus. Please take a note that direct access to AMD SMC from multiple simultaneously running hardware monitoring applications can be unsafe and result in collisions, so similar to I2C access synchronization we introduce global namespace synchronization mutex “Access_ATI_SMC” as SMC access synchronization standard. Other developers are strongly suggested to use it during accessing AMD GPU SMC in order to provide collision free hardware monitoring
• Added core voltage control for reference design AMD RADEON R9 Fury / Nano series cards with on-die SMC voltage controller
• Added unofficial overclocking support for PowerPlay7 capable graphics cards (AMD Tonga and newer graphics processors family). Please take a note that unofficial overclocking mode with completely disabled PowerPlay is currently not supported for PowerPlay7 capable hardware
• Added version detection for AMD Radeon Software Crimson edition. Please take a note that new AMD Radeon Software versioning scheme is not backward compatible so now Catalyst version can be reported improperly if you reinstall older versions of Catalyst drivers on top of AMD Radeon Software Crimson edition without cleaning the registry up. Until the issue is addressed inside AMD Radeon Software Crimson edition installer, MSI Afterburner is providing compatibility switch “LegacyDriverDetection” in the configuration file allowing you to use legacy driver version detection mechanism if you’re rolling back to legacy Catalyst drivers after AMD Radeon Software Crimson edition drivers
• GPU usage monitoring filtering algorithms, aimed to filter GPU usage monitoring artifacts in AMD ADL API on AMD Sea Islands GPU family are now disabled by default. Filtering algorithms can still be enabled by power users via configuration file if necessary
• Added core, memory and auxiliary PEXVDD voltage control for custom design MSI GTX980Ti Lightning series graphics cards with IR3595A+IR3567B voltage regulators
• Added memory and VRM temperature monitoring for custom design MSI GTX980Ti Lightning series graphics cards with NCT7511Y thermal sensors
• Now SDK includes detailed documentation for third party hardware database format, allowing experienced users to add voltage control support for custom design non-MSI graphics cards
• Temperature monitoring for AMD Family 10h – 16h micro architecture CPUs is no longer experimental. Now thermal monitoring on such CPUs is unlocked by default
• Slightly altered VRAM usage monitoring implementation for AMD and Intel graphics cards. Now total resident bytes are being displayed as VRAM usage instead of total committed bytes, and allocated blocks are no longer being rounded to 1MB boundary per block when calculating a total value
• Improved skin engine. Added support for altered USF skins obfuscation scheme used in most recent versions of third party overclocking tools
• Added Brazilian Portuguese localization
• RivaTuner Statistics Server has been upgraded to v6.4.1
Revision history for RTSS v6.4.1:
• Added On-Screen Display profile for Assassin's Creed Syndicate
• Added On-Screen Display profile for Just Cause 3
• Starting desktop recording sessions with “Use dedicated encoder server” option enabled no longer results in blocking subsequent in-game recording sessions until restarting the application
• Fixed inverted state of “Low-level encoding” option in NVIDIA NVENC H.264 encoder plugin
• Improved AMD AMF VCE H.264 encoder plugin:
o Unlocked encoding in > 1080p resolutions for VCE 3.0 capable graphics cards (AMD Tonga and Fiji GPUs)
o Added option for selecting host, Direct3D9 or Direct3D11 memory type for encoder. It is recommended to leave default Direct3D9 memory type for everyday usage and select the rest types for performance testing or troubleshooting scenarios only
• Added Brazilian Portuguese localization
• Updated profiles list
Revision history for RTSS v6.4.0:
- Fixed On-Screen Display rendering in Direct3D9Ex applications compiled with Windows 10 compatibility flags (e.g. recent update of
World of Tanks)
- Fixed On-Screen Display rendering in 64-bit Direct3D9 applications using additional swapchains (e.g. DOTA 2 Reborn)
- Fixed crashing in Direct3D10 and Direct3D11 applications when FCAT indicator is enabled in conjunction with vector 2D On-Screen
Display rendering mode
- Improved thread safety of delayed injection implementation
- Added On-Screen Display profiles for Batman : Arkham Knight and Daylight to provide correct On-Screen Display rendering on
NVIDIA graphics cards when advanced NVIDIA GameWorks visual effects are enabled
- Added On-Screen Display profile for 64-bit version of StarCraft II
- Improved NVIDIA NVENC H.264 encoder plugin:
o Increased upper adjustable bitrate limit to 130 Mbps for NVIDIA Maxwell graphics processors family
o Added new option allowing you to disable low-latency encoding if necessary. Low-latency encoding mode is aimed for
streaming and it configures NVENC hardware/software infrastructure to compress frames as fast as it is possible. So the
driver may re-balance GPU load in graphics intensive applications in order to achieve as low compression latency as it is
possible. You may disable low-latency encoding to prevent the driver from balancing GPU load and allow it to sacrifice
compression latency under high GPU load
- Added AMD AMF VCE H.264 encoder plugin:
o Considering that AMD officially dropped OpenEncode hardware acceleration API support since Catalyst 15.7, new plugin
uses alternate AMD AMF hardware acceleration API. New plugin it is aimed to replace the previous AMD VCE H.264
plugin, based on deprecated AMD OpenEncode API. However, the previous OpenEncode API based plugin is still included
in distributive and can be use for performance testing or solving compatibility issues on pre-Catalyst 15.7 drivers. Please
take a note that AMD AMF libraries require installing Microsoft Visual C++ 2013 runtime libraries, those libraries are not
included in distributive and must be downloaded and installed separately
- Source code of all hardware accelerated H.264 encoder plugins is now included in RivaTuner Statictics Server SDK. Now you may
create your own hardware accelerated plugins or modify existing plugins if you wish to create a custom build with deeper
customization of hardware encoder
- Improved encoder plugin loader
- Updated profiles list
|
(From http://forums.guru3d.com/showthread.php?t=404400 and http://forums.guru3d.com/showthread.php?t=403556 )
|
|
| Back to top |
|
|
3E74
Posts: 2559
Location: feels wrong
|
| Posted: Mon, 7th Dec 2015 17:51 Post subject: |
|
|
nice..
THX Jonas for teh heads up..
i totally forgot about teh new version 
..:: Life - A sexually transmitted disease which always ends in death. There is currently no known cure::.. 
|
|
| Back to top |
|
|
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
| Posted: Mon, 7th Dec 2015 18:18 Post subject: |
|
|
It's a very handy utility though I don't use the overclock functionality much, mostly monitoring certain stats and displaying framerate plus taking screenshots and such.
EVGA's Precision X going by the changelog has a few more features but they have a development team whereas Unwinder is a single person co-operating with MSI so it's not exactly fair to compare the two I suppose.
http://www.evga.com/precision/
(DX12 support, supported the 980Ti since June and a few other things but it only works on supported Nvidia GPU's.)
|
|
| Back to top |
|
|
Roach_666
Posts: 1299
Location: Hell in its Alpha Build
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
Roach_666
Posts: 1299
Location: Hell in its Alpha Build
|
|
| Back to top |
|
|
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
| Posted: Fri, 2nd Sep 2016 15:36 Post subject: |
|
|
http://www.guru3d.com/news_story/download_msi_afterburner_4_3_beta_14.html
http://forums.guru3d.com/showthread.php?t=409692 / http://forums.guru3d.com/showthread.php?t=409693
4.3.0 public beta.
http://www.guru3d.com/files-details/msi-afterburner-beta-download.html
Changelog for Afterburner:
| Quote: |
Revision history Version 4.3.0 Beta 14
Added AMD Ellesmere and Baffin graphics processors families support
Added Overdrive N (Overdrive 7) technology support for AMD Polaris architecture based graphics cards
Added core voltage control for reference design AMD RADEON RX 460, AMD RADEON RX 470 and AMD RADEON RX 480 series cards with on-die SMC voltage controller
Added memory controller usage graph to hardware monitoring module for AMD graphics cards. Currently memory controller usage monitoring is implemented for AMD Ellesmere and Baffin graphics processors families only
Added GPU power draw graph to hardware monitoring module for AMD graphics cards. Currently GPU power draw monitoring is implemented for AMD Ellesmere and Baffin graphics processors families only
Added “Erase autosaved startup settings” option to “AMD compatibility properties” section in “General” tab. Starting from AMD Crimson drivers family, the driver is automatically saving hardware settings (e.g. overclocking or fan control settings) in the registry and apply it at Windows startup. It makes settings of any third party hardware overclocking tool virtually permanent, meaning that applied settings stay in the system even after rebooting or powering down the system. However, such implementation is unsafe and even potentially dangerous, because you're no longer able to undo unsafe overclocking with system reboot or even driver reinstall. To prevent such situations, MSI Afterburner can now optionally erase AMD driver's autosaved startup settings after applying new settings to hardware
Added GPU Boost 3.0 technology support for NVIDIA Pascal graphics cards:
Added percent based overvoltage support.
Added voltage/frequency curve customization support. You may use traditional core clock slider on NVIDIA GeForce GTX 1070 and 1080 graphics cards to apply fixed offset to all voltage/frequency curve points as well as use brand new flexible voltage/frequency curve editor window for more precise per-point curve adjustment. The editor window can be activated either with <Voltage/frequency curve editor> button in the main application window or with <Ctrl> + <F> keyboard shortcut and it provides you the following features: You may independently adjust clock frequency offset for each point with mouse cursor or <Up> / <Down> keys
You may hold <Ctrl> key to set anchor and fix clock frequency offset in minimum/maximum voltage point and adjust the offset of any other point with mouse to linearly interpolate the offsets between the anchor and adjustment points
You may hold <Shift> key while adjusting the offset of any point with mouse to apply the same fixed offset to all points. That’s equal to adjusting the offset with the slider in main application window.
You may press <Ctrl> + <D> to reset offsets for all points You may switch between traditional core clock control slider in the main window and voltage/frequency curve editor window to see how they affect each other in real-time
You may press <L> after selecting any point on the curve with mouse cursor to disable GPU dynamic voltage/frequency adjustment and lock the voltage and core clock frequency to a state defined by the target point. This feature allows you to test graphics card stability independently for each voltage/frequency point of the curve using real 3D applications or any stress test of your choice. In addition to stability testing usage scenario, MSI Afterburner allows you to save a curve with locked point setting to a profile, so you may easily switch between dynamic voltage/frequency management and fixed voltage/frequency settings in realtime (e.g. to achieve the maximum performance during benchmarking). Please take a note that fixed voltage and frequency settings do not allow you to disable power and thermal throttling
Increased default maximum limits for “Core clock”, “Memory clock” and “Memory usage” graphs to improve graphs readability on NVIDIA Pascal series graphics cards
Added configuration file switch, allowing you to toggle the source for “Power” graph on NVIDIA graphics cards. Normalized total power draw (i.e. normalized value from multiple power sensors installed on the graphics card) is selected by default per NVIDIA recommendation, however you can configure MSI Afterburner to display power draw from GPU sensor only
Improved representation of performance limits graphs for NVIDIA graphics cards per NVIDIA recommendations:
“Voltage limit” and “OV max limit” graphs have been merged into single “Voltage limit” graph
“Utilization limit” graph has been renamed to “No load limit” graph
“SLI sync” graph is now hidden on the systems with single NVIDIA GPU
Improved representation of performance limits graphs in On-Screen Display or in Logitech keyboard LCD. Now the names or currently triggered performance limits are being displayed in On-Screen Display or in Logitech keyboard LCD instead of previously used binary limits representation form
Added uP1816 voltage regulators support to provide compatibility with future custom design MSI graphics cards
Improved validation and handling of erroneous data reported after TDR or during runtime driver installation on NVIDIA graphics cards
Improved clock monitoring on GPU Boost 2.0 NVIDIA graphics cards after dynamic uninstallation/reinstallation of display driver during MSI Afterburner runtime
Added detection of runtime driver installation on NVIDIA graphics cards. Now MSI Afterburner is periodically checking the presence of NVIDIA driver and displaying notification message informing you that the connection with GPU is lost when the driver is being dynamically uninstalled during MSI Afterburner runtime
Startup profile is now also affected by “Lock profiles” button, which means that you cannot modify or delete your startup overclocking settings while this button is pressed. This feature can be useful to protect startup overclocking settings from modification while temporarily testing various overclocking scenarios on overclocked system
Added support for unofficial overclocking mode with disabled PowerPlay on PowerPlay7 capable hardware (AMD Tonga and newer graphics processors family)
Added unofficial overclocking support for AMD Polaris architecture based graphics cards
Added ability to use low-level hardware access interface on the systems with AMD graphics cards when legacy VGA BIOS image is not mapped to memory
Improved compatibility with the systems with both Overdrive 5 and Overdrive 6 API AMD graphics cards installed
Fixed bug causing the maximum value to be invisible on some hardware monitoring graphs under certain conditions (e.g. “Framerate” or “Frametime” graphs after closing 3D application)
Added ability to define numpad keys as hotkeys when <Num Lock> in on
RivaTuner Statistics Server has been upgraded to v6.5.0
|
I don't think there's a published changelog for RivaTuner yet but it should support DirectX 12 now in most situations as one of the bigger changes, Vulkan support is also planned eventually.
(Does not support UWP though since it's a bit different.)
|
|
| Back to top |
|
|
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
| Posted: Thu, 27th Oct 2016 15:51 Post subject: |
|
|
Forgot to update this with the newer beta releases since the initial release but 4.3.0 and RTSS 6.5.0 final are now available.
http://forums.guru3d.com/showthread.php?t=410627
http://www.guru3d.com/files-details/msi-afterburner-beta-download.html
(Will say 4.3.0 final/stable in the download link now.)
EDIT: Final changelog for Afterburner 4.3.0->
| Quote: |
Revision history Version 4.3.0
Added AMD Ellesmere and Baffin graphics processors families support
Added Overdrive N (Overdrive 7) technology support for AMD Polaris architecture based graphics cards
Added core voltage control for reference design AMD RADEON RX 460, AMD RADEON RX 470 and AMD RADEON RX 480 series cards with on-die SMC voltage controller
Added memory controller usage graph to hardware monitoring module for AMD graphics cards. Currently memory controller usage monitoring is implemented for AMD Ellesmere and Baffin graphics processors families only
Added GPU power draw graph to hardware monitoring module for AMD graphics cards. Currently GPU power draw monitoring is implemented for AMD Ellesmere and Baffin graphics processors families only
Added “Erase autosaved startup settings” option to “AMD compatibility properties” section in “General” tab. Starting from AMD Crimson drivers family, the driver is automatically saving hardware settings (e.g. overclocking or fan control settings) in the registry and apply it at Windows startup. It makes settings of any third party hardware overclocking tool virtually permanent, meaning that applied settings stay in the system even after rebooting or powering down the system. However, such implementation is unsafe and even potentially dangerous, because you're no longer able to undo unsafe overclocking with system reboot or even driver reinstall. To prevent such situations, MSI Afterburner can now optionally erase AMD driver's autosaved startup settings after applying new settings to hardware
Added GPU Boost 3.0 technology support for NVIDIA Pascal graphics cards:
Added percent based overvoltage support
Added voltage/frequency curve customization support. You may use traditional core clock slider on NVIDIA GeForce GTX 1070 and 1080 graphics cards to apply fixed offset to all voltage/frequency curve points as well as use brand new flexible voltage/frequency curve editor window for more precise per-point curve adjustment. The editor window can be activated either with “Voltage/frequency curve editor” button in the main application window or with <Ctrl> + <F> keyboard shortcut and it provides you the following features:
You may independently adjust clock frequency offset for each point with mouse cursor or <Up> / <Down> keys
You may hold <Ctrl> key to set anchor and fix clock frequency offset in minimum/maximum voltage point and adjust the offset of any other point with mouse to linearly interpolate the offsets between the anchor and adjustment points
You may hold <Shift> key while adjusting the offset of any point with mouse to apply the same fixed offset to all points. That’s equal to adjusting the offset with the slider in main application window
You may press <Ctrl> + <D> to reset offsets for all points
You may switch between traditional core clock control slider in the main window and voltage/frequency curve editor window to see how they affect each other in realtime
You may press <L> after selecting any point on the curve with mouse cursor to disable GPU dynamic voltage/frequency adjustment and lock the voltage and core clock frequency to a state defined by the target point. This feature allows you to test graphics card stability independently for each voltage/frequency point of the curve using real 3D applications or any stress test of your choice. In addition to stability testing usage scenario, MSI Afterburner allows you to save a curve with locked point setting to a profile, so you may easily switch between dynamic voltage/frequency management and fixed voltage/frequency settings in realtime (e.g. to achieve the maximum performance during benchmarking). Please take a note that fixed voltage and frequency settings do not allow you to disable power and thermal throttling
Increased default maximum limits for “Core clock”, “Memory clock” and “Memory usage” graphs to improve graphs readability on NVIDIA Pascal series graphics cards
Added configuration file switch, allowing you to toggle the source for “Power” graph on NVIDIA graphics cards. Normalized total power draw (i.e. normalized value from multiple power sensors installed on the graphics card) is selected by default per NVIDIA recommendation, however you can configure MSI Afterburner to display power draw from GPU sensor only
Improved representation of performance limits graphs for NVIDIA graphics cards per NVIDIA recommendations:
“Voltage limit” and “OV max limit” graphs have been merged into single “Voltage limit” graph
“Utilization limit” graph has been renamed to “No load limit” graph
“SLI sync” graph is now hidden on the systems with single NVIDIA GPU
Improved representation of performance limits graphs in On-Screen Display or in Logitech keyboard LCD. Now the names or currently triggered performance limits are being displayed in On-Screen Display or in Logitech keyboard LCD instead of previously used binary limits representation form
Community-created third party hardware database providing voltage control support on some non-MSI custom design graphics cards is now included in distributive
Added uP1816 voltage regulators support to provide compatibility with future custom design MSI graphics cards
Improved validation and handling of erroneous data reported after TDR or during runtime driver installation on NVIDIA graphics
cards
Improved clock monitoring on GPU Boost 2.0 NVIDIA graphics cards after dynamic uninstallation/reinstallation of display driver during MSI Afterburner runtime
Added detection of runtime driver installation on NVIDIA graphics cards. Now MSI Afterburner is periodically checking the presence of NVIDIA driver and displaying notification message informing you that the connection with GPU is lost when the driver is being dynamically uninstalled during MSI Afterburner runtime
Startup profile is now also affected by “Lock profiles” button, which means that you cannot modify or delete your startup overclocking settings while this button is pressed. This feature can be useful to protect startup overclocking settings from modification while temporarily testing various overclocking scenarios on overclocked system
Added support for unofficial overclocking mode with disabled PowerPlay on PowerPlay7 capable hardware (AMD Tonga and newer graphics processors family)
Added unofficial overclocking support for AMD Polaris architecture based graphics cards
Added ability to use low-level hardware access interface on the systems with AMD graphics cards when legacy VGA BIOS image is not mapped to memory (e.g. in UEFI environment)
Improved compatibility with the systems with both Overdrive 5 and Overdrive 6 API AMD graphics cards installed
Added driver registry key detection for the secondary display adapters in SLI/Crossfire systems. Due to this improvement it is no longer necessary to temporarily disable Crossfire when altering some settings in “!MD compatibility properties” section (e.g. “Extend official overclocking limits” or “Enable ULPS” settings)
Improved hardware polling and application startup time on ULPS-enabled Crossfire systems with AMD Fiji and newer AMD graphics processors
Primary GPU usage is no longer cloned on all secondary GPU usage graphs on Crossfire systems when “Enable unified GPU usage monitoring” is enabled in “!MD compatibility properties”. Please take a note that only the primary GPU load is available on Crossfire systems when this option is enabled
Updated IO driver provides more secure MMIO access interface
Fixed bug causing the maximum value to be invisible on some hardware monitoring graphs under certain conditions (e.g. “Framerate” or “Frametime” graphs After closing 3D application)
Added ability to define numpad keys as hotkeys when <Num Lock> in on
Guru3D RivaTuner Statistics Server has been upgraded to v6.5.0
|
And for RTSS 6.5.0
| Quote: |
Version 6.5.0
Direct3D12 On-Screen Display, screen capture and video capture support. Currently RivaTuner Statistics Server is the only application providing On-Screen Display support for both single-GPU Direct3D12 applications and multi-GPU Direct3D12 applications running in explicit LDA mode on both AMD Crossfire and NVIDIA SLI systems. Please take a note that Direct3D12 support is provided for native Win32 applications only, Microsoft UWP applications are currently not supported.
Added “Hide pre-created profiles” option to “General properties” section in “General” tab.
New option allows you to see your own profiles only and hide built-in pre-created 3D exclusion profiles supplied with the application.
64-bit Steam overlay library has been removed from delayed hooking engine configuration.
Now On-Screen Display is being rendered immediately after starting 64-bit Steam applications without 15 second delay.
Power users may still add 64-bit Steam overlay library to delayed hooking engine configuration if necessary
Fixed bug in the encoder server causing it to continue capturing audio and leak memory after recording a video through dedicated encoder server and closing 3D application without stopping video recording session
Updated profiles list
|
EDIT:
http://forums.guru3d.com/showthread.php?p=5344112#post5344112
Specific changes between 4.3.0 beta and 4.3.0 final.
|
|
| Back to top |
|
|
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
|
| Back to top |
|
|
Roach_666
Posts: 1299
Location: Hell in its Alpha Build
|
| Posted: Sat, 4th Nov 2017 16:17 Post subject: |
|
|
|
|
|
| Back to top |
|
|
JBeckman
VIP Member
Posts: 34863
Location: Sweden
|
| Posted: Sat, 9th Dec 2017 15:39 Post subject: |
|
|
https://forums.guru3d.com/threads/rtss-6-7-0-beta-1.412822/page-51#post-5499466
Afterburner 4.4.1 and Rivatuner Statistics Server 7.0.1
| Quote: |
MSI Afterburner v4.4.1:
· Fixed crash on application startup on the systems with more than 8 NVIDIA GPUs installed on recent NVIDIA display drivers
· Now the list of GPUs in "General" tab in the application properties is sorted properly on the systems with more than 10 GPUs installed
· Added voltage control for NVIDIA P104-100 and P106-100 mining cards
· Now MSI Afterburner is displaying notification message in monitoring window area when trying to overclock NVIDIA 10x0 series GPU with debug mode enabled in NVIDIA control panel
· Added "Frametate Min", "Frametate Avg", "Frametate Max", "Frametate 1% Low" and "Frametate 0.1% Low" graphs to hardware monitoring module. The graphs are duplicating benchmark statistics displayed in benchmark On-Screen Display, but give you more freedom in On-Screen Display customization
· Improved On-Screen Display layout editor. Now you can customize On-Screen Display graph styles independently for each graph instead of changing it globally
· RivaTuner Statistics Server has been upgraded to v7.0.1
RivaTuner Statistics Server v7.0.1:
· Improved built-in benchmarking engine:
o Added 1%/0.1% low framerate statistics calculation. Unlike traditional calculation approach, which is assuming post-processing of whole set of collected frametimes at the final stage of benchmarking, RivaTuner Statistics Server introduces new concepts of dynamic 1%/0.1% low framerate statistics calculation. The implementation is open source and demonstrated in RivaTuner Statistics Server SDK.
o 1%/0.1% low framerates are stored in the benchmark results file. 1%/0.1% low framerate are also displayed in benchmark On-Screen Display, so you may track 1%/0.1% low framerate dynamics in realtime.
· Updated SDK:
o Added new open source RTSSFrametimePipeSample sample. The sample is demonstrating implementation of custom benchmarking software, which is receiving per-frame frametime statistics in realtime via named pipe connection to RivaTuner Statistics Server. Post-processing text frametime log files after running the benchmark is no longer necessary! Now you may create your own benchmarking software and receive frametime data from RivaTuner Statistics Server in realtime directly while 3D application is running. Such approach was in use by some major hardware reviewers for a few years, now it is open source and available to everyone! The sample is also demonstrating the following techniques:
§ Realtime frametime graph rendering
§ Realtime current framerate averaging with sliding window algorithm, minimum and maximum framerates calculation and display
§ Dynamic 1%/0.1% low framerate statistics calculation and display
§ Logging per-frame frametime, current, minimum, average, maximum, 1% low and 0.1% low framerates to CSV text file
· Improved text formatting tags support:
o Now text position tags can use negative coordinates to move a text to a new position specified in character units instead of zoomed pixel units
o Improved text position tags handling for cases when the tag is used explicitly before the embedded object
o Added new visualization style support for embedded graph objects. Now it is possible to embed barchart styled graphs
· Slightly optimized On-Screen Display geometry batching for all 3D APIs in order to simplify the process of new functionality implementation in future versions
|
|
|
| Back to top |
|
|
Roach_666
Posts: 1299
Location: Hell in its Alpha Build
|
| Posted: Sat, 28th Apr 2018 15:17 Post subject: |
|
|
MSI Afterburner v4.5.0
http://www.guru3d.com/files-details/msi-afterburner-beta-download.html
| Changelog wrote: | • 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 |
Rivatuner Statistics Server v7.1.0
| Changelog wrote: | • Added On-Screen Display locking mechanism for third party On-Screen Display client applications. The mechanism is aimed to eliminate unwanted On-Screen Display flickering effect when some client application is performing risky two-stage On-Screen Display refresh while On-Screen Display is being actively refreshed by another client. Please take a note that third party On-Screen Display clients must be also updated in order to use this mechanism and get rid of flickering
• Added new text formatting tags support for displaying minimum, average, maximum, 1% low and 0.1% low framerates in benchmark mode. 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
• Now it is possible to adjust frametime history graph size via RivaTuner Statistics Server properties. Please take a note that you may use positive values to specify the size in pixels or negative values to specify it in symbols
• Now it is possible to toggle benchmark mode state from RivaTuner Statistics Server properties. However, third party benchmark client applications like MSI Afterburner are still required to toggle benchmark mode state with hotkeys during 3D application runtime and to save benchmark results to a text file
• Now it is possible to toggle between averaged or instantaneous calculation modes for peak (i.e. minimum and maximum) framerates for benchmark mode via RivaTuner Statistics Server properties
• Fixed issue in context help system, which could cause the tooltip to flicker when it was displayed below mouse cursor
• Fixed screen capture feature in On-Screen Display preview window when RivaTuner Statistics Server is installed in UAC-protected folder
• Updated SDK:
○ Now RTSSSharedMemorySample sample code is demonstrating the implementation of On-Screen Display locking and flickering filter
• Updated profiles list |
|
|
| Back to top |
|
|
| Page 1 of 1 |
All times are GMT + 1 Hour |
I, like you, like having the FPS overlay on screen.. I like seeing what utilisation there is. Hopefully Unwinder keeps working on Afterburner but if he doesn't, there's at least Precision X eh? 
