Reply to thread

Message: [QUOTE="ciro64, post: 197282, member: 61046"] Thank you for looking at the tutorial! I decided to use setInterval for the sake of simplicity. If I used requestAnimationFrame instead, I'd either have to: [LIST=1] [*]Multiply the movement with delta time. While it would have been fine for this game, I plan to make tutorials that build on top of this one, introducing concepts of acceleration, gravity and platforming. In those more complex cases, it's a bad idea to use delta time in the logic loop because it introduces instabilities in the game physics, which can affect the gameplay quite a lot. I don't think delta time is a bad thing on its own, but I've seen tutorials and even game engines in the past create a bad habit in developers by encouraging them to use it everywhere. . [*]Handle the drawing at every requestAnimationFrame call and the game loop in some other way. A good way I found to do this is to calculate how much time has passed from the last animation frame and advance logic frames accordingly. This method also compensate for stutters unlike setInterval. But like [USER=1380]@JustLooking123[/USER] said, I want to keep things simple by introducing them one by one. But in a future tutorial, I might introduce complex loop handling. [/LIST] [/QUOTE]

Totals may include hidden visitors.