I add: the tool HWMonitor gives a yet further different value for the CPU temp, though one that is considerably closer to the value that Speccy reports than to the value that Rainmeter is reporting-via-CoreTemp (!).I have been stuck on this issue for a while now. Perhaps the updateDividers do have something to do with that. The difference between (1) what Rainmeter says when the PC has been rebooted, and (2) what Rainmeter says when the PC has been rebooted and the relevant skin refreshed - that difference perplexes. So I cannot directly compare CoreTemp's UI to that which Rainmeter pulls from CoreTemp. CoreTemp seems to lack the ability to show the mean temperature of the cores. CoreTemp has a particular (adjustable) polling interval Speccy's interval appears to be one second, but even when I set the CoreTemp interval to one second, the Rainmeter-Speccy discrepancy persists. And once I had done that, Rainmeter seemed to over-report the CPU temperature. Just now I tried commenting out those UpdateDividers - thereby leaving the update divider for the relevant measures to be set by this line earlier in the script: Update=1000. Yet, does the code shown immediately really above update the measures for the individual cores? Might the problem be those instances of UpdateDivider=-1? I forget why I have them.Īnd Rainmeter's output for the CPU temperature does change over time. (update divider x update ) should not be less than CoreTemp's 'temperature polling interval'.įormula=Round(( measure_cpu_temp_firstCore + measure_cpu_temp_secondCore + measure_cpu_temp_thirdCore + measure_cpu_temp_fourthCore ) / 4)
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |