Skip to content

Commit ecfc2c5

Browse files
Fix formatting of Tip Admonition (MonoGame#159)
1 parent 03cfb26 commit ecfc2c5

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

  • articles/tutorials/building_2d_games/12_collision_detection

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -192,7 +192,8 @@ For example, if we had a ball moving around the screen and wanted it to bounce o
192192

193193
[!code-csharp[](./snippets/bounce_example.cs)]
194194

195-
> [!TIP] > [**Vector2.UnitX**](xref:Microsoft.Xna.Framework.Vector2.UnitX) is $(1, 0)$ and [**Vector2.UnitY**](xref:Microsoft.Xna.Framework.Vector2.UnitY) is $(0, 1)$. We use these to get the screen edge normal since the edges of the screen are not at an angle. For more complex surfaces, you would need to calculate the appropriate normal vector based on the surface angle.
195+
> [!TIP]
196+
> [**Vector2.UnitX**](xref:Microsoft.Xna.Framework.Vector2.UnitX) is $(1, 0)$ and [**Vector2.UnitY**](xref:Microsoft.Xna.Framework.Vector2.UnitY) is $(0, 1)$. We use these to get the screen edge normal since the edges of the screen are not at an angle. For more complex surfaces, you would need to calculate the appropriate normal vector based on the surface angle.
196197
197198
### Optimizing Collision Performance
198199

0 commit comments

Comments
 (0)