Correct. Window's timer resolution is 15.6ms. That is how fast Windows can deal with the message queue. So that is the logical lower limit for skin updates, although I strongly suggest you don't set any skin that is doing any significant work to anything close to that, as it can make Rainmeter, and potentially even Windows itself, have some lag or stutter. The most common symptom would be "mouse click lag".We can make Rainmeter's refresh rate at least 16 ms. So, why?
It because Windows' timer resolution is 15.6 ms or ?!?!
Just curious
I personally would never go lower than about Update=25 or so, and in any case, I would make every attempt to set UpdateDivider's on EVERYTHING, measures and meters, that didn't explicitly need the low update rate.
Statistics: Posted by jsmorley — Yesterday, 10:45 pm