MSI AB / RTSS development news thread

Framerate/frametime displayed by "Show own statistics" is redundant functionality, it will unlikely get any new options because I plan to deprecate and remove it from GUI one day. Initialy it was intended to provide minimalistic FPS/frametime overlay for those who wanted to use RTSS as standalone solution without MSI AB. Now such functionality is fully covered by OverlayEditor and you can create any kind of minimalistic FPS overlays with it.
It is also by design of "Show own statistics" FPS overlay to hide itself as soon as any overlay client (MSI AB, AIDA, HwInfo or OverlayEditor) take control on displaying own framerate overlay and try to show anything related to application's framerate statistics (which includes <FR>, <FT>, <APP> tags)

On a side note: I had some spare hours during weekend to peek into DXVK/FarCry3 deeper and I think I see rather simple workaround to filter device creation/destruction spam on this game startup and get it working.

 

Alternately, I can offer it as a power user oriented option, so it won't be available in GUI but it will be possible to enable 3D API name display in "Show own statistics" overlay with config file edit.

 

It is not a question of correction formula, it is a question of different output value formatting. It should be done on plugin side, AIDA, HwInfo and PerfMon plugins I created allow customizing formatting, but I don't know if libre plugin supports that.

 

PerfMon won't help you, windows performance counters exposed by it do not provide access to mobo specific sensors like CPU tachometer.

 

I'd purchase PRO version of HwInfo or AIDA then. It is not that expensive and that's a good way to say @Mumak or Fiery thanks for his work.

 

It is not a known issue and I won't be peeking into it. And I'm pretty busy with Intel Arc now, sorry.

 

Dear forum visitors,

I experimented with Intel Arc support during the last few days and i'm happy to report that most of monitoring related functionality is already implemented and working in RTSS/OverlayEditor. So I guess we'll release RTSS beta with initial Arc support in the nearest days. After that we'll release MSI AB beta with Arc monitoring (monitoring only!) support soon. Fully overclocking capable MSI AB beta is not expected at the moment, some things still need to be done from Intel side prior to that.

 

We're preparing RTSS 7.3.4 Beta 4 Build 27054 for uploading, so it will be available for downloading soon. This is the first build with Intel Arc telemetry support in internal HAL of OverlayEditor.

Stay tuned!

 

RTSS 7.3.4 Beta 4 Build 27054 is online. The main and the primary change is Intel Arc GPUs support in internal HAL of OverlayEditor’s plugin, but besides that there are a few other additional minor changes mentioned in this thread above. I'll document full changes list a bit later. Grab it here:

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

 

Full changes list for RTSS 7.3.4 Beta 4 Build 2705 includes the following:

o Improved compatibility with Vulkan applications, using multiple coexisting swapchains (e.g. Godot v4 editor)
o Framerate limit is no longer displayed as blank field when using <Alt> + framerate limit field clicking functionality for some periodic refresh rate values, defined with arbitrary non-power-of-10 refresh rate denominator. Such periodic refresh rates are rounded to 3 decimal places
o Improved compatibility with Vulkan applications, creating multiple dummy Vulkan devices on different GPUs during startup (e.g. Far Cry 3 with DXVK mod)
o Added power user oriented config file switch, allowing displaying 3D API (either abbreviated or full) in framerate counter displayed by "Show own statistics" option
o Epic Games Overlay compatibility strategy is disabled by default now, it is no longer mandatory due to changes in recent Epic Games Overlay updates
o Frametime counter in shared memory is now buffered and no it longer updates dynamically during presenting the frame. Buffering is implemented to protect the counter from being asynchronously accessed by third party monitoring clients and prevent such client applications from reading incomplete frame timings
o Fixed Windows XP/Vista compatibility regress, introduced tn the previous beta due to adding debug module dumping feature
o Added Intel Arc GPU architecture support to internal HAL of OverlayEditor plugin
o Added special stub data source to internal HAL of OverlayEditor plugin. This data source is not bound to any physical sensor so it doesn't consume any CPU time by polling hardware. You may use stub sources to implement some virtual sensors implemented purely via correction formulas and referencing other data sources only (e.g. total power consumption represented as "CPU power" + "GPU1 power" + fixed_delta).
o %VRAM% macro is now aligned to closest 0.5GB boundary in OverlayEditor plugin
o Updated built-in profiles list

 

Yep, it is a part of changes list. Thanks for confirming.