Download: MSI Afterburner 4.5.0
Click here to post a comment for Download: MSI Afterburner 4.5.0 on our message forum
Unwinder
We'll also provide standalone installer of RTSS 7.1.0 and make it visible to Guru3D update servers a few hours later. Making 4.5.0 itself visible to MSI update servers can take a bit more time.
Stay tuned!
Netherwind
Thanks Unwinder! Also thanks for the preview video.
metagamer
Thanks, nice shiny update.
SpajdrEX
Thanks for update mr. Unwinder!
Unwinder
Hope that's not a typo and you indeed mean shiny 😀
Singleton99
Thank you Unwinder 🙂 🙂 🙂 for your hard work and keeping Afterburner updated and constantly adding more features
Unwinder
There are no known issues requiring any changes to make it work with AMD drivers. And there are zero changes in this area, sorry. Every single change is documented in the release notes.
Angantyr
Greatly appreciated.
Process specific memory monitoring with PerfCounter plugin
That feature is absolutely golden.
xxela
Great software Unwinder! Thanks for your hard work.
P.S. Does anybody know how to monitor a specific process cpu usage?
GroinShooter
Once again, greatly appreciated Unwinder!
JOHN30011887
Thanks again, all working perfect as usual 😀
Unwinder
No, it is not a known issue. Works fine here and there were no changes in AMD API. No changes in this area are expected.
Unwinder
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.
Unwinder
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.
JonasBeckman
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.)
Unwinder
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.
Unwinder
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.
xxela
[SPOILER][/SPOILER]
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]http://oi65.tinypic.com/2j1lso7.jpg[/SPOILER]
Unwinder
You misunderstood interpretation of "% Processor time". It is documented here, for example:
https://social.technet.microsoft.com/wiki/contents/articles/12984.understanding-processor-processor-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).
ruthan
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..
