Hello Martin!
The problem is of this nature. RivaTuner cannot load data sources from HWiNFO64 version.
From the HWiNFO32 version, data sources are loaded without problems.
I got this error after running HWiNFO64 7.22, now older versions don't work either.
I turned it on once, but then reset the settings.Do you have the "Shared Memory Support" option enabled in HWiNFO64?
HWinfo Pro user here. I have a more specific question which goes beyond the common OSD; I'm talking about the "new" RivaTuner Overlay Editor, which only gives the possibility to add the current live status of any value (so no max, min, avg). I was thinking, since it doesn't seems possible to circumvent the issue from the Overlay Editor side, is there a way (for example) to mock the max (or avg, min) value as current live value from the HWinfo's side and then feed it to the Overlay Editor? Or any other solutions? Thank youHWiNFO32/64 now introduces the support of RivaTuner OSD (Statistics) Server which allows displaying of any HWiNFO32/64 sensor values in DirectX applications/games.
The OSD Server is part of one of the following packages:
- RivaTuner (no longer updated)
- MSI Afterburner
- EVGA Precision
Download the latest HWiNFO32 or HWiNFO64 version (v3.81 at least).
Besides HWiNFO32/64 you need to have the OSD/Statistics Server running as well. This is included in any of these packages: RivaTuner or EVGA Precision or MSI Afterburner. Download one of them (any you prefer) and start the Statistics Server before opening HWiNFO32/64 Sensors.
In HWiNFO32/64 go to Sensors/Configure and set your preferred values to be included in the RivaTuner OSD - for each value needed to be shown in OSD click "Show" in the RivaTuner OSD section.
Submit feedback
Many thanks to Alex (aka Unwinder) for making this possible !
HWinfo Pro user here. I have a more specific question which goes beyond the common OSD; I'm talking about the "new" RivaTuner Overlay Editor, which only gives the possibility to add the current live status of any value (so no max, min, avg). I was thinking, since it doesn't seems possible to circumvent the issue from the Overlay Editor side, is there a way (for example) to mock the max (or avg, min) value as current live value from the HWinfo's side and then feed it to the Overlay Editor? Or any other solutions? Thank you
Yeah that's what I ended up doing at last, even if it screwed a bit my layout since it isn't aware of the layers that I created in the editor, but one way or another I managed to match the two things. Thanks for the quick reply.You can achieve this also the other way around - by letting HWiNFO push data straight into RTSS where you can choose which value type will be used. This is available in the OSD (RTSS) tab in sensor settings.