First thank you very much for this new version of such a great tool! But I have to report something weird regarding CPU cores temperatures. I have a 7700k with 4 cores and I have noticed a big difference in temperature with one the cores compared to another great tool such as HWINFO. I did a screenshot bellow where you can see the difference in temperature for the third core (I removed the other 4 threads temperatures reports because they have the same value as 4 cores) Here you can check the "CPU5" in Afterburner is 5° colder (77°) than the same "Core#2" in HWinfo (82°) : Which one is correct? It looks to me that HWInfo is more accurate, but can't prove it. Something else weird in Afterburner is cores 5 and 7 temperatures are linked together but in the opposite way: when one has a pic then the other has the same pic but in the other way...
It is rather hard (if not say impossible) to misread DTS just for one thread, but I cannot prove it too. CPU temperature monitoring implementation in CPU.dll plugin is also open source and included in SDK, so you may try to find the reason there.
Why still and why would it magically start controlling it? It is proprietary and undocumented EVGA's PWM controller, how do you imagine to see support for that in MSI AB? Primary GPU fan controllers for both NVIDIA and AMD cards are supported and directly controlled inside NV/AMD drivers, all critical safety measures as fan stop control, access synchronization for multiple software tools etc are implemented there. EVGA decided that they don't need all that and used additional own controller, invisible to standard NVIDIA fan control software infrastructure. Which means that any software needs to access undocumented fan controller directly at low level in order to work with additional fans. That's not something you can expect to see either in AB or in any other NVIDIA software fan controller - too much development cost to pay because of one vendor's exclusivity tricks.
Just thought Id throw this out there but this version of Afterburner made my previous overclocking settings unstable. I'm not sure what they changed in this version that would do so but beware.
No chances and zero changes in this area, sorry. I’m seeing similar reports with each new version during 20 years of RT development and that’s what is called “placebo” effect. I’m pretty sure that even if I’ll re-release exactly the same binary as a new version I’ll receive the same feedback.
Can you guys add some sort of GPU grouping in your options area for what metrics are displayed on the graphs? The current method of scrolling through a massive list is very tedious and it's often that the metric i'm looking for is hard to find
Sorry, not my cup of tea, but i can help of your with interface and user friendliness design. Dont take it wrong but sometimes is a bit linux like mess.. and make tools as easy to use as possible is always good.
@Unwinder Please and @Hilbert Hagedoorn, thanks for the release. Can you add VERY IMPORTANT THINGS in the next MSI AB update?: 1. Horizontal scroll bar for EVERY separate graphs column. I have huge wide monitor and always divide Hardware Monitor window onto 3 or 4 columns. When I do benchmaks for a long time I can't see previous sensors data which "hiding" outside HW monitoring window and it's really annoying. Assume that I'm not the one man only who want to have ability to scroll through long data graphs. Please, ADD IT! 2. Independent OSD and HW monitor graphs sequence. I mean, to have ability to configure the OSD independently without changing HW monitor graphs sequence. In previous AB version when I move "Frametime" graph to the OSD's bottom it moves from 1 to the last one HW monitor position which messes up all my HW monitor graphs structure. Fix it, please. 3. Will be soon... P.S. I know that you (Unwinder) are Russian man, hope you understand my request. If not exactly, so... Алексей Николайчук, пожалуйста, добавьте вышеуказанные функции для улучшения и облегчения пользования программой. Спасибо за внимание! Hope, it's right translate to your primary language. =)
I dont use this often as i use to but, it still one first things I install on my pc on clean installs of windows, These days I only use it when I change gpu change drivers or get new game and want to see what FPS i get. Either way it my go to program for this stuff, Kudos to Unwinder
Any plans to add the fixed throttling option to RTSS suggested some months ago? A profile file option would be enough for this. Something like: ThrottleTime = n If non-zero, then the FPS limiter should do a busy loop for n milliseconds (or microseconds) if the target frame time was exceeded for the current frame (meaning the game didn't hit the frame cap for the current frame.) I hope this would be rather trivial to implement and it would help a lot for g-sync/freesync users, as well as for vsync off users, as it reduces input lag quite a bit for GPU-bound games.
Hehe, impatient thread bumper I'll add it in the next beta of RTSS and drop you PM to test it when it is ready.
Nice update, especially the ability to customise "data source"/"data provider" settings. However, I have a request. Please, can the ability to customise internal source also be added?
Like the image below, but for the internal source data. The thing I want to do in particular is to edit the "Power" internal source. Instead of a percentage, I want it to reflect TDP in Watts derived from that percent. If we had customisation, like below, for internal data then it would be possible. Or maybe I'm not understanding and it's possible to already do what I want? Also, can you explain what "Type" in "Plugin data source properties" does? It doesn't seem to change anything. I understand the text boxes, but the "Type" dropdown menu seems to not change anything.
You won't be able to override displayed units for internal sources, but you can use correction formulas to achieve your goal (i.e. convert power to watts via multiplying power usage percentage by power limit). "Type" field for a plugin specific data source identify data source type so third party applications (e.g. sidebar gadgets, rainmeter plugins, Android/iOS applications conntected to AB via remote server etc) can always know that they are reading CPU temperature (for example) without parsing data source name (which can be customized by user as well). OSD layouts are also using those types to apply different text formatting style to different items.
Thanks for the explanation. Yeah, I'm already using a correction formula to get the TDP in W, but it's displayed as % since there's no way to change units, which bugs me a little bit. It's not a big problem. Just wanted to see if I could request a feature. You'll never get anything if you don't ask, right? Thanks for responding though, amazing software regardless.
thank you for the new update! anyone else have a problem with RTSS 7.1.0 and the new nvidia driver 397.31? one game I play wouldn't launch anymore and just went whitescreen. creating a profile for it in RTSS with application detection level none (turning it off for this game) was the only fix. Then another game the OSD would come on but would stay on and not toggle per the hotkey I had set. I used DDU and rolled back to previous 391.35 and everything is working perfectly again. This new driver must have something going on which is conflicting.