No, it is not the case and you’re not supposed to do so when upgrading AB/RTSS to newer version. But it can be the case after major OS version upgrade, in case if RTSS injection cache gets damaged.
Attached video is demonstrating specific process memory usage monitoring in details, step by step. The same approach can be used for other process specific counters like CPU usage, handle count etc.
The added option to delete the cache should be fine I'm assuming. After upgrading to a new Windows 10 build RTSS tends to pop up a warning prompt (EDIT: First time it's run that is.) about the hook not initializing properly and a compare of the config file at this point will generally have the cache addresses as 000000 I believe, restarting the software usually corrects it and if not a reboot will but now with the option to delete and rebuild the cache since a few versions back that too should work. EDIT: This thread moves fast. (EDIT: And some cumulative update changing the DirectX files will usually see the address modified but I've never gotten a warning prompt from RTSS and it just handles it, cleaning the cache after major updates couldn't hurt though.)
Alright, I'll keep that in mind for whenever MS releases 1803 to the public, if things do go weird. I don't mind doing "clean installs" its just that it requires a little more prep on my part first, remember settings and such.
So what's your suggestion that I can get it work? Right now it's like I adjust power limit to 50%, click apply, the slider jump back to 0. Same to the core and mem: I change the number, click apply, everything revert back to default. Appreciate your help!
Yep, resetting the cache via options will also do the trick. "Clean install" is just faster way to instruct a user. Those are two different cases and two different situations. The first one is the message you mentioned, it is displayed when RTSS is started into a sandbox environment for a first time and it see that some system software (e.g. antivirus) is trying to replace DirectX runtimes with proxy libraries on the fly, so offsets for injection cache cannot be detected reliably. Upgrading DirectX files to newer versions is a different case, it is normally handled transparently for end user and RTSS should redetect the offsets without displaying any notifications.
Sorry, I gave up on "how do I configure AB" questions in the forum, probably somebody else can help you. I'm focused on development related things only.
I wached the video and I tried for process memory usage monitoring and it worked fine but when I chose "processor time" option for the specific process it show me only 100% Spoiler
You misunderstood interpretation of "% Processor time". It is documented here, for example: https://social.technet.microsoft.co...rocessor-time-and-process-processor-time.aspx It is a total CPU usage across all logical CPUs. So if you have let's say 8 logical CPUs then it is measured in 0-800% range, so to convert it to 0-100% you should define divider as 8. Also, don't forget to enable dynamic mode for this counter (it is disabled on your screenshot). Otherwise the graph won't appear if you start MSI AB without target process (bf1.exe) running in background (dynamic counters are not validated during creation).
I kinda miss the early days where Afterburner was been developed(I mean before it reached a stable/final state) and we or at least I, was waiting impatiently for every new revision/release! I say that with the utmost respect! Thank you Unwinder!
Did some testing, not all processes are listed or could be monitored in PerfMon - for example not works on Kingdom come (i tried write procces name and pid too)- and GUI, need adjustment to be more fail proof - empty input boxes are fail - there should be comboboxes with predefined options..
Many thanks to Guru3D, Hilbert, and the innovative Unwinder. I really appreciate these ongoing Afterburner updates!
Anyone else having trouble getting the new metrics for 1%, 0.1% and min/max/average frame rates to show in the osd? For the life of me I can't seem to get them to work...
PerfCounter plugin is fully open source, you're free to locate and fix the problem if you beleive that not all processes are being listed or empty input boxes are "fail".
It is not new for this version and it was repeated a few times in the forum that fps min/avg/max/1/0.1 statistics are available in benchmark mode only. Start a benchmark with assiciated hotkey.
That's not called averaging, you're talking about rounding and using different output format. Currently output format override is supported for plugin-specific hardware monitoring data sources only, built-in sources always output data as is. So if you're displaying power usage via any plugin you can change format to "%.0f".
