Week 2: AR Implementation

AR Brick Breaker Implementation

In the second session of MIX1 we were given lab hours to work on our project so we started by adding the images we wanted to use as image targets to the Vuforia Database and we imported them to our Unity project. We added an AR Camera and two image targets. The first image target will be the player, and the other one will be level 1 of the game.

PlayerLevel1


Once we had set up the camera and image targets we proceeded to add the models. The player consists of a paddle that the user will move around to hit the ball. The level 1 consists of a board, some walls, the bricks and the ball. At this point we had all the elements so we tried to run it on our phone devices but this took us a little more time than we expected so we decided to keep working on the weekend. 

On Saturday we worked on adding the properties and scripts. We started by adding a collider and a bouncy material to all the walls, the bricks, the ball, and the paddle from the player so every time the ball hits one of these elements it will bounce back. For the base plane we added a normal surface physical material



Once we started running the project we lost the ball since it escaped the room, so we needed to add a script to try to control gravity, what we did is adding two functions to enable and disable kinematic. We wanted to enable kinematic when the target is founded and disabled it when we lose it, so on the Level’s Image Target we added the following:



We also added a rigid body to all the elements, this allowed gameObjects to react to real-time physics such as gravity force. Now we had the ball on the board but it was not working exactly as we wanted, we tried to add a force which made it better but the ball would lose velocity to the point of stopping completely, so we decided to do more research.

Since we had multiple bricks we added the block to the prefab folder so we could copy it as many times as we wanted. We also added an invisible top plane to make sure that all the ball will never get out of the level plane.

The bricks needed to be destroyed when hit by the ball, to do that we added a script with a OnCollisionEnter function, in order to be able to select the ball we had previously added a tag to the ball element. 


At this point we had most of the project done but the ball movement was not fully what we were looking for and we couldn’t find out why so we decided to ask our teacher Kasper and fix it next week.

Comments

Post a Comment

Popular posts from this blog

Week 4: Markerless Implementation and Finalisation

Image
Markerless Virtual Worlds At this point, we have some of the project done and running, such as detecting planes and displaying the portal on the new plane, now we have to work on travelling to Paris when the user enters the portal. First, we start by finding a suitable 360 video, that we be the virtual world behind the portal. We found a video that is about Paris and it shows the main attractions there plus captions of what landmarks they are showing at the moment, which is really cool, so we downloaded it and imported it to the assets in our project. Our goal now is to add the video to the scene, and since it’s a 360 video, a sphere is perfect to have the video playing on the circumference of the sphere.  So we created a sphere and we scale it up to 50, so it becomes the new virtual world. We attach a Video Player component to it and add our video as the Video Clip. Now, the video is playing on both sides of the portal, but we want it to only play on the other side, to do so, we s...
Read more

Week 3: AR Final Result

Image
AR Brick Breaker Finalisation  This week we finished the project, Kasper recommended using velocity on FIxedUpdate() so the function will be executed periodically while our game is running.  This fixed our problem with the balls’ behaviour, we also angled the side walls so we wouldn’t end up in an infinite loop. This is a video showing the final result:
Read more

Week 10: Project finalization

Image
VR Escape Room  Finalization We tried many ways to make the buttons pressable, and only one way worked for us, which is by using animations. So we started by creating the animation, which is a simple change in the position of the button.  Then, we only want the button to animate if the player presses it, so we need a trigger to start the animation. After creating the button’s animation, we double click on the animator to get its window. By default, the animator will look something like this: Which means that as soon as the button is instantiated, the animation will start. But we wanted to only start when the player presses it. So we replaced the default state of the button with a new empty state that we just created and we set it as default. Next thing is to create a transition between the new default state and the ButtonAnimation, and also the transition between the buttonAnimation and the default state, so, back and forth. We also create a boolean parameter to the animator t...
Read more