I love shadertoys as a visualization, and use a random screensaver. I noticed that on my (German) time settings, the analog clock screensaver displays the time one hour early (i.e. it is 5 pm here, and the shadertoys clock shows 4 pm).
Is that a known bug? Which time is used for the visualization? OSMC itself displays the right time of course.
localtime reportes the correct time. I will take a closer look, maybe it’s just a problem drawing the clock dial correctly, but it definitely looks to me as if it wants to display an hour earlier.
Edit: I just looked at it closely, and it seems that the hour-finger only moves at full hours, which is definitely not what a “real” analog clock does. It shouldn’t be too hard to move that little finger by 30/60 = 0.5 degree per minute, is it?
I just caught this. It was 6:55pm and the clock looked like five to six.
At 7:05pm the clock looked like 7:05pm.
So I don’t think it is time zone related - just how that particular shader rounds the hours.
I seem to recall there was an option (in the code) for the second hand to be discrete or continuous.
I suspect the continuous form wouldn’t have this issue. I’ll look into it.
Edit - yes, avoiding the truncation on hours improves the behaviour.
Will push an update soon.