The VR escape room game project - part 3

The puzzles in the escape room are all in a different scene, but they all use the same garage as location. Whenever the players complete a puzzle, the scene is changed and they are presented with the next puzzle. This is achieved by calling the SceneManager.LoadScene() method. 

The player can also teleport or use snap turns instead of walking around, making it easier to explore the whole room, even if you don't have enough space in real life or want to stay stationary. This is achieved by the Locomotion System under XR Origin, which has 3 scripts: Locomotion System, Teleportation Provider and Snap Turn Provider. On both controllers, there is an XR Ray Interactor and  XR Interactor Line Visual script which show a line coming from the controllers to help players visualize where they want to move. The floor is set as the Teleportation Area, so players can only teleport within the room. 

Locomotion System Scripts
Controller Scripts and components


Puzzle 1 - Buttons:

In this puzzle, the player in VR can see 2-4 buttons and some different tools on the tool rack. "Mission control" has to decide based on the number of buttons and which tools are present, which is the correct button to push. When the correct button is pushed, the puzzle is completed. 

There are 12 scenarios in total, and the current scenario is decided by a random number generator. Then based on the number, the correct scenario is set up by setting the correct tools and buttons to active in the scene and saving the correct button to push. Then on button push, it's checked if the pushed button is the same as the correct button. If it is, we load the next puzzle. If it's not, a new scenario is created and the players have to start over. 

A scenario is set up with the correct game objects activated
A scenario is set up with the correct game objects activated


Puzzle 2 - Sound:

The player in VR has to determine where the sound is coming from and interact with the correct object. When they do, a victory sound will play and then they have to interact with the small stool to complete the puzzle. 

The audio source is set randomly to one of the target game objects (e.g. table, locker) which can be the current object that emits the sound. Then the interactable of that game object is saved in a variable and a Coroutine is started to play the sound on a loop. On Update we check if the saved interactable is selected. When it is, the Coroutine is stopped and the player has to interact with the stool to complete the puzzle. After they do, the new puzzle is loaded. 

A possible audio source is set as Target
The stool is set as SecondTarget, which completes the puzzle

Puzzle 3 - Labyrinth:

The player in VR has to walk around the square grid on the floor to see the favorite tool, then they have to walk around the room to find that tool, which has a code on it. Based on the code, "mission control" can determine the blueprint for the labyrinth and guide the VR player through it. There is a correct path the player has to go through to grab a cube at the end. When they have that cube, they have to throw it on the correct square to complete the puzzle. 

The favorite tool, it's position and the labyrinth blueprint are all decided based on a random number generator. Each square in the grid has a trigger. When the player comes in contact with one of the squares, it's checked whether the player is allowed to touch it. If not, the player's position is reset to the beginning. When the player comes in contact with the correct square, they are allowed to stand on it, and continue their path through the labyrinth based on the blueprint. The same technique is used to determine if the cube is placed on the correct square. After it is, the players have completed the last puzzle, and thus won the game. 

Code on the tool
Favorite tool

Author: Anett Barát











Kommentarer

Send en kommentar

Populære opslag fra denne blog

XR project final part and XR Expo

Billede
This last post on this blog will concern the final version of the XR barcade project, as well as some notes on the XR Expo, where we have demoed this project.   Sadly, not all features could be in the final version of the project. The biggest one, probably, is the multiplayer. This was due to the fact that, apparently, the Coherence plugin is apparently not compatible with the Oculus plugin – and, this being a VR experience, the Oculus plugin had to take priority. Obviously, this also had the consequence of the Movement SDK parts being deemed unnecessary, and removed. We all regretted this decision, but we had no other option. Regardless, we feel we have gained valuable experience from this as well – learning that a problem cannot, at least with our current tools, be solved is an important thing to any developer. In cases like this, the only thing we can do is abandon it, and focus on what we CAN solve – which we did.   In the final version of the project, three elemen...
Læs mere

Individual reflections - Kristóf Lénárd

I feel that I have gained a lot from this course. I have learned things about different types of AR, both marker-based and markerless, and have learned about VR. I have learned when to use it, how to develop apps for these, what makes these different from “regular” apps, and why is it a very quickly developing and growing field. During development, I have contributed to the marker-based AR app in the development of the code, contributed to the markerless AR app in the AR code and model creation, contributed to the VR app by developing one of the levels and in the sound design of the escape room game, and contributed to the XR app by helping the others, both in code and in general Unity development, along with adding a few bits of models, code, and sound design. Sadly, for the XR project, the main feature I attempted to develop, that is, multiplayer experiences in VR, has failed, as the package I used to develop networking was not compatible with the Oculus XR plugin. In the followi...
Læs mere

Individual reflections - Christian

My main contributions for the four projects are as follows:       - Marker-based AR project: Brainstorming, unity implementation, animation setup.       - Marker-less AR project: Brainstorming, model acquisition, portal doors & animation, interaction            script       - VR app: Brainstorming, codebreaking implementation (my own level), keypad interaction       - XR app: Brainstorming, pool level (ended up not working), general support role afterwards In the following sections I will reflect on the projects and the knowledge I have gained throughout the course.  The marker-based project was a very weird one. Of course, it being the first project we have makes it very limited in scope, but it was also plagued by technical issues from the SDK we were using. Vuforia created a lot of problems, especially for me as I was in charge of the main Unity implementation. Technical issues ...
Læs mere