[Help] Reducing lag in skins with lots of meters
Posted: February 22nd, 2020, 6:42 am
Hey Rainmeter community,
I'd like to get into animating my skins with the ActionTimer plugin, but I've been coming across a lag problem. It appears that, once I have around 20 meters rendered at a time (a small amount for all of the skins that I'm making), Rainmeter caps the skin's framerate at around 10 FPS. At this point, even hover actions have a noticable delay. This effect isn't gradual either. In my latest test, with 20 meters loaded, everything ran nice and smooth, but introducing a 21st meter, even if it was just a string, killed the skin's preformance.
Is there something that I can do to optimize the way I'm updating/redrawing my skins? As of now, I've been using [!UpdateMeter *][!Redraw], which is what's shown in the docs, but it doesn't seem to be any more efficient than just using [!Update].
My CPU is an Intel Core i7 6700K and my GPU is an Nvidia GeForce GTX 1080, so I doubt my system specs are bottlenecking anything. Is this just a limitation of Rainmeter, or am I missing something?
(I'm running the latest version of Rainmeter)
I'd like to get into animating my skins with the ActionTimer plugin, but I've been coming across a lag problem. It appears that, once I have around 20 meters rendered at a time (a small amount for all of the skins that I'm making), Rainmeter caps the skin's framerate at around 10 FPS. At this point, even hover actions have a noticable delay. This effect isn't gradual either. In my latest test, with 20 meters loaded, everything ran nice and smooth, but introducing a 21st meter, even if it was just a string, killed the skin's preformance.
Is there something that I can do to optimize the way I'm updating/redrawing my skins? As of now, I've been using [!UpdateMeter *][!Redraw], which is what's shown in the docs, but it doesn't seem to be any more efficient than just using [!Update].
My CPU is an Intel Core i7 6700K and my GPU is an Nvidia GeForce GTX 1080, so I doubt my system specs are bottlenecking anything. Is this just a limitation of Rainmeter, or am I missing something?
(I'm running the latest version of Rainmeter)