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 - ОСНОВЫ и ДОПОЛНЕНИЕ

Guys, I’m afraid that we have to stop waiting for a fix from NVIDIA side for RTX 30x0 series fan speed reporting issue, it is taking way too long. So here is new beta with small “hack”, which we’ll use to bypass the problem from our side until the fix arrives form NV side (if it ever arrives). The root of this problem is normalized fan speed reporting, which NVIDIA decided to introduce with 30x0 series cards. Fan speed % reported by NVIDIA driver and displayed in _any_ monitoring software is no longer reflecting the real fan speed %. Now it is normalized value, which is mapping vendor specific RPM limits to GUI min%-max% fan speed range. For reference design min% is equal to 30% and max% is 100% and RPM limits are properly mapped to that range. But the chaos began when partners started altering reference cooling system and tune their RPM limits, while leaving min 30% limit unchanged. As a result, on some custom design cards min% is still set to 30% and you can see it as the minimum fan speed for automatic fan control mode, but the real fan speed can be MUCH slower or faster. This is confusing users and causes effects of weird jumps in fan speed, i.e. you can see a few % (or even a few dozen %) difference between the speed you set and the speed you see reported back by driver. Until it is addressed by driver and VGA BIOS updates, we fix it the following way:

- Afterburner will stop relying on NVIDIA’s native fan speed reporting in monitoring module for 30x0 series cards as soon as you enable manual fan speed control (i.e. set fixed fan speed of software fan curve). In this case it will simply display you the last programmed fan speed instead of reading back normalized (and possibly distorted) fan speed value from NVIDIA driver. NVIDIA’s normalized fan speed monitoring is still being used as soon as you enable default automatic fan speed control, because it is the only way to read fan speed in this case. Just keep in mind that in this case you’ll always see fan speed floating inside (30%-100%) range, and it may not match the real fan speed range. So always pay attention to tachometer readings.

- Afterburner will stop relying on NVIDIA driver’s native fan speed limits for GUI on 30x0 series cards. Currently they don’t reflect the reality on many non-reference cards.

In addition to fan speed problem workaround new beta also adds an ability to force legacy OC Scanner usage on 455+ and newer drivers on Pascal and Turing series GPUs. New scanner API has limited support for pre-Ampere GPUs, e.g. it is currently unsupported on Pascals and seem to be broken on Turings in SLI configs. So you may force old legacy scanner usage, if your system is affected. To force it set LegacyOCScanner to 1 in [NVAPIHAL] in MSIAfterburner.cfg

Grab new beta here: https://download-eu2.guru3d.com/afterbu ... d15854.zip