MSI AB / RTSS development news thread

In meanwhile you may read context help for user mode/kernel mode hardware access levels and guess what's possibly going on on BattleEye side.

 

Guys, I mentioned before that sadly we cannot yet release new MSI AB beta with RTX support because of evil green NDA. J However, nothing can stop us from releasing new RTSS beta. So in meanwhile you’ve got a few new features to test and to play with. Here is RTSS 7.2.0 beta 5, changes list comparing to beta 4 includes the following:

· Added power user oriented idle framerate limiting mode. Unlike traditional framerate limiting mode, idle framerate limiting mode is only affecting inactive 3D applications running in background. Idle framerate limit is specified as a target frametime with 1 microsecond precision. Idle framerate limiting mode helps to reduce power consumption when you minimize some heavy 3D applications and switch to other processes
· Increased static command buffer size for Vulkan and pure Direct3D12 renders to increase amount of primitives rendered in On-Screen Display in a single pass
· Improved desktop duplication based desktop video capture implementation ( Windows 8 and newer OS versions):
o Now desktop video recording sessions do not stop on display mode switch or on switch to exclusive fullscreen mode. Such approach allows you to start capturing video on desktop then launch some 3D application and create a video file containing both desktop and 3D application’s video streams
o Improved video capture API allows video capture frontend applications (e.g. MSI Afterburner) to force desktop or 3D application video capture modes in addition to default mixed desktop/3D application capture mode
o Now desktop capture is using multhithreaded active busy-wait loop frame capture instead of timer driven frame capture in order to improve frame timing precision and resulting video smoothness. The previous timer driven frame capture can be enabled via configuration file if necessary
o Decreased desktop duplication timeouts in order to improve RivaTuner Statistics Server GUI response time under certain conditions during desktop videocapture sessions in timer driven frame capture mode
· Added timeout to API hooks injection in CBT hook handler. The timeout is aimed to reduce injection related CPU overhead on some systems, related to high mouse polling rate combined with keyboard/mouse hooks installed by third party applications
· Interoperability D3D10 page flips on some systems are now filtered by framerate calculation module in OpenGL/Vulkan applications

http://msi-afterburner.guru3d.com/RTSSSetup720Beta5.rar

Stay tuned!

 

Keep in mind that it is a profile specific setting, so you can define different idle framerate limits for different apps.

 

You don't need to relaunch RTSS, profile is read on 3D application start so it needs to be relaunched instead

 

Some development news.
Some new card with some new GPU just arrived to my home PC. Which means that I have approximately 1 week to play with it till NDA lifts and possibly improve something on MSI AB side. Current version of MSI AB (4.6.0 beta 8, which MSI will also provide to reviewers) already provides full support for new GPU family, but during this week I'll be able to experiment with one more feature - new NVIDIA overclocking scanner technology and possible include it into MSI AB.

 

0 = disabled, it is reflected in context help for it

 

"Reset order" does exactly what it is supposed to do, it is resetting the list and order to default state. Framerate related graphs are supposed to be off by design. 32 threads is NOT a MSI AB limitation. Settings window is not resizable and won't be, sorry.

 

I was a bit skeptical about new automatic overclocking technology recently introduced by NV, but after getting the card installed here and after playing with NVIDIA scanner technology and API during a couple days I may say for sure that we'll have NVIDIA scanner supported in MSI Afterburner. Actually, support for it is already implemented so MSI will probably provide this beta to reviewers and you'll be able to read about it a few days later when NDA lifts:



Stay tuned!

 

That's a process of searching for the best stable overclock.

 

You almost _never_ see real voltage monitoring and typically see target VIDs instead. Real voltage lower/higher than it is supposed to be confuses noobs to death.