MSI AB / RTSS development news thread

Bad luck for you. I use build number info displayed in tray icon tooltip frequently myself, so it won't change.

 

RTSS 7.3.2 Beta 2 Build 24797 is available for download. Changes list includes the following:

o Added new <RES> hypertext tag, allowing displaying framebuffer resolution in On-Screen Display
o Added new <ARCH> hypertext tag, allowing displaying application architecture info (x64 or UWP) in On-Screen Display
o Added new <API> hypertext tag, allowing displaying application 3D API info in On-Screen Display. This tag is quite similar to <APP> tag, but unlike existing tag it displays full 3D API name instead of abbreviated one (e.g. OpenGL instead of OGL)
o Added new <TIME=format_string> hypertext tag, allowing displaying custom formatted system date/time in On-Screen Display. Please take a note that format string is not validated due to performance reasons, so it is up to client to perform the validation
o Slightly altered geometry batching implementation in On-Screen Display renderer. Previously RivaTuner Statistics Server internally represented On-Screen Display contents as a few uber batches, containing all On-Screen Display geometry grouped by primitive type (for example, the first batch containing triangles representing all On-Screen Display symbols, solid color bars, and embedded images and the second batch containing all lines used to render all graphs). Such batching provides optimal rendering performance and minimizes draw calls count and rendering pipeline state changes. With such implementation it was possible to render On-Screen Display contents in expected Z-order for the same type of graphics primitives (e.g. for text, images or solid color bars), but line primitives were always rendered on top of everything. New altered geometry batching implementation allows splitting uber batches on smaller batches, so it is now possible to render both lines and triangle primitives in expected Z-order. Please take a note that batches splitting mode is enabled by default, but power users may enable old uber batch rendering mode at profile level if necessary

https://download-eu2.guru3d.com/rtss/[Guru3D.com]-RTSSSetup732Beta2Build24797.rar

New MSI AB beta is also around the corner. It will include the following changes:

o Added experimental support for Intel 11th generation CPUs
o Added experimental support for mobile AMD Ryzen CPUs
o Increased memory overclocking limit for NVIDIA GeForce RTX 30x0 series graphics cards

 

Small note on new <TIME=format_string> hypertext tag. Only legacy time format specifiers supported by VC++ 2008 runtimes are allowed to be used in the format string. You can find the list of legacy specifiers online, for example here (legacy ones are in white, newer ones are in yellow). As it is reflected in the release notes, format string is not validated in realtime due to performance reasons, so it is up to you to ensure that you specify only supported specifiers there.

 

@orangewoolcry

Please no need to turn this thread into one more “modify my OSD for me” place. MADFLOR’s thread is sadly almost dead, thanks to endless “requests” spammed there.

 

MSI Afterburner 4.6.4 Beta 2 build 16079 is available for download. Changes list includes:

o Added experimental support for Intel 11th generation CPUs
o Added experimental support for mobile AMD Ryzen CPUs
o Increased memory overclocking limit for NVIDIA GeForce RTX 30x0 series graphics cards
o RivaTuner Statistics Server has been upgraded to v7.3.2

https://www.guru3d.com/files-details/msi-afterburner-beta-download.html

Please take a note that experimental support for Intel 11th generation CPUs was added blindly without such hardware here, so I'm not sure if it is working properly yet.
Also I remind third party webmasters that it is internal beta, which is not intened to appear in news. No need to link it please.

 

No, of course I cannot do it. Passive waiting mode in fps limiter is timer events based, preceise timing and high timer resolution is a must for that.

 

It is not a smart decision at all. If you don't want to use passive waiting and framerate limiter with lower CPU "usage" becasue of mandatory high timer precision, you can totally disable passive mode and return back to active busy-waiting implementation.

 

It is not specific to new release. This feature was added to V/F curve editor more than 2 years ago, in 4.6.1:

 

I said that it is mandatory and I have nothing to add to it.

 

My intended usage is explicitly documented in the release notes, it is framebuffer resolution. Your hopes are not in sync with reality because you confuse framebuffer and render target resolutions. And no, I won’t be tracking dynamic render target resolution for games using internal resolution scaler because detection implementation is specific for each game. While it is “super useful” from your POV as a user, it is complete jar of worms in terms of development and compatibility. Forget about it.