1. Для разблокировки разгона в файле MSIAfterburner.cfg (Находится в папке, где установлена программа) необходимо прописать следующие значения:
UnofficialOverclockingEULA = I confirm that I am aware of unofficial overclocking limitations and fully understand that MSI will not provide me any support on it
UnofficialOverclockingMode = 1
2. Для разблокировки напряжения и его мониторинга в том же файле прописываем следующие значения:
UnlockVoltageControl = 1
UnlockVoltageMonitoring = 1
(!)В драйвере Catalyst 12.2+ не хватает пары файлов, скачиваем здесь
3. Программа так же "умеет" отображать энергопотребление CPU и GPU в играх.
~ Для этого в Настройках (Настройки > Мониторинг) нужно активировать пункты "Энергопотребление" и "Энергопотребление ЦП".
4. После перезагрузки или включения компьютера слетает профиль разгона. Как сделать, чтобы он грузился вместе с Windows?
~ Одно из решений тут - настройка автозапуска
~ Или штатный метод попробовать, описанный здесь
5. Выскакивает ошибка "В данный момент невозможно произвести внедрение в Diretc3D12 компоненты. Строго рекомендуется перезапустить приложение"
Решение описано в этом посте
6. Шпаргалка по оформлению оверлейного дисплея от камрада y0121ck - ОСНОВЫ и ДОПОЛНЕНИЕ

New RTSS beta is around the corner. Many changes inside this build are related to scanline sync. But a lot of changes are also aimed to ... educate reviewers:

· Various Vulkan bootstrap layer and Vulkan overlay renderer cleanups aimed to improve compatibility with Vulkan validation layer
· Improved compatibility with multithreaded Direct3D1x applications, using multiple Direct3D devices and swapchains and concurrently presenting frames on them from different threads (e.g. Windows Terminal)
· Added RenderDelay profile compatibility switch, allowing delaying On-Screen Display initialization and rendering for some applications when it is necessary (e.g. Resident Evil 3 in Direct3D11 mode when HDR mode is enabled)
· FCAT overlay update rate is no longer limited to overlay content update rate in offscreen overlay rendering mode
· Added new hypertext tags for displaying process specific 1% low and 0.1% low framerate graphs. Now multiple simultaneously running 3D applications can display their own independent 1% low and 0.1% low framerate graphs instead of foreground 3D application’s 1% low and 0.1% low framerate graphs in the previous version
· Improved 1% low and 0.1% low framerate graphs rendering implementation for graph and diagram rendering modes. The graphs showing the history of 1% low and 0.1% low framerate changes has no statistical sense, so now RivaTuner Statistics Server is showing you more informative dynamic histogram of sorted and the most slowest immediate framerates with highlighted 1% or 0.1% areas on it. For barchart rendering mode 1% low and 0.1% framerate graphs still display the current value like before
· Added new “moving bar” rendering mode for FCAT overlay. New mode is aimed to simplify visual identification of tearline position and it can be used when calibrating Scanline Sync settings
· Added new “Frametime calculation point” option to “General” application properties. This option is aimed to help those who try to directly compare frame rendering start timestamp based frametimes with frame presentation timestamp based frametimes. Please refer to new option context help to get more detailed info
· Added new “Percentile calculation mode” option to “General” application properties. This option is aimed to help those who try to compare different implementations of 1% low and 0.1% low framerate metrics in different applications. Please refer to new option context help to get more detailed info
· Added new “Framerate limiting mode” option to “General” application properties. Two alternate framerate limiting modes selectable with this option (“front edge sync” and “back edge sync”) are intended to be used in conjunction with scanline sync mode. Using those options in tandem allows enabling so called hybrid scanline sync mode. In this case actual target scanline synchronization is performed just once for initial tearline positioning then tearline position can be steered with high precision system clock. This option can also help those who try to compare flatness of frametime graphs measured at different points (frame start vs frame presentation timestamp based)
· Added power user controllable passive wait stage to framerate limiter’s busy waiting loop. It is aimed to help those who is ready to sacrifice timing precision in favor of lower CPU load
· Improved power user oriented scanline sync info panel. New performance counters are aimed to improve the process of scanline sync calibration and help you to diagnose tearline jittering. The following new performance counters have been added to it:
o Sync start – index of scanline where 3D application called 3D API frame presentation function and scanline sync engine started the process of waiting for the target scanline
o Sync end – index of scanline where scanline sync engine ended the process of waiting for target scanline. Ideally it must be as close to expected target scanline as it is possible
o Present – index of scanline where 3D API frame presentation function was actually called after performing scanline synchronization. For normal scanline sync modes it is pretty close to the previous performance counter. For hybrid scanline sync mode it can drift depending on your framerate limit, if it doesn’t match with your display refresh rate
o Present latency – time spent inside 3D API frame presentation call

New hybrid scanline sync mode, new scanline sync calibration related performance counters and indicator are demonstrated in this short video:

- Added Dirt 5 compatibility profile. More details about it are available in my previous post.
- Framerate limiter’s passive waiting implementation is now overriding timer resolution on each wait iteration instead of doing it just once on startup. This change is aimed to improve passive waiting precision in the applications, which dynamically alter timer resolution in realtime (e.g. Dirt 5 before and after playing in-game cinematic).
- Fixed bug in video capture framerate limiting mode, corrupted in the previous beta during porting timing calculations from floating point to integer format.
- D3DKMT based process specific local videomemory usage counter, similar to one introduced in MSI Afterburner 4.6.3 beta 2, is now natively supported by HAL of OverlayEditor plugin.
- External access to the game process required to implement D3DKMT based process specific videomemory usage counter is restricted for EAC and BattlEye specific titles, so RTSS introduces asynchronous process specific performance counters access interface integrated into hooks library, which is running inside protected process context. OverlayEditor plugin also supports this interface and allows using these counters in your overlay templates. Sample OverlayEditor overlay template demonstrates this interface usage to display foreground process specific RAM and VRAM usages.
- Added new <EXE> hypertext tag, allowing displaying hooked process executable name in overlay. Sample OverlayEditor overlay demonstarates new tag usage.

Beta 9 got one more improvement today. I've just added "total videomemory" data source to HAL in OverlayEditor and two simple "videomemory usage percent" and "videomemory usage percent \ process" sources derived from it to simplify the process of visualizing normalized percent based usage values. That was possible with correction formulas before, but now it is easier for OverlayEditor beginners to understand it. New data sources are used in sample overlay template to visualize process specific RAM/VRAM usages right on animated round progress indicators. So it is easier for you to see current process RAM/VRAM usage inputs into total system wide RAM/VRAM usages.

Still polishing sample OverlayEditor overlay template for beta 9. One more improvement on the way: now there are process specific RAM/VRAM usage history graphs rendered on top of sytem-wide filled RAM/VRAM usage graphs, so it is easier to see if delta changes in time

- Added Zen3 CPU monitoring
- Added internal "Memory usage / process" and "RAM usage / process" graphs based on async process performance counter access interface introduced by the latest RTSS. Unlike GPU.dll plugin, those sources support in-process VRAM and RAM reporting for EAC/BattlEye protected and UWP titles.
- RTSS has been upgraded to the latest 7.3.0 beta 9