MSI AB / RTSS development news thread

Looks like NVIDIA also applied rather similar fix in 457.09, normalized fan speed monitoring is finally gone and driver reports target fan speed as is now, without any normalization and similar to all previous GPU generations. This caused applications expecting normalized fan speed reporting on 3xxx series to stop working. Updates were necessary to get rid of normalization, beta 3 already have this change inside preemptive.

 

RTSS 7.3.0 beta 9 is around the corner. Changes list includes:

- 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.

Screenshot is BattlEye protected “Escape From Tarkov” with process specific RAM and VRAM usages in sample OverlayEditor's overlay:

 

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.

 

It is not supported yet, how do you expect a few month old beta to peek in the future and detect recently released hardware? No ETA on compatible version, it is even not in development yet.

 

No ideas how long will it take for MSI to provide me a sample. It directly depends on it. Considering that I’m STILL waiting for a 3080, it may take a while.

 

RTSS 7.3.0 beta 9 build 24084 is online. Changes list was published a few posts above. And in the following two posts: #1 and #2.

https://download-eu2.guru3d.com/rtss/RTSSSetup730Beta9Build24084.rar

 

A bit of humor. Always nice to see youtubers educating you and explaining you how hardware monitoring internals of MSI AB work in reality.