Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 97f1329

Browse files
authoredSep 26, 2024
Update 5_adding_basic_code.md (#64)
Small typo
1 parent ef84c4c commit 97f1329

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎articles/getting_started/5_adding_basic_code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ The following is a line-by-line analysis of the above code.
120120
float updatedBallSpeed = ballSpeed * (float)gameTime.ElapsedGameTime.TotalSeconds;
121121
```
122122

123-
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.
123+
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.
124124

125125
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.
126126

0 commit comments

Comments
 (0)
Please sign in to comment.