Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 5_adding_basic_code.md #64

Merged
merged 2 commits into from
Sep 26, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/getting_started/5_adding_basic_code.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ The following is a line-by-line analysis of the above code.
float updatedBallSpeed = ballSpeed * (float)gameTime.ElapsedGameTime.TotalSeconds;
```

This code caches how much time, in seconds, since the last `Update` call was run, which gives us the duration of a single frame drawn to the screen. This is then multiplied by the `ballSPeed` value to allow us to control just how fast the ball moves each frame.
This code caches how much time, in seconds, since the last `Update` call was run, which gives us the duration of a single frame drawn to the screen. This is then multiplied by the `ballSpeed` value to allow us to control just how fast the ball moves each frame.

The reason why `ballSpeed` is multiplied by `gameTime.ElapsedGameTime.TotalSeconds` is because, when not using fixed time step, the time between Update calls varies. To account for this, the ballSpeed is multiplied by the amount of time that has passed since the last Update call. The result is that the ball appears to move at the same speed regardless of what framerate the game happens to be running at.

Expand Down