Project 2

Build Instructions

1. Install Unity Hub from here.

2. Install Unity version 2019.4.28f1 from here by clicking the Unity Hub button for that version. Add the Android Build Support, Android SDK & NDK Tools, and OpenJDK modules when installing.

3. Install Blender 2.93 here for importing models into Unity.

4. Clone the project's GitHub repository into a folder using the git clone command or by downloading the project ZIP file by clicking Code -> Download ZIP on the GitHub repository page and extracting it.

5. Open Unity Hub, click the Open button, and select the project folder. Click on the project with the project folder name in Unity Hub to open it in the Unity Editor. The VRTK v4 packages should now install.

6. Open Assets/Scenes/ScareCoOffices.unity by double-clicking on it in the Unity Editor Project window.

To use a simulator in the Unity Editor, enable the CameraRigs.SpatialSimulator GameObject and disable the CameraRigs.UnityXR GameObject by selecting each of them in the Hierarchy window and toggling the checkbox in the top left of the Inspector window. Click on the play button at the top middle of the screen to start and stop the simulator. (Press the Escape key to unlock the mouse cursor.) Toggle the GameObjects again to return to being able to build for a headset.

7. Connect an Oculus Quest headset to your computer over USB. Make sure your Quest has developer mode on. Select Allow on your headset to allow your computer to access the headset's data.

8. Click on File -> Build Settings and select the Android platform. Select Oculus Quest in the Run Device menu. (Click Refresh if it does not appear.) Click on File -> Build And Run, select a file name and location for the APK file, and click the Save button. After building, the application should be open on the headset.

Models From Online

Models I Created

I created these models using Blender.

Sounds From Online

Ambient Sound: Fluorescent Light Buzz by Sauron974 on Freesound - https://freesound.org/people/Sauron974/sounds/273625/

Four Unique Sounds:
1. Button Click by JarredGibb on Freesound - https://freesound.org/people/JarredGibb/sounds/219478/

This sound plays when the user presses the button all the way down.

2. Fly Buzz by Kneedless on Freesound - https://freesound.org/people/Kneedless/sounds/167455/

This sound plays at the location of the fly near the trash and gets louder as the user gets closer.

3. Door Creak by JarredGibb on Freesound - https://freesound.org/people/JarredGibb/sounds/219499/

This sound plays when the cabinet is fully opened.

4. Splat by gprosser on Freesound - https://freesound.org/people/gprosser/sounds/360942/

This sound plays when a fly is destroyed using the fly swatter.

Frame Rate Screenshots

The overlay in these screenshots displays a graph of the headset frame rate in frames per second over time, with 0 FPS at the bottom and 72 FPS at the top.

Model Requirements

Interactable (Grabbable, Droppable, Tossable) Objects

1. Beetle

2. Fly Swatter

3. Ladybug

4. Crumpled Paper

5. Coffee Cup

Objects With Colliders

1. Trash Can

2. Trash Bag

3. Picnic Basket

4. Flower Pot

5. Cabinet

Interactable Objects That Generate Other Objects

1. Button - Generates a fly when pressed.

2. Cabinet - Generates a cockroach when fully opened after being fully closed.

Animated Models

1. Ant - Has a movement animation and a walking animation.

2. Fly (Near Trash) - Has a movement animation and a flying animation.

Lighting

The scene includes a point light near the table containing the beetle, the fly swatter, and the ladybug, a point light near the picnic area, and two point lights upstairs below the only fluorescent light model.

Difference Between Simulator and Headset

In the simulator, the user’s view, the left controller, and the right controller have to be swapped between and moved individually using the WASD keys and the mouse. Controllers move automatically with the camera when moving or rotating the user’s view in the simulator. For moving a controller, the mouse is used to rotate the controller and the keyboard is used to translate the controller. The keyboard and mouse controls for positioning a controller are difficult to use because the direction and position of the controller in 3D space is unclear when viewing the scene with a 2D view.

In the headset, the camera view and each controller can be moved simultaneously just from the user moving around their head and hands. Controller and view positioning is more intuitive in the headset because it involves physically moving with the corresponding part of the body and does not require aiming each controller. Holding down a trigger to grab an object in the headset is also more natural than holding left click in the simulator. Having control over both hands is another major difference between interaction in the simulator and the headset. For example, using a headset in my scene, the user can move the fly swatter in their left hand while pressing the button that spawns flies with their right hand. This behavior can be somewhat replicated in the simulator when the user has camera control, but each hand is not moving independently.

In the simulator, it can be difficult to tell where a controller is in relation to an interactable object, meaning that it is hard to position the controllers to pick up or interact with an object. A controller clipping into an object can indicate that the controller is touching that object. However, when an interactable object happens to line up with the position of one of the controllers while the user is controlling the camera view, then it is easy to interact with that object because the user can just left click to interact. For example, the cabinet in my scene can be interacted without having to move the controller by moving the view over to the cabinet, positioning a controller on the left side of the cabinet, holding left click, and moving to open or close the cabinet.

It is natural in the headset to get a sense of how big an object should be because it can be seen in 3D relative to the height of the user. How big an object should be in the headset is difficult to gauge in the simulator because the 3D scale the object will have is difficult to determine from a 2D image. In the simulator, the user cannot move their view vertically. This limitation makes closely looking at objects that are above or below the camera’s view impossible. In the headset, the user can move their head downward and get a closer view of an object in the scene, such as the crumpled paper or ant in my scene.

Additional Resources Used

This resources from the internet are also in the repository files:

UFO Model by hana on 3D Warehouse - https://3dwarehouse.sketchup.com/model/273a556e078133532296d88107d065f6/UFO

UFO Sound by Daniel Simion on SoundBible - https://soundbible.com/2213-Alien-Spaceship-UFO.html

Cow Model by Max M. on 3D Warehouse - https://3dwarehouse.sketchup.com/model/288b4047-1c6b-43e5-9b76-eb14ff9152fa/Cow

Roswell Logo from the Roswell New Mexico site - https://roswell-nm.gov/FormCenter/Convention-Civic-Center-9/Submit-a-Community-Event-53

Bounce Sound by Mike Koenig on SoundBible - https://soundbible.com/1120-Bounce.html

Mars Texture from NASA - https://nasa3d.arc.nasa.gov/detail/mar0kuu2

Typing on Keyboard Sound from SoundBible - https://soundbible.com/358-Typing-On-Computer-Keyboard.html

Office Chairs and Tables from Allsteel - https://www.allsteeloffice.com/design-resources/resources/2d-3d-models?brand=Allsteel

Avatar Idle Animation from Mixamo