Interactive Real Time Mixed Reality Application for HoloLens 2
| Name | Year | Course | GitHub username | Student number |
|---|---|---|---|---|
| Cian Moriarty | 2nd | ICS | moriarci | 21367392 |
| Dan Preda | 2nd | ICS | DanPreda90 | 21363698 |
| Darius Pop | 2nd | ICS | Dezu17 | 21367524 |
| Hannah Foley | 3rd | CSB | hannahfoley-1 | 20332137 |
| Ivan Puig | 2nd | ICS | ipuig | 22329949 |
| Peter Rolfe | 2nd | ICS | pjhrolfe | 21368433 |
| Steven Bondaruk | 3rd | ICS | bondarus | 20333385 |
| Steve Thomas | 2nd | CSB | stevethomas13 | 21346990 |
| Zehao Yu | 3rd | ICS | Zehao00 | 19336864 |
Our application is an interactive real-time game utilising augmented reality technology. When the game starts, moving targets are constantly generated in front of the player. Players can fire projectiles to hit targets to earn points. The player can fire three types of projectiles: earth projectiles, fire projectiles and water projectiles. Different projectiles have different physical properties and launching conditions. When the countdown of the game reaches 0, the game ends and the player's stats are displayed on the finish screen.
There are three type of projectile : earth projectile, fire projectile and water projectile. All three types of projectiles are made with shaders and they have different physics properties. Different projectiles have different launching conditions:
- earth projectile --> 'press the right mouse button' or 'grip right hand'
- fire projectile --> 'press the "F" key on the keyboard' or 'the speed of movement reaches a certain threshold when the hand is not clenched'
- water projectile --> 'press the "F" key on the keyboard' or 'the speed of movement reaches a certain threshold when the hand is not clenched' (press the 'M' key on the keyboard to switch between fire projectile and water projectile)
To reduce the overhead associated with projectile creation and destruction, we use pooling. When the player launches the game, the game creates a pool of pre-allocated objects for each type of projectile. When the player is about to fire a projectile, a projectile object is taken from the corresponding pool.
When the game starts, moving targets are constantly generated in front of the player. Targets move on a sin wave. When the projectile fired by the player hits the targets, the player will get a certain score. We also use pooling for targets. When the player launches the game, the game creates a pool of pre-allocated objects for targets. The target object is sequentially taken out from the pool over time.
The List timer is used to show the remaining time of the game and end the game when the countdown reaches 0. At the beginning of the game, initialize the list timer to 90. Decrease the value of the list timer by one every second. When the value of the list timer becomes 0, the game ends.
Score tracker is used to record the player's score. When the projectile launched by the player hits the target, the score tracker will increase by a certain value.
All the player's interactions with the game will be accompanied by audio. All audio is placed in the Sound folder under the Assets folder. There are different sound effects when the player clicks the button, when different types of projectiles are fired, and when they hit the target.
When the game is over, the player will be shown a finish screen with various buttons. Clicking the 'Leave the game' button on the finish screen will directly exit the game. Clicking the 'Try again' button on the finish screen will restart the game. Clicking the 'See game statistics' button on the finish screen will display the player's statistics.
In order to prevent mutual interference between the main project code and the test code, we created a new project for unit tests. The name of the Unit tests project is CHIPSZTest. We used the "Unit Test App (Universal Windows)" for our unit tests. We also make a "CHIPSZClassLibrary (Universal Windows)" project in our solution to hold the code that needs to be shared between the tests and the application.
We have a functioning Continuous Integration check implemented on our GitHub repository. This was a very challenging task for the group.
The CI includes installing the necessary software including .NEt and NuGet. Then the MSBuild is set up and the project is built.
As we are working with UWP, we have had to implement our unit testing in a separate project. Below is a screenshot of the tests passing.
We are currently figuring out a way to add the unit tests to our CI file.