Merge pull request #20 from AristurtleDev/18-texture-sampling

Chapter 18: Texture Sampling

Author: AristurtleDev

articles/toc.yml

@@ -146,6 +146,8 @@
           href: tutorials/building_2d_games/16_working_with_spritefonts/
         - name: "17: Scenes"
           href: tutorials/building_2d_games/17_scenes/
+        - name: "18: Texture Sampling"
+          href: tutorials/building_2d_games/18_texture_sampling/
 - name: Console Access
   href: console_access.md
 - name: Help and Support

articles/tutorials/building_2d_games/04_creating_a_class_library/index.md

@@ -177,7 +177,7 @@ Running the game now will show the same window as before, only now it is at a 12
 > [!IMPORTANT]
 > If you receive an error stating that the following:
 >
-> *The type or namespace name 'FramesPerSecondCounter' could not be found (are you missing a using directive or an assembly reference?)*
+> *The type or namespace name 'Core' could not be found (are you missing a using directive or an assembly reference?)*
 >
 > This means either you forgot to add the `using MonoGameLibrary;` using directive to the top of the *Game1.cs* class file, or you did not add the project reference correctly.  Ensure that the project reference was added correctly by revisiting the [Add a Reference to the Class Library](#adding-a-reference-to-the-class-library) section above and that you added the using directive.
 

articles/tutorials/building_2d_games/05_content_pipeline/index.md

@@ -183,7 +183,7 @@ The [**ContentManager**](xref:Microsoft.Xna.Framework.Content.ContentManager) of
 > When an asset is loaded for the first time, the [**ContentManager**](xref:Microsoft.Xna.Framework.Content.ContentManager) will internally cache the loaded asset.  Loading that same asset later will return the cached asset instead of having to perform another disk read to load the asset again.
 
 > [!TIP]
-> When an asset is unloaded, if the asset type implements the `IDisposable` interface, the `Dispose` method will automatically be called on the asset during hte unload process.
+> When an asset is unloaded, if the asset type implements the `IDisposable` interface, the `Dispose` method will automatically be called on the asset during the unload process.
 
 When loading an asset, the load methods require two parts:
 
@@ -223,17 +223,17 @@ Now that we have an image file to add, perform the following:
 
 1. Open the content project in the MGCB Editor.
 2. Select the *Content* node in the Project Panel.
-3. Right-click on the selected *Content* node and choose *Add > New Folder...* from teh context menu.
+3. Right-click on the selected *Content* node and choose *Add > New Folder...* from the context menu.
 4. Name the folder *images* and click the *Ok* button.
 5. Select the new *images* node in the Project Panel.
-6. Right-click on the selected *images* node and choose *Add > Existing Item..* from teh context menu.
+6. Right-click on the selected *images* node and choose *Add > Existing Item..* from the context menu.
 7. In the file browser that appears, navigate to the location of the *logo.png* file you just downloaded.
 8. Select the *logo.png*  file click *Open*.
 9. When prompted choose the *Copy the file to the directory* option from the add exiting file pop-up.
 10. Save the changes made to the content project by selecting *File > Save* from the top menu.
 
 > [!IMPORTANT]
-> After changes have been made in the MGBC Editor, ensure that you save the changes.  They are not automatically saved, though you will be warned if you close the editor and haven't saved changes. You can tell that changes have not been saved by looking at the title bar of the MGCB editor window.  If it has an '*' at the end of the window title, this means changes have not been saved
+> After changes have been made in the MGCB Editor, ensure that you save the changes.  They are not automatically saved, though you will be warned if you close the editor and haven't saved changes. You can tell that changes have not been saved by looking at the title bar of the MGCB editor window.  If it has an '*' at the end of the window title, this means changes have not been saved
 
 | ![Figure 5-8: The logo image added to the content project in the MGCB Editor](./images/mgcb-logo-added.png) |
 |:-----------------------------------------------------------------------------------------------------------:|

articles/tutorials/building_2d_games/07_optimizing_texture_rendering/index.md

@@ -177,14 +177,13 @@ First, we'll explore creating the texture atlas and defining the texture regions
 The key changes in this implementation are:
 
 1. The `_logo` field was removed.
-2. The `FramesPerSecondCounter` component that was added in the constructor was removed.
-3. Added  `TextureRegion` members for the slime and bat sprites.
-4. In [**LoadContent**](xref:Microsoft.Xna.Framework.Game.LoadContent):
+2. Added  `TextureRegion` members for the slime and bat sprites.
+3. In [**LoadContent**](xref:Microsoft.Xna.Framework.Game.LoadContent):
     - Removed loading the logo texture.
     - Created a `TextureAtlas` with the atlas texture.
     - Added regions for both the slime and the bat.
     - Retrieved the regions using their names.
-5. Updated [**Draw**](xref:Microsoft.Xna.Framework.Game.Draw(Microsoft.Xna.Framework.GameTime)) to render both sprites, using the slime's `Width` property to position the bat.
+4. Updated [**Draw**](xref:Microsoft.Xna.Framework.Game.Draw(Microsoft.Xna.Framework.GameTime)) to render both sprites, using the slime's `Width` property to position the bat.
 
 Running the game now shows both sprites in the upper-left corner:
 

articles/tutorials/building_2d_games/11_input_management/index.md

@@ -93,13 +93,13 @@ Next, we'll add methods to check various key states:
 
 These methods serve two distinct purposes.  For checking continuous states:
 
-- `IsKeyDown`: Returns true as long as a key is being held down.
-- `IsKeyUp`: Returns true as long as a key is not being pressed.
+- `IsKeyDown`: Returns true as long as the specified key is being held down.
+- `IsKeyUp`: Returns true as long as the specified key is not being pressed.
 
 And for detecting state changes:
 
-- `WasKeyJustPressed`: Returns true only on the frame when a key changes from up-to-down.
-- `WasKeyJustReleased`: Returns true only on the frame when a key changes from down-to-up.
+- `WasKeyJustPressed`: Returns true only on the frame when the specified key changes from up-to-down.
+- `WasKeyJustReleased`: Returns true only on the frame when the specified key changes from down-to-up.
 
 > [!TIP]
 > Use continuous state checks (`IsKeyDown`/`IsKeyUp`) for actions that should repeat while a key is held, like movement. Use single-frame checks (`WasKeyJustPressed`/`WasKeyJustReleased`) for actions that should happen once per key press, like jumping or shooting.
@@ -207,13 +207,13 @@ Next, we'll add methods to check various button states:
 
 These methods serve two distinct purposes. For checking continuous states:
 
-- `IsKeyDown`: Returns true as long as a key is being held down.
-- `IsKeyUp`: Returns true as long as a key is not being pressed.
+- `IsButtonDown`: Returns true as long as the specified button is being held down.
+- `IsButtonUp`: Returns true as long as the specified button is not being pressed.
 
 And for detecting state changes:
 
-- `WasKeyJustPressed`: Returns true only on the frame when a key changes from up-to-down.
-- `WasKeyJustReleased`: Returns true only on the frame when a key changes from down-to-up.
+- `WasButtonJustPressed`: Returns true only on the frame when the specified button changes from up-to-down.
+- `WasButtonJustReleased`: Returns true only on the frame when the specified button changes from down-to-up.
 
 > [!NOTE]
 > Each method uses a switch statement to check the appropriate button property from the [**MouseState**](xref:Microsoft.Xna.Framework.Input.MouseState) based on which `MouseButton` enum value is provided. This provides a consistent API while handling the different button properties internally.
@@ -372,7 +372,7 @@ The key changes to the `Core` class are:
 
 Now let's update our `Game1` class to use the new input management system through the `Core` class.  Open *Game1.cs* in the game project and update it to the following:
 
-[!code-csharp[](./snippets/game1.cs?highlight=74,80,86,92,98,106,111,114,118,124,126-127,132,138,144,150)]
+[!code-csharp[](./snippets/game1.cs?highlight=71,77,83,89,95,103,108,111,115,121,123-124,129,135,141,147)]
 
 The key changes to the `Game1` class are:
 

articles/tutorials/building_2d_games/11_input_management/snippets/game1.cs

@@ -49,9 +49,6 @@ protected override void LoadContent()
 
     protected override void Update(GameTime gameTime)
     {
-        if (GamePad.GetState(PlayerIndex.One).Buttons.Back == ButtonState.Pressed || Keyboard.GetState().IsKeyDown(Keys.Escape))
-            Exit();
-
         // Update the slime animated sprite.
         _slime.Update(gameTime);
 

articles/tutorials/building_2d_games/11_input_management/snippets/keyboardinfo.cs

@@ -12,16 +12,6 @@ public class KeyboardInfo { }
     /// </summary>
     public KeyboardState PreviousState { get; private set; }
 
-    /// <summary>
-    /// Gets the state of keyboard input during the current input cycle.
-    /// </summary>
-    public KeyboardState CurrentState { get; private set; }
-
-    /// <summary>
-    /// Gets the state of keyboard input during the previous update cycle.
-    /// </summary>
-    public KeyboardState PreviousState { get; private set; }
-
     /// <summary>
     /// Gets the state of keyboard input during the current input cycle.
     /// </summary>

articles/tutorials/building_2d_games/12_collision_detection/index.md

@@ -348,7 +348,7 @@ Let's review what you accomplished in this chapter:
   - Implemented bouncing behavior for the bat.
   - Created a trigger response when the slime "eats" the bat.
 
-In the next chapter, we'll start exploring audio to add sound effects when a collision occurs and background music to our game.
+In the next chapter, we'll explore using tilesets and tilemaps to create tile based environments for our game.
 
 ## Test Your Knowledge
 

articles/tutorials/building_2d_games/17_scenes/index.md

@@ -215,9 +215,12 @@ Add the following fields to the `GameScene` class:
 - The `_slimePosition` and `_batPosition` fields track the current position of the slime and bat.
 - The `MOVEMENT_SPEED` constant defines the base movement speed for both the slime and bat.
 - The `_batVelocity` field tracks the current velocity of the bat as it moves around the screen.
+- The `_tilemap` field stores the tilemap that we'll load and draw for the level background environment.
+- The `_roomBounds` field defines a rectangular boundary that represents the boundary of the room that the slime and bat stays within.
 - The `_bounceSoundEffect` and `_collectSoundEffect` fields store the sound effects to play when the bat bounces off a screen edge or is eaten by the slime.
 - The `_font` field stores the font used to display the player's score.
 - The `_score` field tracks the player's current score, which increases when the slime eats a bat.
+- The `_scoreTextPosition` and `_scoreTextOrigin` defines the position and origin to use when drawing the score text.
 
 #### Game Scene Methods
 
@@ -230,8 +233,10 @@ Add the following override for the `Initialize` method to the `GameScene` class:
 [!code-csharp[](./snippets/gamescene.cs#initialize)]
 
 - We set `Core.ExitOnEscape` to false because in the gameplay scene, we want to handle the escape key differently; instead of exiting the game, it will return to the title screen.
-- The height of the font is measured to calculate proper vertical positioning for the game elements.
-- The initial positions of the slime and bat are set, placing the slime below where the score will be displayed and the bat a small distance to the right of the slime.
+- The room bounds is calculated using the bounds of the screen and adjusting that so that it shrinks by one tile width and height on each edge, which will match with the tilemap wall boundary.
+- The slime's initial position is set to be the center tile by calculating the center row and column.
+- The bat's initial position is placed at the top left of the room bounds.
+- The position and origin of the score text is precalculated.  The height of the text is measured to properly calculate the center origin for vertical positioning.
 - The `AssignRandomBatVelocity` method is called to give the bat its initial velocity.
 
 ##### Game Scene LoadContent
@@ -240,9 +245,9 @@ Add the following override for the `LoadContent` method to the `GameScene` class
 
 [!code-csharp[](./snippets/gamescene.cs#loadcontent)]
 
-- Similar to the title scene, we capture a reference to the global content manager from the `Core` class.
 - The texture atlas is loaded using the global content manager, and the slime and bat animated sprites are created from it.
-- The sound effects are loaded using the scene's content manager since they're specific to the gameplay scene.
+- The tilemap is loaded using the scene's content manager since they are specific to the gameplay scene.
+- The sound effects are loaded using the scene's content manager since they are specific to the gameplay scene.
 - The font is loaded using the global content manager since it is used in multiple scenes.
 
 > [!TIP]
@@ -257,10 +262,10 @@ Add the following override for the `Update` method to the `GameScene` class:
 - The animated sprites for the slime and bat are updated.
 - Input from keyboard and gamepad is checked with dedicated methods `CheckKeyboardInput` and `CheckGamePadInput`.
 - Collision detection is performed to:
-  - Keep the slime within the screen bounds.
-  - Make the bat bounce off screen edges.
+  - Keep the slime within the room bounds.
+  - Make the bat bounce off edges of the room bounds.
   - Detect when the slime eats the bat.
-- When the slime eats the bat, the bat respawns in a random location, given a new velocity, the collect sound is played, and the score is increased.
+- When the slime eats the bat, the bat respawns in a random location within the room bounds, given a new velocity, the collect sound is played, and the score is increased.
 
 ##### Game Scene Helper Methods
 
@@ -278,10 +283,10 @@ Add the following override for the `Draw` method to the `GameScene` class:
 
 [!code-csharp[](./snippets/gamescene.cs#draw)]
 
-- A reference to the graphics device from the `Core` instance is captured so we don't have to type `Core.Instance.GraphicsDevice` each time to use it.
 - The back buffer is cleared.
-- The slime and bat animated sprites are drawn at the current position.
-- The player's score is drawn in the top-left corner of the screen.
+- The tilemap is drawn.
+- The slime and bat animated sprites are drawn at their current positions.
+- The player's score is drawn at using its precalculated position and origin so that it is in the top left of the room bounds centered on the wall sprite.
 
 ### Updating the Game1 Class