Rainmeter Forums

Nightliss wrote:After an update gadget shows correct temp for cores 1-4 but for 5-8 it shows distance to max temp

ss.jpg

Before it showed correct same temp for core 1-2, 3-4, 5-6, 7-8 as it should.

Huh... I accidentally overrode the threadsPerCore variable in the script with a 1. I'll have to release a patch.

In the meantime, you can fix it yourself by navigating to ModernGadgets\@Resources\Scripts\Config\CpuConfig.lua. On line 80 it should say threadsPerCore = 1. Murder it. Kill it with fire. After saving the file, go to ModernGadgets\CPU\CPU.ini, and change threadsPerCore=2 on line 34 to threadsPerCore=1. Save the file, middle-click CPU meter, and it should be fixed.

EDIT: I HAD FIXED THIS BEFORE, BUT GIT WAS STUPID AND IT REAPPEARED. WHYYYYYYYYYYY!!!??? #gitfail

I can't find it o.o
Ran search in whole ModernGadgets folder. Found threadsPerCore in /CPU/CPU.ini but changing it back to 1 from 2 doesn't seem to work.

Nightliss wrote:I can't find it o.o

ss.jpg

Ran search in whole ModernGadgets folder. Found threadsPerCore in /CPU/CPU.ini but changing it back to 1 from 2 doesn't seem to work.

You missed a step. You need to change that line that you did, as well as go into @Resources\Scripts\Config\CpuConfig.lua, and delete line 80.

raiguard wrote:You missed a step. You need to change that line that you did, as well as go into @Resources\Scripts\Config\CpuConfig.lua, and delete line 80.

line 80 starts if statement, deleting the line or whole block doesn't change anything.

Nightliss wrote:line 80 starts if statement, deleting the line or whole block doesn't change anything.

That is very odd. The LUA script is missing an entire function. Do a fresh install of v1.2.1.

raiguard wrote:That is very odd. The LUA script is missing an entire function.
2017-08-03 14_30_58-CpuConfig.lua — ModernGadgets — Visual Studio Code.png
Do a fresh install of v1.2.1.

Hmm seems like it didn't update properly. I'll do fresh install tomorrow. Thanks for help

Nightliss wrote:Hmm seems like it didn't update properly. I'll do fresh install tomorrow. Thanks for help

Well, I'm in the process of ACTUALLY fixing this issue, and I'll have a patch out tonight. Sorry about that, this is why I do betas (but apparently none of my 180 beta testers had this problem...). So hopefully you should just be able to install v1.2.2 and be done with it.

v1.2.2 - 2017-8-3
- ACTUALLY fixed core temperature issues
- Changed all author references to raiguard

Just updated MG on my pc at work. Works fine Thanks

Already updated to 1.2.2, but the update notification still appears after reboot. That happened in the PC of my work, and in my house.