Difference between revisions of "F22: xGameCreate"

Revision as of 06:02, 9 December 2022

Grading Criteria

Whack-a-mole

Abtract

Whac-a-Mole is a fun arcade game in which the player hits plastic moles with a hammer as soon as it appears out of their hole, to score points. We will be recreating the same old game with some modifications. Instead of plastic moles and a hammer, we will be using a LED Matrix to display mole-like characters and touch sensors to imitate the hammer. The scoring will be based on the no of moles you hit and how accurately you hit. We will be designing three levels and after each level, the difficulty of the game will rise.

Objectives & Introduction

• The aim of the game is to hit as many moles as possible as they appear out of the holes

• There will be three lives and the speed and complexity of the game increase as the score goes up.

• If you miss a mole you lose a life

• Based on how many moles you hit your score will increase.

• The LED matrix is used to create the 12-mole-hole-like animation and the moles appear randomly in some holes.

• ITO-coated PET is used for receiving the touch input (hitting the mole).

• A speaker is used to play background music, and sound clips when you hit a mole.

Team Members & Technical Responsibilities

• Karthigai Amutha Ezhilarasu
  • Touch Sensor Driver Implementation
  • Game logic design
  • Hardware Integration

• Stephen Oneto
  • Graphics Driver Implementation
  • Game logic design
  • Enclosure design and 3D printing
  • Battery regulatory circuit design

• Yatish Koul
  • MP3 Driver Implementation
  • Integrating MP3 module with the Game
  • Game logic design

Schedule

Materials List with cost

Design & Implementation

Schematic

Hardware Design

Implementation

Capacitive touch breakout

We used a MPR121

LED Matrix

mp3 module

Hardware Interface

Touch Sensor Driver

LED matrix Driver

Audio Driver

Software Design

Game Logic

Implementation

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.

This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

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? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

<Bug/issue name>

Discuss the issue and resolution.

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?

Project Video

Upload a video of your project and post the link here.

Project Source Code

• Sourceforge Source Code Link

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix

You can list the references you used.