![]() ![]() 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 (!). 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. The skin uses CoreTemp for temperature readings, which mean the measurements, are recorded per core and not per thread. To launch the Settings dialog again, just right-click on any widget or the top bar and choose Gnometer > Settings.ini from the. You can also edit or refresh the skin from this menu if you choose. 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. The Dynamic CPU Core rainmeter plugin makes the process of checking your CPU performance and CPU temperature simpler just by looking at two independent and scalable radii. To close it, you’ll do it the same way you’ll close any Rainmeter widget, by simply right-clicking and choosing Close Skin from the menu. 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) Jsmorley wrote:First you need to know which application and corresponding Rainmeter plugin a skin is using to measure sensor values. It will always take some work on your part to match up the skin with the correct application, plugin and settings for your system. The long and the short of it is that NO skin you download is ever going to work for measuring hardware sensors out of the box. It all depends on what the skin you're using expects, running the correct application, and then some tweaking of the options in the skin to match things up with your actual hardware. So there is no simple answer to your question. what is going on is that the actual application, CoreTemp, SpeedFan, HWiNFO, etc., do the measuring, and the matching plugin for Rainmeter is able to get the results from the application to use in a skin.ģ) You will then need to look at the instructions for the desired Rainmeter plugin, to see how you tell your skin which specific sensors (it will vary wildly depending on the application/plugin and your system) you want to measure, and how you set the options in the skin to do so. ![]() ![]() Rainmeter does not and cannot measure sensor values. This is a 3rd-party plugin, that must be downloaded and installed in Rainmeter prior to using it in a skin: These come with Rainmeter and are ready to use: One of these applications must be running on your system while the skin is loaded.Ģ) Use the appropriate Rainmeter plugin for the application you are using: First you need to know which application and corresponding Rainmeter plugin a skin is using to measure sensor values.Īt its most basic, the way you use Rainmeter to measure hardware sensor information is:ġ) Run an application on your system that measures these values. ![]()
0 Comments
Leave a Reply. |