F24: Brick Breaker - Revision history

Proj user9: /* Schedule */

2024-12-20T01:32:42Z

‎Schedule

Proj user9: /* References */

2024-12-20T01:31:04Z

‎References

Proj user9: /* Acknowledgement */

2024-12-20T01:30:42Z

‎Acknowledgement

Proj user9: /* Acknowledgement */

2024-12-20T01:30:24Z

‎Acknowledgement

Proj user9: /* Conclusion */

2024-12-20T01:29:20Z

‎Conclusion

Proj user9: /* Testing & Technical Challenges */

2024-12-20T01:26:31Z

‎Testing & Technical Challenges

Proj user9: /* Design & Implementation */

2024-12-20T01:16:31Z

‎Design & Implementation

Proj user9: /* Team Members & Responsibilities */

2024-12-20T00:47:00Z

‎Team Members & Responsibilities

Proj user9: /* Parts List & Cost */

2024-12-19T23:59:26Z

‎Parts List & Cost

Proj user9: /* Project Title */

2024-12-19T23:55:19Z

‎Project Title

@@ Line 167: / Line 167: @@
 * Update the wiki page.
+|
-* <span style="color:orange">In progress</span>
+* <span style="color:green">Completed</span>
-* <span style="color:orange">In progress</span>
+* <span style="color:green">Completed</span>
 |-
 ! scope="row"| 10
@@ Line 188: / Line 188: @@
 *Update the wiki page.
+|
-* <span style="color:red">Not started</span>
+* <span style="color:green">Completed</span>
-* <span style="color:red">Not started</span>
+* <span style="color:green">Completed</span>
-* <span style="color:red">Not started</span>
+* <span style="color:orange">In progress</span>
-* <span style="color:red">Not started</span>
+* <span style="color:orange">In progress</span>
 |-
 |}

← Older revision		Revision as of 01:31, 20 December 2024
Line 344:		Line 344:
	=== Acknowledgement ===		=== Acknowledgement ===
	We'd like to thank Preet for giving us the opportunity to develop and learn through an interactive team project. We would also like to acknowledge the TA Shailja Jain for their feedback throughout the semester.		We'd like to thank Preet for giving us the opportunity to develop and learn through an interactive team project. We would also like to acknowledge the TA Shailja Jain for their feedback throughout the semester.
−
−	~~=== References Used ===~~
−	~~List any references used in project.~~
−
−	~~=== Appendix ===~~
−	~~You can list the references you used.~~

@@ Line 343: / Line 343: @@
 == References ==
 === Acknowledgement ===
-We'd like to thank Preet for giving us the opportunity to develop and learn through an interactive team project. We would also like to acknowledge the TA Shilja Jain for their feedback throughout the semester.
+We'd like to thank Preet for giving us the opportunity to develop and learn through an interactive team project. We would also like to acknowledge the TA Shailja Jain for their feedback throughout the semester.
 === References Used ===

@@ Line 343: / Line 343: @@
 == References ==
 === Acknowledgement ===
-Any acknowledgement that you may wish to provide can be included here.
+We'd like to thank Preet for giving us the opportunity to develop and learn through an interactive team project. We would also like to acknowledge the TA Shilja Jain for their feedback throughout the semester.
 === References Used ===

@@ Line 327: / Line 327: @@
 == Conclusion ==
-Conclude your project here.  You can recap your testing and problems.  You should address the "so what" part here to indicate what you ultimately learnt from this project.  How has this project increased your knowledge?
+The Brick Breaker game project served as an excellent opportunity to apply and expand our knowledge of embedded systems, specifically in hardware-software integration and real-time application development. Throughout the project, we faced several challenges, including collision detection issues with block corners and the difficulties associated with debugging real-time game logic. By addressing these problems with a combination of structured design and innovative solutions, such as standardizing collision handling and leveraging modular code, we were able to deliver a functional and engaging game.
 === Project Video ===

@@ Line 322: / Line 322: @@
 == Testing & Technical Challenges ==
-Describe the challenges of your project.  What advise would you give yourself or someone else if your project can be started from scratch again?
+A significant technical challenge during the implementation of the Brick Breaker game was ensuring accurate collision detection, especially when the ball interacted with multiple bricks or hit a corner. The issue arose when the ball's next position overlapped with a corner shared by two or more blocks. This led to inconsistencies in how collisions were detected and resolved. For instance, if two bricks were stacked vertically or placed side by side, the ball's direction could behave unpredictably, leading to unexpected bounces. Initially, our collision logic treated corners as part of either a row or a column based on the ball's direction of travel. While this approach worked in simple cases, it failed when multiple blocks were involved.
-Include sub-sections that list out a problem and solution, such as:
+To address this, we standardized the handling of corners by treating all corners as part of a column rather than a row. This change provided a consistent logic flow for detecting and handling collisions, ensuring the ball's trajectory behaved predictably even in complex scenarios. Testing this approach revealed that treating corners as rows led to erratic bounces and breaks in the gameplay flow, while treating them as part of columns yielded a smoother and more intuitive experience. This adjustment significantly improved the game's performance and user experience, resolving an issue that had initially seemed insurmountable.
 == Conclusion ==

@@ Line 243: / Line 243: @@
 == Design & Implementation ==
-The design section can go over your hardware and software design.  Organize this section using sub-sections that go over your design and implementation.
+For the design and implementation of the Brick Breaker game, the SJ2 board serves as the central controller to interface with a 64x64 LED matrix, control buttons, and an accelerometer. Each of these components plays a crucial role in the functionality of the game, enabling dynamic gameplay and interactivity.
 === Hardware Design ===
-Discuss your hardware design here.  Show detailed schematics, and the interface here.
+In the hardware setup for this project, we outlined a few high-level connections that were necessary to implement the Brick Breaker game. These connections can be visualized in the top-level schematic shown below. The schematic was designed using draw.io.
 === Hardware Interface ===
-In this section, you can describe how your hardware communicates, such as which BUSes used.  You can discuss your driver implementation here, such that the '''Software Design''' section is isolated to talk about high level workings rather than inner working of your project.
+The 64x64 LED matrix acts as the primary display for the game, rendering all visual elements such as the paddle, ball, and bricks. The SJ2 board interfaces with the matrix using GPIO pins, which are configured to drive the rows, columns, and colors.
 === Software Design ===
-Show your software design.  For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level.  Do not show the details of the code.  For example, do not show exact code, but you may show psuedocode and fragments of code.  Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
+The Brick Breaker game was implemented using a state machine design, which allowed for modular and organized control over the game's logic. The main function driving the game, game_state_machine__run_game(), transitions through different states based on user interactions and game events. These states, such as INIT, GAME, PAUSE, and GAME_OVER, provide a clear structure to the game flow. A state machine design was chosen for its ability to simplify complex logic by dividing it into smaller, well-defined states, making the code easier to understand and maintain. Transitions between states occur based on specific triggers, such as a button press to pause the game or the ball falling out of bounds. By using a state machine, redundant operations were minimized, particularly in the GAME state, where initialization functions were executed only once during transitions to ensure optimal performance.
-=== Implementation ===
+Player input was managed through buttons and an accelerometer, providing intuitive and responsive control. The buttons allowed precise left or right movement of the paddle, while the accelerometer offered an alternative control method, enabling the paddle to move based on the tilt of the SJ2 board. This dual-input system enhanced player engagement and added variety to the gameplay experience. Additionally, dynamic game elements, such as increasing ball speed and additional levels of difficulty, kept the game challenging as players progressed. The game state transitions were smooth and well-optimized, with the state machine ensuring clear separation of responsibilities and efficient execution of tasks.
 == Testing & Technical Challenges ==

@@ Line 27: / Line 27: @@
 === Team Members & Responsibilities ===
 *  Manoj
-**
+** Game logic
 *  Kevin
-**
+** Hardware connections
 *  Harbans
-**
+** Accerometer and paddle
 == Schedule ==

@@ Line 194: / Line 194: @@
 == Parts List & Cost ==
-Give a simple list of the cost of your project broken down by components.  Do not write long stories here.
+{| class="wikitable"
 == Design & Implementation ==

@@ Line 11: / Line 11: @@
 </font>
-== Project Title ==
+== Brick Breaker ==
 == Abstract ==