i would like to solve dt and floor() gaps using built-in behaviours and plug-ins (so i could eventually still upload to the arcade).
i have been recreating the example tutorial from another program for an endless runner for construct. when i tried to make it framerate independant gaps began to appear in the object spawning so i left it out to complete the tutorial.
another problem appeared - when the run speed is not a factor of 32 (the ground size) it creates gaps in the floor because floor() is used to get rid of the remainder in the ground spawning code, so it doesn't randomly stop spawning the ground because the runspeed isn't a factor of 32.
if any one has some ideas to help fix the floor() rounding gaps i would very much appreciate it. is framerate independance important in an endless runner type game?