HWINFO64 has a more rudimentary alternative to Shared Memory option.
Would be nice to have support for reading sensor values from Gadget reporting since Shared Memory works on a trial-based 12H limit for the free version.
The data is being written and update by hwinfo46.exe inside registry key [HKEY_CURRENT_USER\SOFTWARE\HWiNFO64\VSB]
The structure is pretty simple :
LabelX: The user-friendly name. Respects user custom labes.
ValueRawX: The value reported by HWINFO64
ValueX: Same as ValueRaw but also reports measure unit.
SensorX: The root sensor name from where the 'Label' and 'Value' are coming, used for further identifying unique sets.
Where X is the Index, a progressive number assigned at the moment of enabling value reporting for a sensor.
Such Index ID is not user modifiable but it is user readable from the setting window during configuration.
If X is provided by the user inside the plugin configuration it should be pretty easy to read the values and use them for Game Activity sessions. For example reading the FPS value after exposing it through HWINFO64 (as this is the only value I am missing)
There is an exception to be handled:
While hwinfo64.exe is not running the VSB registry key is not present.
HWINFO64 has a more rudimentary alternative to Shared Memory option. Would be nice to have support for reading sensor values from Gadget reporting since Shared Memory works on a trial-based 12H limit for the free version.
The data is being written and update by hwinfo46.exe inside registry key [HKEY_CURRENT_USER\SOFTWARE\HWiNFO64\VSB]
The structure is pretty simple :
If X is provided by the user inside the plugin configuration it should be pretty easy to read the values and use them for Game Activity sessions. For example reading the FPS value after exposing it through HWINFO64 (as this is the only value I am missing)
There is an exception to be handled: