Finally found some time to mess around again, I combined two pieces from the sysinfo script (see below)
For some reason the core 2 meter isn't running like core 1 what did I do wrong here.....
balala wrote: ↑September 5th, 2020, 3:39 pm
Perfectly agree. But if you need it, it probably does worth to dig into it.
Last edited by balala on September 8th, 2020, 11:26 am, edited 1 time in total.
Reason:Please use <code> tags whenever are posting code snippets. It's the </> button.
AdrianJC wrote: ↑September 8th, 2020, 11:21 am
For some reason the core 2 meter isn't running like core 1 what did I do wrong here.....
The [Core1Gather] and [Core2Gather] measures have both the same Processor=1 option, so both are returning the same information. I suppose on the [Core2Gather] measure, this option should be Processor=2.
Whahahahaha I totally overlooked that one thanks for you fast response.
balala wrote: ↑September 8th, 2020, 11:30 am
The [Core1Gather] and [Core2Gather] measures have both the same Processor=1 option, so both are returning the same information. I suppose on the [Core2Gather] measure, this option should be Processor=2.
Do you know what values rainmeter uses for reading the core(s), because the script starts with 1 to 8 but when I take a look
at SpeedFan it reads/uses core 0 to 7.
balala wrote: ↑September 8th, 2020, 11:30 am
The [Core1Gather] and [Core2Gather] measures have both the same Processor=1 option, so both are returning the same information. I suppose on the [Core2Gather] measure, this option should be Processor=2.
AdrianJC wrote: ↑September 8th, 2020, 1:35 pm
Do you know what values rainmeter uses for reading the core(s), because the script starts with 1 to 8 but when I take a look
at SpeedFan it reads/uses core 0 to 7.
AdrianJC wrote: ↑September 8th, 2020, 1:43 pm
BTW what would be better to use: SpeedFan or HWInfo?
I don't have a strong opinion on that. My only real axe to grind with SpeedFan is that it doesn't measure anything about the GPU, and that is of some interest to me. So I personally use HWInfo, although I readily confess that setting up the variables for HWInfo is quite a bit more complicated than SpeedFan. That isn't a particularly big deal for a skin you are using yourself, as you only have to do it once. If you are distributing a skin, HWInfo adds a level of complexity for your end-users that is hard to avoid.
jsmorley wrote: ↑September 8th, 2020, 1:48 pm
I don't have a strong opinion on that. My only real axe to grind with SpeedFan is that it doesn't measure anything about the GPU, and that is of some interest to me. So I personally use HWInfo, although I readily confess that setting up the variables for HWInfo is quite a bit more complicated than SpeedFan. That isn't a particularly big deal for a skin you are using yourself, as you only have to do it once. If you are distributing a skin, HWInfo adds a level of complexity for your end-users that is hard to avoid.
I dont mean to throw a tire on the campfire, but I use a combination of MSIAfterburner and CoreTemp - these are relatively easy to use and customise in rainmeter, and in the end the dual backend programs really dont impact on anything like performance or disk space.
So basically simplicity + complexity = freedom of choice, in this case.
Also, SpeedFan does not have an option to start with Windows so after every boot you have to manually restart it.
AdrianJC wrote: ↑September 8th, 2020, 1:35 pm
Do you know what values rainmeter uses for reading the core(s), because the script starts with 1 to 8 but when I take a look
at SpeedFan it reads/uses core 0 to 7.
I don't know about SpeedFan, I'm not using it, but on CPU measures, as you can see on the link posted above by jsmorley, CPU=0 is used for to get the average of all CPU cores, while CPU=1 and so on, to get specific core value.