What is wait # frames based on
-
Tyller_ aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa last edited by
I am having inconsistency due to unknown reasons where a device with better hardware appears to have somewhat different results than worse devices, is wait # frames just wait (#/framerate limit) seconds, actually wait until the screen has drawn # times, or wait until if there was # blocks here when it would finish, the last one is effectively just wait # ticks, I want to know due to technical issues with a project Iām having across devices relating to the wait # frames block
-
@jaysen4games-gmail
Hi, the wait block simply waits some time, and the time period can be specified by different units, where a frame is assumed to be 1/60 seconds. It does not account for the actual number of frames since it does not have that information.
If you need to run some code at fixed intervals, a better choice might be this block:
This block will try to run a new iteration by the fixed time interval, no matter how long it takes to finish each iteration.
If that does not work for your project, please share the project with us, and we can probably figure out a working solution for you.
CreatiCode Support