User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
labs:pong_part_2 [2019/12/03 15:53] jgoeders [Exercise #1 - Drawing the objects] |
labs:pong_part_2 [2019/12/03 16:26] (current) jgoeders [Exercise #1 - Drawing the objects] |
||
|---|---|---|---|
| Line 197: | Line 197: | ||
| 6. Implement the other components as follows: | 6. Implement the other components as follows: | ||
| - | * **Ball Location:** You should create a new ''always_ff'' block to manage the ball location. Create two registers, ''BallX'' and ''BallY'' that are reset to the center of the screen when ''initGame'' is true. This is sufficient for this exercise. | + | * **Ball Location:** You should create a new ''always_ff'' block to manage the ball location. Create two registers, ''ballX'' and ''ballY'' that are reset to the center of the screen when ''initGame'' is true. This is sufficient for this exercise. |
| * **Paddle Locations:** You should create a new ''always_ff'' block to manage the paddle locations. Create two registers, ''LPaddleY'' and ''RPaddleY'' that position the paddles halfway down the screen when ''initGame'' is true. This is sufficient for this exercise. | * **Paddle Locations:** You should create a new ''always_ff'' block to manage the paddle locations. Create two registers, ''LPaddleY'' and ''RPaddleY'' that position the paddles halfway down the screen when ''initGame'' is true. This is sufficient for this exercise. | ||
| * **Player Scores:** You should create a new ''always_ff'' block to manage the player scores. For this exercise, just assign the ''P1score'' and ''P2score'' registers to 0 when ''initGame'' is true. | * **Player Scores:** You should create a new ''always_ff'' block to manage the player scores. For this exercise, just assign the ''P1score'' and ''P2score'' registers to 0 when ''initGame'' is true. | ||
| Line 231: | Line 231: | ||
| * **Ball Location:** Add more logic to your ball location component. When in the move state (''moveAndScore'' is high), update the ball location according to its direction. Consider the values of ''ballMovingRight'' and ''ballMovingDown'' and either add 1 or subtract 1 from ''ballX'' and ''ballY'' accordingly. | * **Ball Location:** Add more logic to your ball location component. When in the move state (''moveAndScore'' is high), update the ball location according to its direction. Consider the values of ''ballMovingRight'' and ''ballMovingDown'' and either add 1 or subtract 1 from ''ballX'' and ''ballY'' accordingly. | ||
| * **Ball Direction: ** You should create a new ''always_ff'' block to manage the ball directions (''ballMovingRight'' and ''ballMovingDown'' registers). On ''initGame'', you should reset these registers to values of your choice. When the ball hits a wall (check the ball location), you should update these registers appropriately. | * **Ball Direction: ** You should create a new ''always_ff'' block to manage the ball directions (''ballMovingRight'' and ''ballMovingDown'' registers). On ''initGame'', you should reset these registers to values of your choice. When the ball hits a wall (check the ball location), you should update these registers appropriately. | ||
| - | * **Erase Switch:** Create a flip-flop, ''erasing'' that is reset to 0 on ''initGame'' and flips its value if ''switchErase'' is high. | + | * **Erase Switch:** Create a flip-flop, ''erasing'' that is reset to 0 on ''initGame'' and flips its value if ''invertErase'' is high. |
