Week 5: Virtual reality Introduction

IDEA


We started our work with looking for ideas for our VR project. After watching a few videos on YouTube and downloading and playing some demos to get inspiration, we decided we would like something that will make us move and will be 100% involved. Initial idea was the game with objects moving fast towards the player. The player should move in a way to avoid being hit by the moving object. After considering all pros and cons, we realized that if we go with this idea, we wouldn’t really use the controllers. That is why we decided to change “escaping” from the objects into hitting them.

The final decision was to create a game with principals of “Beat Saber”. The player is keeping red and blue sabers and needs to hit the moving red and blue cubes that are positioned in different angles. The red objects should be hit with red saber in the right direction and the same goes to the blue.


SETTING UP UNITY AND OCULUS SET


After choosing the idea we started to set up OCULUS device. We used already existing account, but developer mode was off, and we could not switch it on. That is why we needed to reset factory settings to have developer mode on. To do that we needed to set up our own user account and developer account in the phone.

To enable the device for development we connected it with the USB cable to the computer and we allowed the access.

Next step was importing the oculus integration package from assets store to get core VR features, components, scripts, and plugins to ease and enhance the Oculus app development process in Unity.

We created our Unity project and configured build settings where platform needed to be changed into Android and Texture compression set to ASCT. In project settings we set minimum API level to Android version 6.0 API level 24. To enable VIRTUAL REALITY support we installed XR plugin Management. After that we installed OCULUS XR plugin for Android.

After we played around with the headset and tried to connect it to unity with a simple project, we saw that unity became way slower after adding the VR dependency so we decided that, next week, we will create a new project and start by creating the scene and when the scene is almost ready, we will add the VR stuff.

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