I happen to run HWinfo64 version 7.0 (portable) and noticed after running that AB monitoring screen doesn't seem to load data I have set up with the plugin, which works with the older versions of HWinfo. The OSD onscreen does show values in games/3d app's and the 32bit version 7.0 works fine, seems only the 64bit has the issue for me. Looking at their site they went premium now (HWinfo64 and HWinfo64 PRO) but it does say 12hrs limited time on shared memory so not sure what's going on there. https://www.hwinfo.com/licenses/ Was just wondering if others see the same thing.
It clearly says the following: "4 HWiNFO64 (non-Pro) has a time-limited Shared Memory support to 12 hours. When this limit is reached during run-time, this feature will be automatically deactivated (and requires manual enabling again)" So it looks like a way to stimulate Pro license purchase. Sad day.
right, but as soon as I DL it and ran it this showed up, maybe a few mins running max, nowhere near the 12hr time-limit. Oh well, the older versions work fine for me and the 32bit new one as well. I thought maybe the plugin needed a tweak or something to fix.
Probably you're confusing something, according to HwInfo FAQ shared memory interface is _disabled_ by default now, so it couldn't show up as soon as you DL it, it requires you to enable it now. When it is disablied after 12 hour usage period, it is also notifying you with a message (this notification message is a reason of making it disabled by default according to the same FAQ).
Yes, I found the option in settings when you first start it. https://www.hwinfo.com/forum/threads/msi-afterburner-plugin-not-working-after-update.7132/ So is working except for the timelimit.
Q: What were the reasons behind limiting the SHM also for personal users? A: Current requirement for allowing other applications to use SHM is that the product must be an unconditional freeware while keeping the interface details closed. The main reason behind this is not to allow commercial products to make use of (and earn from) a freeware product. However this was difficult to meet for many projects - open-source projects to keep a part of code closed, or projects that were somehow related to commercial products or were earning even indirectly. Moreover, some subjects have attempted to circumvent the SHM restriction and use it for commercial purposes by utilizing illegal methods. So the new SHM model is uniform without implementation restrictions and allows full disclosure of the interface. I also believe that a 12-hour limit on SHM is sufficient for most personal users and will deter some of the commercial usage. Q: Why will the default value of the "Shared Memory Support" configuration option change from Enabled to Disabled? A: This is to avoid disturbing users that don't use the SHM (a majority) with the automatic SHM deactivation notification.
Cannot say that I completely like this decision, but that is your weighted decision and your choice. At least people selling commercial RTSS clone will benefit from it and happy to see less free alternatives on the scene. I'll keep following "free monitoring for everyone" paradigm.
Exporting data from HWiNFO64 into RTSS (unlike the MSI Afterburner plugin) is not affected and still can be used free and without limit (except commercial purposes). I'm evaluating the impact of this decision and perhaps there might be some exceptions in future... My only concern for now is to restrict commercial usage for which the existing SHM was a nice feat for a massive/automated deployment in commercial environments.
I understand the reasons behind it. Exporting data from HWiNFO64 into RTSS is not affected, but built-in RTSS OSD formatting GUI inside MSI AB, AIDA or HwInfo is rather oldschool and basic. That's why more complex and universal hypertext editor and multi-provider, RTSS OverlayLayout plugin was added, but it will be effectively invalidated with such limitation (for those who wanted to use HwInfo+RTSS combo).
This decision seems to break StreamDeck's plugin, so that's great. Not quite sure how they are making money from this plugin but hey.. your decision, right? I rather think that blocking the use of 'shared memory' in order to stop 3rd party apps from getting the data that I want to see without having to use the interface for the actual app is just an excuse for hiding one of the most useful and well-used features behind a paywall.
Hey sorry for responding to such an old post, but was wondering if this issue was ever solved in some way? I saw that they allowed rainmeter to pull data from the registry instead of using shared memory: https://forum.rainmeter.net/viewtopic.php?f=127&t=37160 I love the customization available from RTSS's Overlay plugin but there are a few values that aren't available in its built in hardware support that are available in hwinfo, but having to manually enable support for it each time I play a game is annoying to say the least. Is there another work around? I know I can use version 6.43 beta, but its missing some of the GPU sensors/values that were added in 7+ that I'd like to include in my overlay.
I understand that, but it seemed like you weren't happy with that situation, and while its handy to have some of the extra sensors, it doesn't seem worth the price. Since he had done work arounds for other software like rainmeter I was wondering if something was available here as well. Like you said yourself, it works with the older RTSS / Afterburner overlay, but doesn't support the new and better overlay editor.
The "workarounds" mentioned above are not full functional replacements for previously existing functionality, otherwise it won't be unlocked in free version. Attempt to use registry to access sensors in performance critical realtime monitoring solution is just insane from performance point of view, shared memory interface is faster by FACTOR. So it is a no go. And honestly I find it absolutely frustrating that you beleive that buying HwInfo doesn't worth the price for YOU, but at the same time expect me to find workarounds for you. So I'll need to pay it by my time instead.
Again, it seemed like you were not happy that it wasn't interfacing with your new overlay. I never asked you to find a work around for it or demand you do anything. I know using the registry isn't a good work around for RTSS, I mentioned that the HWINFO developer realized that forcing users to buy it for things like Rainmeter was bad, so made a work around for those users. I was simply asking if anything similar had been worked out between you and him to support the new overlay features in RTSS. I took that as you weren't happy with the limitations so asked if there was some change sine 2021 when this was originally posted. Thats fine with me if there isn't, I just won't use the extra sensors or will manually enable it if really needed when testing.
It doesn't matter if I like it or not, it is not my decision, not my limitation and not my software product to decide if it needs to be available for free or not. There was no progress and no changes in this area.
