Как включить мониторинг в играх?

Доброго времени суток!

Сейчас я постараюсь объяснить как это сделать. Начнём :)

Для начала нам понадобятся две программы: Msi afterburner и hwinfo64

Ссылки на них:

1)Msi afterburner (выбираем самую последнюю версию):

Устанавливаем обе программы.

Далее заходим в msi afterburner, кликаем settings открываем последнюю вкладку интерфейс и выбираем русский язык, перезапускаем программу и снова открываем settings, далее переходим во вкладку мониторинг и в окошке "Активные графики мониторинга" Ищем "Частота кадров" ставим галку на ней и внизу выбираем "Показывать в Оверлейном Экранном Дисплее" Далее переходим во вкладку "Основные" и ставим две галки "Запускать вместе с Windows" и "Запускать в минимизированном состоянии" Кликаем ОК, закрываем прогу. Теперь в трее у вас появился значок с фиолетовыми цифрами, это RTSS (Riva Tuner Statistic Server), открываем его и ставим всё как на скрине (1), после сворачиваете его обратно.

Теперь переходим ко второй программе HWiNFO

Открываем её тыкаем галку sensors only и жмём RUN.

Переходим в "Configure Sensors"

В первой же вкладке General выставляем значение "Scan interval" на 200 (скорость обновления датчиков)

Теперь переходим во вкладку "OSD (RTSS)" в столбце "System" кликаем параметр Physical Memory Used и ставим две галки снизу "Show value in OSD" и "Show Label in OSD" Рядом в параметре Position выставляем первое значение (Line) на 3, а второе (Column) на 1, теперь переходим во вкладку custom и переименовываем этот же параметр как показано на скрине (2). Поздравляю! Мы только что вывели инфу о потребляемой оперативной памяти :) Думаю вам понятна процедура, далее я приведу список наименований с которыми нужно сделать так же, за исключением параметра Position (позиция на экране) ну и названия собственно

- Core #0 Clock (Будет показывать частоту процессора) ставим галку show value in OSD, Line:2, column:2

- Total CPU Usage (Показывает нагрузку на процессор) ставим галку show value in OSD и Show label in OSD, Line:2, column:1 (так же идём во вкладку layout или custom и переименовываем его так как называется ваш процессор)

- CPU 0 (Температура процессора) ставим галку show value in OSD, Line:2, column:3

- GPU Temperature или GPU Thermal Diode(radeon) (Температура видеокарты) ставим галку show value in OSD, Line:1, column:3

- GPU Core Load или GPU D3D Usage(radeon) (Загрузка видеокарты) ставим галку show value in OSD и Show label in OSD, Line:1, column:1 (так же идём во вкладку layout или custom и переименовываем его так как называется ваша видеокарта)

- GPU Memory Allocated или GPU D3D Memory dedicated(radeon) (Количество потребляемой видеопамяти) ставим галку show value in OSD, Line:1, column:2

Далее в трее жмём правой кнопкой мыши по программе HWiNFO64 и выбираем Settings и смотрим чтобы стояли галки Minimize Main Window on Startup и Minimize Sensors on Startup. Если что не понятно, пишите сюда в комменты, помогу)

Ну вот собственно и всё :)

Сори если как то криво или не понятно написано, первый мой гайд )

Техническая документация

Страница 6 из 17

Да. RivaTuner предлагает мощный и гибкий механизм триггеров, который может быть использован для создания сложных схем динамических управления системой охлаждения и разгона. Вы можете использовать его для задания различных скоростей вентилятора в 2D и 3D режимах. Для этого выполните следующие действия:

1. Откройте закладку «Low-level fan control»
2. Настройте требуемую скорость для 3D режима (к примеру, 100% цикл работы) и сохраните настройки в профиль низкоуровневого управления вентилятором, например «3D fan settings».
3. Настройте требуемую скорость для 2D режима (к примеру, 50% цикл работы) и сохраните настройки в профиль низкоуровневого управления вентилятором, например «2D fan settings».
4. Перейдите на закладку «Launcher» и добавьте новый Regular Item, назвав его, к примеру, «apply 3D fan settings».
5. Отметьте флажком опцию «Associated fan profile» и выберите тип профиля — low-level.
6. Выберите подходящий профиль, «3D fan settings» в данном случае, и сохраните Launcher Item, нажав на кнопку «OK».
7. Перейдите на закладку «Launcher» и добавьте новый Regular Item, назвав его, к примеру, «apply 2D fan settings».
8. Отметьте флажком опцию «Associated fan profile» и выберите тип профиля — low-level.
9. Выберите подходящий профиль, «2D fan settings» в данном случае, и сохраните Launcher Item, нажав на кнопку «OK».
10. Запустите модуль низкоуровневого аппаратного мониторинга и щелкните правой кнопкой по графику «Core clock», выберите из меню «Setup». Это нужно для создания триггеров для частоты GPU в целях обнаружения переходов между 2D/3D режимами.
11. Добавьте новый триггер (threshold), назвав его «3D mode detection threshold» и определите пороговое значение частоты. Помня, что для GeForce 7800 GTX частоты 2D режима составляют менее 300 МГц, а 3D режима — более 400, можно задать значение 300 МГц.
12. Выберите запуск item в поле «Launch … on upward threshold crossing» и выберите объект «apply 3D fan settings». Таким образом, модуль мониторинга будет всегда запускать этот объект при изменении частоты через значение 300 МГц в направлении от меньших значений к большим, т.е. при запуске 3D приложений.
13. Выберите запуск item в поле «Launch … on downward threshold crossing» и выберите объект «apply 2D fan settings». Таким образом, модуль мониторинга будет всегда запускать этот объект при изменении частоты через значение 300 МГц в направлении от больших значений к меньшим, т.е. при выходе из 3D приложений.

Мне известно, что карта GeForce 6800 Ultra использует 2D/3D управление вентилятором на уровне драйвера, и не укомплектована контроллером с температуро-зависимым управлением вентилятором. Однако мне хотелось бы настроить вентилятора работу с полной скоростью только при превышении частотой определенного рубежа. Возможно ли такое сделать с помощью RivaTuner?

Да, прочитайте ответ на предыдущий вопрос. Способ очень схож с приведенным выше, вам нужно просто настроить триггер для значения температуры ядра, а не частоты.

Могу я включать/выключать показ экранного меню сервера статистики RivaTuner нажатием «горячих» клавиш?

Да, вы можете привязать загрузку/выгрузку сервера статистики к нажатию клавиш. Это также влияет на видимость экранного меню Для привязки загрузки сервера к клавише выполните следующие действия:

Riva Tuner Statistics Server help? Operating Systems and Software - Linus Tech Tips

Like This Unlike

Fahrenheit 25 May 2015

Like This Unlike

Minibois 25 May 2015

Like This Unlike

Fahrenheit 25 May 2015

Like This Unlike

Minibois 25 May 2015

Alright, because I heard some mods interfere with some applications that show your fps and some recording programs (heard about Fraps and DX Tory).

Like This Unlike

Fahrenheit 26 May 2015

Alright, because I heard some mods interfere with some applications that show your fps and some recording programs (heard about Fraps and DX Tory).

Like This Unlike

GER_T4IGA 26 May 2015

Like This Unlike

Tim Drake 26 May 2015

Альтернативы RivaTuner от производителей видеокарт

Устанавливал в качестве эксперимента Windows 7 x64 и всё шло хорошо, пока не захотелось поиграть в Fallout 3. Выяснилось, что RivaTuner не может разогнать видеокарту, предположительно из-за неподписанного драйвера. Альтернативное решение нашлось быстро.

Оказывается, производитель видеокарт EVGA заключил соглашение с автором RivaTuner и плодом их сотрудничества стала фирменная утилита EVGA Precision. Поддерживается мониторинг и оверклокинг современных видеокарт GeForce, причем не обязательно производства EVGA. Для рядового пользователя EVGA Precision будет лучше RivaTuner благодаря простоте, наглядности и понятности. Причем для жаждущих большего доступны расширенные настройки.

Другой производитель видеокарт, компания MSI, решила перенимать передовой опыт. Утилита MSI AfterBurner по функциональности в точности повторяет аналог, хотя ее раздувшееся окно понравилось мне значительно меньше. Зато MSI AfterBurner поддерживает видеокарты ATI.

Новости про RivaTuner

Алексей Николайчук a.k.a. Unwinder выпустил очередное обновление к 4-й версии фирменной для MSI утилиты Afterburner, которая является одной из наследниц RivaTuner и предназначена для мониторинга характеристик работы видеокарты в реальном времени с выводом значений в OSD .

В версии 4.2.0 представлен целый ряд экспериментальных разработок по управлению видеокартами AMD, а также появились новые возможности контроля ускорителей от NVIDIA.

• Добавлена поддержка графики AMD Fiji.
• Переработан архитектурный слой аппаратной абстракции, позволяющий реализовать управление напряжением посредством прямого доступа к встроенному контроллеру напряжений на GPU AMD Fiji, в дополнение к ранее реализованным функциям контроля напряжения посредством сторонних контроллеров.
• Добавлен контроль напряжения ядра для AMD RADEON R9 Fury / Nano референсной конструкции.
• Добавлена неофициальная поддержка разгона для карт PowerPlay7 (AMD Tonga и более новые).
• Добавлено определение версии для драйвера AMD Radeon Software Crimson. Номер версии нового драйвера не имеет обратной совместимости, в связи с чем возможно некорректное наименование драйвера при установке старых версий поверх Crimson.
• Добавлен контроль напряжения ядра, памяти и дополнительного канала PEXVDD для видеокарт серии MSI GTX980Ti Lightning заказной конструкции.
• Добавлен мониторинг температуры VRM и памяти для видеокарт MSI GTX980Ti Lightning заказной конструкции.
• В SDK добавлена детальная документация о структуре базы данных программы для сторонних разработчиков.
• Мониторинг температуры для процессоров AMD Family 10h – 16h больше не является экспериментальным и включён по умолчанию.
• Немного изменена реализация мониторинга использования видеопамяти в графических платах AMD и Intel.
• Улучшен движок скинов.
• Добавлена локализация для бразильского португальского языка.
• Обновлён RivaTuner Statistics Server до версии 6.4.1.

Guru3D RTSS Rivatuner Statistics Server Download v6

Guru3D RTSS Rivatuner Statistics Server Download v6.4.0

Advertisement

Here you can download RTSS Rivatuner Statistics Server. Initially designed as a small helper application for RivaTuner graphics card utility, RivaTuner Statistics Server became de-facto framerate monitoring, On-Screen Display and high-performance videocapture service provider for other graphics card utilities.

• The server provides framerate and frametime monitoring support to the client applications. Framerate and frametime statistics is being collected for DirectX and OpenGL applications. The statistics can be rendered in On-Screen Display or provided to client applications connected to the server.
• The server provides 3D acceleration usage statistics to the client applications. The clients can use the statistics to determine if any 3D applications are currently running and apply different hardware profiles depending on it.
• The server provides On-Screen Display support to the client applications. The clients can display any text info in the On-Screen
• Display in DirectX and OpenGL applications. The server can be also used as a standalone framerate monitoring solution and display own framerate statistics in the On-Screen Display.
• The server provides desktop and in-game screen capture support to the client applications. BMP, PNG and JPG screen capture formats are supported.
• The server provides high-performance realtime desktop and in-game video capture support to the client applications.
• Uncompressed, high-performance custom RTV1 and native MJPG video encoding, encoding with third-party external VFW compatible codecs (e.g. Lagarith or x264vfw) and hardware accelerated H.264 encoding via Intel QuickSync, NVIDIA NVENC and AMD VCE are supported in conjunction with wide range of additional video capture related options, multisource stereo and multichannel (for Window Vista and newer) audio capture with Push-To-Talk support. The functionality of expensive commercial video capture products is now available to everyone absolutely for free! There is no need to buy dedicated video capture software anymore!
• Framerate limiting support. Limiting the framerate during gaming can help to reduce the power consumption as well as it can improve gaming experience due to removing unwanted microstuttering effect caused by framerate fluctuations.
• User extendable architecture. You may express your creativity and design your own skins for RivaTuner Statistics Server, create localization for your native language, use the server to display any custom text in On-Screen Display directly from your own application and many, many more!

System requirements:

• Windows XP, Windows Vista, Windows 7, Windows 8 or Windows 10 (both x86 and x64 versions) with full administrative rights
• Any DirectX or OpenGL compatible graphics card1

Version 6.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:
  • Increased upper adjustable bitrate limit to 130 Mbps for NVIDIA Maxwell graphics processors family
  • 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:
  • 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

Version 6.2.0

• Improved compatibility with FRAPS in 64-bit mode
• Removed MSI Afterburner exclusivity lock for 64-bit On-Screen Display service
• Drastically improved skin engine:
• Improved skin compiler gives more detailed error messages when skin compilation fail due to error in some source image file
• Source image file format is no longer limited to 24-bit BMP files only. Now skin compiler supports all possible bit depths for BMP format and fully supports PNG format with alpha channel
• Added built-in bitmap effect for extracting alpha-channel from PNG image files
• Skin format has been upgraded to v1.3. New format supports alpha channel based transparency for skinned window, allowing skin designers to define semi-transparent skin areas, apply antialiasing to the skin window edges and so on
• Added new skinned window composition modes support and “Skin composition mode” settings to “User interface tab”.

New settings allows you to use one of the following modes:

• Traditional mode – suits best for backward compatibility with existing skins and performance testing
• Layered mode with colorkey - provides much faster rendering of skins with non-rectangular window shape and additionally allows you to adjust transparency of skinned window
• Layered mode with alpha – provides per-pixel alpha channel support and advanced visual effects for compatible skins and also allows you to adjust transparency of skinned window
• Skin format reference guide has been updated to v1.7 to document these changes

Version 6.1.3

• Improved handshaking algorithm reduces the risk of seeing multiple running instances of child processes (e.g. RTSSHooksLoader64)
• Added 340.xx drivers family support to NVIDIA NVENC H.264 encoder plugin
• Added exception handling to audio capture routine
• Added automatic prerecording support to video capture engine. Now video capture client applications (e.g. MSI Afterburner) can configure the server to start prerecording automatically when 3D application is started

Version 6.1.2

• Added raster 3D On-Screen Display rendering mode support for Wolfenstein. The New Order rendering engine

Version 6.1.1

• Fixed memory leak in Intel QuickSync H.264 encoder plugin running in Direct3D 11 mode
• Added 337.xx drivers family support to NVIDIA NVENC H.264 encoder plugin
• Added On-Screen Display profile for Banished Direct3D9 renderer
• Added On-Screen Display profile for Daylight

Riva statistic server

That's correct, I've released (most) of the source of HearthstoneTracker on github today: https://github.com/HearthstoneTracker/HearthstoneTracker

Note that the current 'master' branch on github is not the latest official release. I cleaned it up a bit, changed licenses and removed obsolete and test projects.

It will take some time to get a new official release out, as I iron out some last issues and implement any incoming pull requests. Also, the issue tracker on github has not all current outstanding issues yet.

I will review any incoming issues and/or pull requests. If you have any questions, feel free to contact me.

Any contribution is greatly appreciated, reporting bugs, implementing a new feature or donating a few bucks to keep the servers running.

Hope this will keep this awesome tool going forward and let the community pick up development as well.

Aug 31, 2014

So I got the following question about the new engine/hook:

Very nice update. 1.9.20 seems to have some kind of injecting code, but does Blizzard gave this version their seal of approval. Bli? policy usually doesn't allowed injection and memory check. I don't wan't to be banned for "cheating".

Here is my response:

The tracker has always contained 'some kind of' injection code. This is used for DirectX screen capture. (it hooks into the games direct3d methods).

The new engine in the latest version does the same hooking, except now it doesn't get pixel data. It gets the actual game data.

Technically, it's almost the same. But this way, it makes it so much easier and 100% accurate to track what is going on. No more cpu intensive image comparison, no more false positives, etc.

I have to agree, this method is much, much closer to the hearthstone core and you can do things, blizzard developers have not intended to expose.

But, if you look at for example World of Warcraft, Blizzard allows a lot of 3rd party development. There are a huge amount of addons/tools which customize the game.

WoW is very open for 3rd party developers and has a lot of api's / hooks developers can use. Think about Boss attack alerts, quest arrows and even 'trinket sounds' in PvP battles.

Now, hearthstone is relatively new and developed by a small team. So I can imagine that they didn't spend their time building a complex, modifiable system for other devs to use.

But (looking at WoW) it does show that Blizzard actually encourages players to develop around their game.

Of-course, they have to draw a line. But in my opinion, this is not a technical issue (logging / hooking / sniffing).

In my opinion (whatever method used) any tool (especially in a competitive setting) should not give an unfair advantage. Also, such a tool should not expose information not already visible in the game.

Personally, I'd like to see a public API / developer kit (just like WoW), where the HS developers decide what we can do and what not. This is not the case though and I understand they don't have the resources to do so.

That means, we as 3rd party developers (which Blizzard needs and likes so much) have to resort to other methods.

Currently, Hearthstone is not protected by any anti-cheat mechanism. And whenever they will activate it, HS tracker will be flagged (because of the injection methods used).

But, I don't think they will anytime soon. And if they do, they will for sure recognize the fact, that there are 'legit' tools out there.

It's up to Blizzard to provide us with a better/public development system or whitelist those tools.

Aug 30, 2014

This release contains some more (possible) fixes for the 'double' games issue.

It also fixes a few other minor UI inconsistencies (like refreshing too much, when editing a deck).

I sneaked in an experimental feature: super-fast, 100% accurate tracking

How does this work?

• By injecting our own 'logging' module into the Unity Engine (the game engine Hearthstone is build on)
• It's super-fast (consumes almost no cpu resources, unlike screen capture)
• It's 100% accurate

By default, this method is not (yet) activated. You have to go into the tracker settings and select 'Hook' as the capture engine.

What does not work yet?

• Taking screenshots of decks is not yet implemented (this new engine is not a 'screen cap' engine, so I need to write something else for deck screenshotting)
• Arena's are only tracked after playing the arena games (not a big deal, but it can cause some confusion)
• The injecting process is a bit unstable now. You have to restart HS and/or HS tracker sometimes to get it to work properly.

• This new engine can track more and 100% accurate than any screen cap engine can: read your decks, played cards, (opponent) player names, etc. In the future (v2+) we will add things like this.
• For 'version 2.0' we will completely replace the (slow / inaccurate) screen cap engines with this new hook engine.
• I need (a lot) of feedback on this new method and how it works on different pc's / setups before I will make it the default.

So. try it out! and report any issues you see.

Aug 28, 2014

There is currently a visual bug, where games show up twice. Deleting any of those 'double' games will result in data getting lost.

I've put up a new version which hopefully fixes the issue where games show twice.

Also, this release has updated 3rd party packages (latest UI components, updated (faster) math library, etc)

Apr 23, 2014

Hey everyone,

First of all, I'd like to thank every Hearthstone player using Hearthstone Tracker for their support. Since the first beta release, the tool has been download over 10.000 times and a lot of you are using the tracker to it's full potential.

Also thanks for the numerous feature suggestions and bug reports. It has helped me a lot developing this tool from a simple tracker to what it is now.

Also a big thank you to all who made a donation. Servers are still running and I'm drinking coffee as I write this :-)

A quick update on the lack of recent updates:

I can't tell you much yet about what is coming. But I can certainly tell Hearthstone Tracker is not dead.

• I recognize the fact that Hearthstone is a multi-platform game. Especially with the recent iPad release and upcoming Android support. I want to support the users of those platforms with the same or equivalent features (as much as possible).
• Detection problems: image recognition is not 100% accurate. I really want the auto-detection to be 100% accurate. I'm looking into alternative detection methods.
• Visual / user interface bugs: I will try to fix most or all of the reported issues in the current version.
• Moving forward: Unsure. I'm currently talking with some people about what would be the best way to move forward. E.g. web-based / multi platform targeting /.
• HearthstoneTracker (although not open-source) is a free product. As I'm currently without a paid job or project, I'm looking into a way of monetizing this so I can keep working on this full-time. How? I don't know yet. But don't be scared, the tool in it's current state (and upcoming minor releases) will remain 100% free.

Got to go now,

Good luck on the ladder!

Mar 23, 2014

Major DirectX performance / memory improvement

The DirectX hook/engine received a major overhaul.

The new DirectX capture engine now eats WAY less cpu resources and memory.

On Very fast setting (30 fps). The tracker cpu usage stays below 1% and the hearthstone process around 2 %.

That's almost a 500% increase in performance :-)

The DirextX engine is now the recommended engine, as it is the fasted and can capture while hearthstone is in full-screen or in the background.

• Drag and drop games between different arenas
• Delete multiple games at once using multi-select (using Ctrl/Shift click). Then press the 'delete' key.

• A few performance improvements in the image scanner (less memory copying)
• Fixed an issue when doing arenas on multiple servers. It didn't take into account the current server when determining your running / last arena. Which could lead to double arenas being created.

Mar 17, 2014

• Deleting arenas didn't delete their games. Trying to delete those games resulted in a crash. Fixed this now
• Fix the colors of the percentages in the statistics screen and added orange as a color.

• Added a simple feature to merge arenas. Click 'merge' and if the hero matches with your previous arena the games are moved and selected arena deleted.
• When an arena game is (wrongly) detected as a loss and it also was the 3rd loss in an arena, a new arena session was started the games after. This resulted in some split arena sessions and no way to correct this.
• Now, when this happens, the tracker tries to correct the last game to a win (based on arena screen win/loss detection)

It's a bit complex to describe, but I hope this last fix will make arena tracking even more accurate.

Mar 15, 2014

• Added one extra win detection point (where opponent concedes)
• Add icons to some buttons
• Add a toggle button to show/hide arena deck screenshot (hidden by default)
• Changed the auto-detect engine to be a bit smarter.

• Fixed the statusbar in arenas to show data again (oops)
• minor ui fixes
• add search by text to the charts screen

Mar 15, 2014

• Fixed a crash coming from the charting library (the 'TimeManager' error)
• fixed some minor ui issues with selecting / deleting an arena
• some minor cleanup of other internal stuff

I hope the crash after arena games which sometimes occurs is now solved.

• smarter turn detection. Extra detection points and takes into account missed turn detections
• changed decks user interface. It works better now if you have a lot of decks.
• changed some arena tracker logic. It's sometimes still tracking double arenas, hopefully this fixes it or helps me debugging towards a final fix.
• add more logging to help debugging possible problems.
• fixed a crash when deleting a deck with a slot assigned.