CapFrameX OSD with RTSS

So, there's a limited amout of chars not only lines? Can you extend this for CX in RTSS please?

 

Using variables for the colors works fine.

 

@Unwinder
What is the relation between "NV_GPU_POWER_MONITOR_POWER_CHANNEL_STATUS_V2 channels[NV_GPU_POWER_MONITOR_POWER_CHANNELS_MAX];" and the enum "_NV_GPU_POWER_CHANNEL_POWER_RAIL"?

I would like to identify the entries.

 

What about RDNA2 support? Do you know the Overdrive version?

 

How can I use bar charts instead of relative numbers (core usages)? EmbedGraphs (RTSS_EMBEDDED_OBJECT_GRAPH_FLAG_BAR) are displayed at the end.

 

Is it possible to close RTSS via a specific shared memory instruction? We've tried C#'s Process.CloseMainWindow but doesn't work.

 

If MSI AB is running, too it will restart RTSS when closed.

 

MSI AB isn't running.

 

How can I use a command line within my C# code?! Or did I miss something?

 

To better explain what we're trying to do: Some people might want to bench without the overlay running due to possible performance impacts but still want to use it when they are not currently benchmarking.

So we added an option that disables our own overlay infos when a capture is running and enable it again when the capture is finished.

To be completely safe in terms of any possible performance impact we'd like to also close RTSS completely and start it again when the capture is finished.

I can start RTSS with "proc.StartInfo.Arguments = "-u" " but Close() or CloseMainWindow() don't work and I don't want to use Kill()

It works with "proc.Kill()" at capture start and "proc.Start()" at capture finished but with this every time RTSS is killed it's tray icon remains and the user is left with dozens of RTSS icons after some benchmarks^^

And "proc.CloseMainWindow()" only works when the RTSS window is open but not when its minimized in tray.

 

That's why it would be an optional setting^^
I don't think many users would even use it, but if there are problems with a specific application, the user that wants to use this option would then close RTSS manually anyway.

Another option would be to use the global OSD toggle in RTSS, I'd assume there's not much left that could impact performance if this is off.

Right now we can disable/release our own overlay with our hotkey and in case the option is enabled automatically for the duration of a benchmark, keeping other clients visible.

Could we also use a command when a benchmark is running to toggle the global OSD switch like the AB hotkey does or is this only possible through AB?