ok, got it now. well, time() is (was?) a built-in function, maybe it should not be 'just' (number of frames/30)?
anyway it's deprecated and a non-blocking issue as there are other options, so let's forget about it.
on topic it seems that simply designing the game at 60fps is ok in most cases since _update60 would be called twice on 30fps hardware (so you'd just lose a draw frame).
From the manual:
If _update60() is defined instead of _update(), PICO-8 will run in 60fps mode:
- both _update60() and _draw() are called at 60fps - half the PICO-8 CPU is available per frame before dropping down to 30fps
** please note that not all PICO-8s support 60fps. On machines that do not support it,
_update60() will instead be called twice per frame and _draw() at 30fps. You can check
the behaviour of your program running at 30fps by adding the following snippet to the
bottom of your code:
u60=_update60 _update60=nil function _update() u60() u60() end
[Please log in to post a comment]