Week 9: VR Escape Room Implementation

 Escape Room Implementation

We started this week by creating the fire and the fireplace. At first, we tried to search for an asset bundle that has both, but we ended up only finding separate ones for each of the fire and the fireplace. So we first downloaded the fireplace asset and added it to the corner of the room. Then we found a cool campfire asset that we can add to the fireplace. This asset gives a really nice fire effect (lights, sparks, sounds, smoke,...) so that helped us at this point.

We need the fire to be on when the game starts, and then the player should turn it off to find the key to the outer door. So we created a script for the fire, that makes it turn off as soon as the bucket collides with it. Which means that the water turned it off. 

In the following snippet, you can see that if the bucket collider triggers the fire’s collider, and the bucket is full of water, the fire will turn off.




Next step is to add the key to the door that the player will use to escape the room. We also found a key asset on the asset store and added it to the scene. We put it in the fireplace and inactivated it. We want it to show up as soon as the fire is off.

So we added to the fire script, the logic that would make the key appear. So we extended the last snippet to be:



And we also added the grabbable script to the key so that the player can grab it.


Next step is to find a suitable puzzle for the scene, and a controller with many buttons, and only one button represents the correct answer, so that the player has to hit that button to turn on the water tap.

So we added a plane and we put it on the table next to where we will add the buttons controller. We created a new material with a shader of type “Legacy Shaders/Diffuse”, and we added the image of the puzzle as the texture of the material, as the following figure shows:



We found a controller box with buttons that we can add to the scene and next week will make the logic of pressing the buttons.


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