Don't worry, it happens to anyone.
Now I see. I missed that post, this is why didn't make the connection.
What does this mean? What time mismatch do you have?
Don't worry, it happens to anyone.
Now I see. I missed that post, this is why didn't make the connection.
What does this mean? What time mismatch do you have?
Several seconds late if I don't use HA and several seconds ahead if I use HA, per minute.What does this mean? What time mismatch do you have?
Code: Select all
[TimeMeterBase]
Meter=Shape
Shape=Ellipse 0,0,56,56 | Fill Color 00000000 | StrokeWidth 4 | Stroke Color 2C2C2C
X=70
Y=70
[MeasureBar]
Measure=Calc
Formula=(TimeLeft % 59) / 60
Disabled=1
[MeterSeconds]
Group=Meters
Meter=Roundline
MeasureName=MeasureBar
X=r
Y=r
StartAngle=(-PI/2)
RotationAngle=(2*PI)
LineStart=54
LineLength=58
LineColor=f9932e
Solid=1
AntiAlias=1
UpdateDivider=1
I'm sorry, but I can't replicate the issue, so it's hard to say something meaningful. As said, I still believe the HA related issues are hard to be fixed. Maybe someone else has a better idea?CarlotaN wrote: ↑February 25th, 2024, 7:16 pm Several seconds late if I don't use HA and several seconds ahead if I use HA, per minute.
If it were possible for this effect to start at 0, I imagine that the decompensation of the seconds would not be noticeable after the minutes, since the circle would not be continuous
Well, it doesn't matter... Don't worry, it works pretty well as it is now. With this is enough.I'm sorry, but I can't replicate the issue, so it's hard to say something meaningful. As said, I still believe the HA related issues are hard to be fixed. Maybe someone else has a better idea?
You're welcome. Glad to help.
I think the main problem here is the awful translation from Spanish that Google produces, so let's clarify something. Is the code supposed to reach one full rotation of the roundline in less than 1 minute, or is this the "time mismatch" you were talking about? For me, while using the code posted by balala here, the roundline completes a full circle in about 37 seconds instead of the more natural 1 minute, with or without HA (for reference, my skin displaying regular time in the upper part of the screenshot - I clicked to start the timer in your skin at 00:42:00 regular time, so that the seconds would be in sync between skins, by the way).
Yup, I'm pretty sure the problem is the Update=60. Although I think the best approach would be to change it to 1000ms and re-adjust all formulas from there. Having it at 60 is only a waste of resources since the skin doesn't need to update every 60ms at all.Yincognito wrote: ↑February 25th, 2024, 11:56 pm Along the lines of what RicardoTM mentioned, if the answer to the question I asked in my previous reply is yes, since the value of Update in the aforementioned code is 60 milliseconds, and MeasureBar goes from around 600 to 0, the total approximate (see below why) time taken by the roundline to complete a full circle is around 36000 milliseconds, aka 36 seconds, which explains the issue and the fact that I got a full roundline circle in roughly the same amount of time.
A quick fix would be to change 599 to something like 959 and 600 to something like 960 in MeasureBar from that code, so that the values are closer to the exact 1000 skin updates required to reach 1 full minute (1 minute = 60 seconds * 1000 milliseconds = 60000 milliseconds, and since the skin Update is 60 milliseconds, it would take around 1000 skin updates to reach 1 minute).
Again, take into account that for measures that are not Time measures and that have an update frequency of less than 1 second, measuring time will NOT be precise - that is why you'd use an approximation of 1000 above, and why I recommended to do precision time measurements from the Lua script, using a function like os.clock(). Either that, or, alternatively, use a typical skin Update of 1000 and Time measures instead of Calc ones for measuring time (further computations can be done in Calc measures, of course).
YES!!!I think the main problem here is the awful translation from Spanish that Google produces, so let's clarify something. Is the code supposed to reach one full rotation of the roundline in less than 1 minute, or is this the "time mismatch" you were talking about?
For me they are 1 or 2 seconds ahead and 3 or 4 seconds behind.For me, while using the code posted by balala here, the roundline completes a full circle in about 37 seconds instead of the more natural 1 minute, with or without HA (for reference, my skin displaying regular time in the upper part of the screenshot - I clicked to start the timer in your skin at 00:42:00 regular time, so that the seconds would be in sync between skins, by the way).
Adjunto el skin completo, uno que es el que Balala ha publicado, y el otro el que contiene el efecto que (de hecho es un reloj) ese no falla, yo pensaba que al reiniciar cada minuto, el fallo no se notaría al no ser una línea continua. Adjunto los 2 archivos, para que podáis probar.Hola Carlota, al parecer los amigos aquí tienen problemas entendiendo la traducción de google, yo hablo español, si quieres puedes explicarme el problema en Español y yo trato de traducirlo, o si puedo, ayudarte. A mi parecer lo que te está sucediendo es que el cronómetro se está adelantando o atrasando, verdad? O sea que no cuenta el tiempo exacto que debería de contar.
Te agradecería si pudieras publicar el skin así como lo tienes ahorita, para poder probarlo. Tienes que subirlo en formato .rmsk (usando el exportador de Rainmeter como hiciste unos posts atrás).
Puede que el problema esté relacionado con el Update que estás utilizando, al final de cuentas los measures se actualizan a la velocidad del update, así que si el update es mayor a 1 segundo (1000ms), el cronómetro estaría desincronizado.