SDL Timers vs Frame Counting

SDL timers offer several important advantages over frame counting for game events. Let's explore why you might choose one over the other.

Frame-based timing can be problematic because frame rates often fluctuate. Consider this frame-counting approach:

1#include <SDL.h>
2#include <iostream>
3
4int main(int argc, char** argv) {
5  SDL_Init(SDL_INIT_VIDEO);
6  SDL_Window* Window = SDL_CreateWindow(
7    "Frame Timer", 100, 100, 800, 600, 0);
8
9  int FrameCount{0};
10
11  // Spawn every 60 frames 
12  const int SpawnInterval{60}; 
13
14  while (true) {
15    // Process events...
16    SDL_PumpEvents();
17
18    FrameCount++;
19    if (FrameCount % SpawnInterval == 0) {
20      std::cout << "Spawning enemy at frame "
21        << FrameCount << '\n';
22    }
23
24    // Render scene...
25
26    // Simulate varying frame times
27    SDL_Delay(16);  
28  }
29
30  SDL_DestroyWindow(Window);
31  SDL_Quit();
32  return 0;
33}

1Spawning enemy at frame 60
2Spawning enemy at frame 120
3Spawning enemy at frame 180
4Spawning enemy at frame 240

If your game runs at 60 FPS, enemies spawn every second. But if it drops to 30 FPS, enemies spawn every 2 seconds! With SDL timers, spawning remains consistent regardless of frame rate:

1#include <SDL.h>
2#include <iostream>
3
4Uint32 SpawnEnemy(Uint32 Interval, void*) {
5  std::cout << "Spawning enemy at time "
6    << SDL_GetTicks() << "ms\n";
7  return Interval;
8}
9
10int main(int argc, char** argv) {
11  SDL_Init(SDL_INIT_TIMER | SDL_INIT_VIDEO);
12  SDL_Window* Window = SDL_CreateWindow(
13    "SDL Timer", 100, 100, 800, 600, 0);
14
15  SDL_AddTimer(1000, SpawnEnemy, nullptr);
16
17  while (true) {
18    // Process events...
19    SDL_PumpEvents();
20
21    // Render scene...
22
23    // Varying frame times don't affect spawn rate
24    SDL_Delay(16);
25  }
26
27  SDL_DestroyWindow(Window);
28  SDL_Quit();
29  return 0;
30}

1Spawning enemy at time 1090ms
2Spawning enemy at time 2090ms
3Spawning enemy at time 3090ms
4Spawning enemy at time 4090ms

Frame counting requires checking conditions every frame, even for events that happen rarely. SDL timers only consume resources when they actually trigger, making them more efficient for:

• Long intervals (like buff duration timers)
• Multiple concurrent timers with different intervals
• Events that need precise timing

SDL timers run on a separate thread, meaning they:

• Won't be delayed by heavy processing in your game loop
• Can trigger during loading screens or other blocking operations
• Can handle system events even when your main thread is busy

The downside is you need to be careful about thread safety when modifying shared data in callbacks.

Use SDL timers for:

• Events that need precise timing (combos, buff durations)
• Background tasks (autosave, network polling)
• Events that should continue during pauses/loading

Use frame counting for:

• Visual effects tied to animation frames
• Game mechanics that should intentionally slow down with frame rate
• Simple cooldowns that don't need precise timing

Remember, you can also combine both approaches where appropriate!