Timers don't work at fractions of a second

Sean shared this bug 5 years ago
Reported

While it's possible to SET timers to have times of 1.2s, 1.4s, etc (via Ctrl+Click on the timer slider). Timers don't actually trigger these times properly, it seems to round down back to the previous whole number (i.e. 1.999s triggers at the same time or extremely close to a 1s timer).

To reproduce:

Start a new, empty world (non-experimental/safe mode optional)


Build a large grid platform (powered) to which you shall place:

3 Timers, side by side in a row


1 Button Panel a small distance away such that you can see all 3 Timers at once


Optional:

3 Rocket Launchers/Pistons/Airtight Hangar Doors (Something that can perform an action when linked to a timer)

Then:

Set the leftmost timer to have a delay of 1s, the middle one to 1.999s, and the rightmost one to 2s. This would also be the time to link one optional block per timer.


Group the 3 timers together, and have the button panel set up to "Start" (NOT "Trigger Now"!) the timer group at the press of a button.


If done correctly, the timer that has been set to 1.999s will finish its countdown (and perform an action) at nearly the same time (or even sooner than!) the timer set to 1s, and after a small but perceivable delay, the 2s timer will complete its countdown.


Whereas what should have happened is the 1.999s timer should've completed its countdown at nearly the same time as the 2s timer.

While this is the most extreme example I can reproduce with reliability, I have another example (which caused me to notice this issue) where I have 6 timers with delays of 1s, 1.2s, 1.4s, 1.6s, 1.8s, and 2s, placed in a row, from shortest time to longest time, with the shortest on the left, and longest on the right. After starting all 6 timers at once, the timers with less than 2s all completed their countdown and activated out of order, seemingly at random, but the same out of order order every time, then did the 2s timer activate.

Replies (4)

photo
2

Hello, Engineer!


Thank you for your feedback! Your topic has been added between considered issues.


Please keep voting for the issue as it will help us to identify the most serious bugs.


We really appreciate your patience.


Kind Regards


Keen Software House: QA Department

photo
1

Any news on this?

It's been 4 years and it's making some builds impossible to make...

photo
photo
2

This is still a thing. Some numbers don't work at all. For example, setting to 8 causes it to go off at 7, but setting 8.5 will make it go off at 8. There's actually more to this. You can set the delay in the block to the nearest 0.1 seconds (or so it tells you), but when you copy and paste it it changes to the nearest second.

photo
1

Still still a thing.

photo
2

Hello!


Thank you for letting us know, I'm moving this ticket to Submitted. We will investigate it.


Kind Regards

Keen Software House: QA Department

photo
photo
2

Hello, Engineers!

Thanks for keeping this issue alive and updating it. It was indeed successfully reproduced and therefore put into our internal system.

Kind Regards

Keen Software House: QA Department

photo
1

Good to see someone still cares. Thank you. :)

photo
photo
1

Still a thing... YEARS later

Leave a Comment
 
Attach a file