I have this setup for all parts of my skin.
But when all of the skins parts are hidden/disable/updatedivider=-1 rainmeter is still using some of my CPU. Compare to when I unload the skin where it's at zero of CPu usage.
I'm wondering if there is something I'm messing or if it's the way of rainmeter functionning.
Still new to rainmeter, so I'm trying to optimize the skin.
Last edited by Duschmoll on September 14th, 2021, 10:50 am, edited 2 times in total.
What's the value of Update in the Rainmeter section?
Do you have DynamicVariables=1 on the skin.
The full code could shed more light on your situation.
David8192 wrote: ↑September 12th, 2021, 6:41 pm
What's the value of Update in the Rainmeter section?
The value of the update is at 1000.
David8192 wrote: ↑September 12th, 2021, 6:41 pm
Do you have DynamicVariables=1 on the skin.
Yes I do have some DynamicVariables at 1. I've just tried to add [!SetOptionGroup Audio DynamicVariables "0"] to the skin, still using CPU
David8192 wrote: ↑September 12th, 2021, 6:41 pm
The full code could shed more light on your situation.
The Skin is 1220 lines, so quite larges for posting it here, I've put a part of the skin in question that I try to hide
In all MeterStyle= there is an updatedivider=-1 and no DynamicVariables
DynamicVariables= needs to be set as 1, not zero "0" is the off state. If that was intentional, you might consider that enabling or disabling meters or measures.
Rainmeter will always use some CPU processing, generally the small variance you mentioned is hardly negligible.
Please check you are using the proper modifier between '0' and '1'1. 0 being the off state for almost everything in rainmeter, 1 is on.
CodeCode wrote: ↑September 12th, 2021, 7:05 pm
DynamicVariables= needs to be set as 1, not zero "0" is the off state. If that was intentional, you might consider that enabling or disabling meters or measures.
Rainmeter will always use some CPU processing, generally the small variance you mentioned is hardly negligible.
Please check you are using the proper modifier between '0' and '1'1. 0 being the off state for almost everything in rainmeter, 1 is on.
Yes that exactly the point, I want to disable some parts of the skin, that why dynamic variables is set to 0 in the bang.
Your measures and most meters are quite active, so CPU usage is in that case is expected behavior. If, and only if, it does not affect the functionality of your skin, you can use
David8192 wrote: ↑September 12th, 2021, 7:53 pm
Your measures and most meters are quite active, so CPU usage is in that case is expected behavior. If, and only if, it does not affect the functionality of your skin, you can use
That's good to know, it's not what I want sadly, cheers for the help.
I've uploaded the skin. (dumb to not have notice sooner the attachements tab)
right click on it to access the config variables and switch the ToggleMeters of all to 0. (be sure to use the test.ini variant)
When all of then are off, it's "supposed" to be at "0%" CPU usage, but it's not the case.
I have this setup for all parts of my skin.
But when all of the skins parts are hidden/disable/updatedivider=-1 rainmeter is still using some of my CPU. Compare to when I unload the skin where it's at zero of CPu usage.
I'm wondering if there is something I'm messing or if it's the way of rainmeter functionning.
Still new to rainmeter, so I'm trying to optimize the skin.
You can pause a measure if you want to. No need of messing with dynamic variables or disabled. Unpause it later. If you want it's value to be 0 when not in use, just use disable measure bang.
death.crafter wrote: ↑September 13th, 2021, 10:01 am
You can pause a measure if you want to. No need of messing with dynamic variables or disabled. Unpause it later. If you want it's value to be 0 when not in use, just use disable measure bang.
See measure bangs in bangs section of docs.
Thanks you I didn't saw that earlier in the documents, that's helpful !
So now I'm using IfTrueAction=[!HideMeterGroup "Audio"][!SetOptionGroup Audio UpdateDivider "-1"][!SetOptionGroup Audio DynamicVariables "0"][!DisableMeasureGroup Audio]
The SeoptionGroup are to be sure that the meters are "disabled" and will not update.
But in the end it's still consuming some CPU even if they are not showing and updating.
Duschmoll wrote: ↑September 13th, 2021, 2:08 pm
Thanks you I didn't saw that earlier in the documents, that's helpful !
So now I'm using IfTrueAction=[!HideMeterGroup "Audio"][!SetOptionGroup Audio UpdateDivider "-1"][!SetOptionGroup Audio DynamicVariables "0"][!DisableMeasureGroup Audio]
The SeoptionGroup are to be sure that the meters are "disabled" and will not update.
But in the end it's still consuming some CPU even if they are not showing and updating.
Is there anything else I can do ?
Thanks again for all the help !
Can you give a rough note on how much they consume and how much you expect them to consume?