![]() ![]() However as said just to form better habits, which in future might be useful, using the brackets is indeed a good idea (same way as enclosing the values set through bangs into quotes). ![]() IfTrueAction=!SetOption TempMeterBar BarColor 0,0,255,255 is same well as IfTrueAction=. For all the Window PC enthusiast out there, these CPU Rainmeter Skins feature to show processor system info and stats. If only one single bang is used, it works even with no brackets. If you have anything more than 2 cores and 2 threads, do let me know how it works. I made this skin that provides a per-core monitoring ability that supports an infinite (theoretically) amount of CPU cores. You can change the skin size and place the skin anywhere on your desktop. One note - framerate will be zero unless you are actually. The difference in the CPU used, and how smoothly other things in Rainmeter work when this is running, is dramatic. Check all the things you want monitored like Power, GPU temp, GPU usage, Fan speed, Core clock Memory Clock, Memory usage, Framerate, GPU voltage. ![]() In addition to that, go to the afterburner settings and go to to the monitoring tab. Because this rainmeter skin will show you your computer CPU usage on your desktop. MSI afterburner has to be running for the skin to work. If you want to set such a condition into another measure, you have to use the name of the measure explicitly.Īlthough this always is an excelent idea, it's not mandatory. Advanced CPU monitoring UPDATED 22/10/18 by kyriakos876 » Sun 5:37 pm. If you like to keep yourself about the CPU usage of your computer all the time, now you will not have to open task manager every time. Maybe you can use or adapt the skin you want to your personal taste :) Reply reply More replies. hello all, I am new to this lua Scripting and rainmeter. They have all of their skins separated (CPU, GPU, ram, etc.). Note that this works ONLY if the condition is set into the same measure. Get help with creating, editing & fixing problems with skins. For instance the above IfCondition might be: IfCondition=#CURRENTSECTION#40) & (#CURRENTSECTION#<=46). That's why it is always a better idea to use the #CURRENTSECTION# variable instead of naming exactly the measure. Any idea what might be happening?īalala wrote: ↑ February 19th, 2020, 2:09 pm Won't change color at all after it turns blue. If it's anywhere over that initially, it stays white until it drops to fulfill that condition. The thing is, the color only stays blue when it registers temperature measure <=40. Values I took for my processor from here: IfTrueAction5=!SetOption TempMeterBar BarColor 255,0,0,255 IfCondition=MeasureMaxTemp40) & (MeasureMaxTempColor46) & (MeasureMaxTempColor60) & (MeasureMaxTempColor71 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |