Log In  

EDIT: Fixed as of 0.2.0!

Original post:


Pretty sure when you originally added _update60(), you compensated for the doubled frame rate when returning time() values, but these days time() is running at double speed when you have _update60() instead of _update().

I noticed this when playing with a simple seven-segment-display demo. Here's one that uses update() and updates once per second as expected:

Cart #49956 | 2018-03-05 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

And this is the same cart, but switched to _update60() and runs twice as fast:

Cart #49957 | 2018-03-05 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

P#49958 2018-03-05 09:23 ( Edited 2020-04-19 01:37)

@zep

Just wanted to point out that this is still an issue as of the 0.1.12 web player.

P#62242 2019-02-25 16:37

[Please log in to post a comment]

Follow Lexaloffle:          
Generated 2024-04-19 12:53:41 | 0.010s | Q:17