Just to clarify: the skin itself will in this case update and redraw every 25 ms, it's only the measures and meters on which DefaultUpdateDivider=40 acts on that will be updated every 1000 ms. So, when the animation happens, the skin redraw will more or less coincide with the redraw of the animation at every 25 ms (depending on whether you let the animation use the regular skin update for the animation, or you perform the animation redraw manually), and when the animation is stopped, the skin will as well redraw every 25 ms except that since there's no visual change in the skin then, no significant resource consumption will occur.Interesting, so I set Update=25 and DefaultUpdateDivider=40, this keeps the skin updating at 1000ms and only those meters and the script measure (which would have UpdateDivider=1) for the snow updating at 25ms. This could work better than the action timer, I'll test it. Thanks![:thumbup:]( "Thumbs Up")
Basically, Update=25 and DefaultUpdateDivider=40 is not the same as Update=1000 in terms of regular skin redraws, albeit the practical effect will be close to being similar when no animation occurs. In terms of measure and meter updates however, Update=25 and DefaultUpdateDivider=40 will be exactly as having Update=1000.
Bottom line, a larger Update is indeed the least expensive choice in terms of skin redraws, but an equivalent small Update coupled with a DefaultUpdateDivider is the closest less expensive choice in that regard. Their precise similarity is only true in terms of measure / meter updates, not in terms of skin redraws. At least based on what the manual says about the Update option (which always involves redrawing the skin).
Statistics: Posted by Yincognito — 32 minutes ago — Replies 7 — Views 105