- Joined
- Sep 23, 2016
- Messages
- 18 (0.01/day)
Processor | Core i7-12700K |
---|---|
Motherboard | Gigabyte Z690 Aorus Master |
Cooling | Noctua NH-D15S |
Memory | 32 GB G.Skill DDR5 |
Video Card(s) | MSI RTX 4070 (Gaming X Trio 12 GB) |
Storage | WD_Black SN850X 2 TB NvME |
Display(s) | LG 32GP850B 32" UltraGear QHD (2560x1440) |
Case | Fractal Design Define 7 |
Audio Device(s) | Creative Sound BlasterX AE-5 |
Power Supply | Seasonic TX-850 |
Mouse | Cobra RedDragon |
Keyboard | Corsair K95 RGB Platinum XT |
Software | Windows 11 Pro 64-bit |
This is probably for @W1zzard, but anyone that knows the answer (or part of it) is welcome to chime in. 
On my RTX 4070 with current NVidia drivers, the sensor called "PerfCap Reason" has the usual [double] floating-point values, but of course doesn't display those, instead displaying one of the following 5 strings: Pwr, Thrm, VRel, VOp, Idle.
I of course only see "Idle" on my system - which seems to correspond to an in-memory value field of 16... taking a large leap of faith (and guessing), I have the other values as being 1, 2, 4, and 8 for Pwr, Thrm, VRel, and VOp, respectively.
I obviously concluded from the "16" that these are binary flags - was I correct? Or is the author (W1zz) willing to divulge the actual mapping used between the reported in-memory double values and the displayed "PerfCap" reasons?
For anyone interested in "why" I ask, I have had an open source "docklet" for the ObjectDock ecosystem for about 20 years now, am in the process of doing some updates and house cleaning, and noticed I wasn't displaying anything for this field.
Thanks!

On my RTX 4070 with current NVidia drivers, the sensor called "PerfCap Reason" has the usual [double] floating-point values, but of course doesn't display those, instead displaying one of the following 5 strings: Pwr, Thrm, VRel, VOp, Idle.
I of course only see "Idle" on my system - which seems to correspond to an in-memory value field of 16... taking a large leap of faith (and guessing), I have the other values as being 1, 2, 4, and 8 for Pwr, Thrm, VRel, and VOp, respectively.
I obviously concluded from the "16" that these are binary flags - was I correct? Or is the author (W1zz) willing to divulge the actual mapping used between the reported in-memory double values and the displayed "PerfCap" reasons?
For anyone interested in "why" I ask, I have had an open source "docklet" for the ObjectDock ecosystem for about 20 years now, am in the process of doing some updates and house cleaning, and noticed I wasn't displaying anything for this field.

Thanks!