Project1W19

From Immersive Visualization Lab Wiki
Revision as of 14:18, 11 January 2019 by Jschulze (Talk | contribs)

Jump to: navigation, search

Homework Assignment 1: Trapped By a Big Wall

The project is almost ready, but we're still fine tuning it. Feel free to start working on it but check back in tonight (1/11) to see if any changes were made.

For this assignment you can obtain 100 points, plus up to 10 points of extra credit.

In the description below we assume you will be using Unity 3D for the implementation. But you don't need to, you can alternatively use UE4, Lumberyard, CryEngine, or C++ with OpenGL and optionally OpenSceneGraph and the Bullet Physics Library

Note that if you use Unity you aren't allowed to use any Unity assets other than 3D models, textures and audio-related ones without explicit permission.

The goal of this assignment is to create a VR application that is only used with the Oculus HMD (no controllers), and in which the user has to break out of a cylindrical brick wall.

This is a team project for teams of two. You are allowed to work solo on it, but this does not change the scope of the project.

The Project (100 Points)

Create an interactive, immersive application for the Oculus Rift head mounted display (HMD). In the application, you are trapped inside of a seemingly impenetrable, tall, beautiful cylindrical brick wall - except that the budget wasn't big enough to include mortar, so the bricks just sit loosely on top of each other. Luckily, you have telekinesis superpowers that you can use just by using your gaze. When you focus on a brick (by staring at it), you will be able to push or pull the brick out of the wall, and it will fall down on the ground. The goal is to remove enough bricks from the wall so that you could get to the outside.

In this application you are only allowed to use the HMD as an input device. Mouse, keyboard, Touch controllers, or other input devices are not allowed. You are not allowed to move the user, except the user's head with their natural head motion. The brick wall should be about 3-6 feet from the user.

You will get points for the following things:

  • A ground plane for the wall to rest on and give it a texture, such as grass, dirt, concrete, etc. (10 points)
  • A cylindrical wall of bricks, generated procedurally from code. It should consist of simple rectangular boxes. The bricks need to be textured or colored with a texture/color of your choice. In Unity, you should create a brick prefab and instantiate the wall using instances of that prefab. The bricks must have realistic physics properties applied to them. Assume that 1 cubic foot of brick weighs about 200 lbs. (30 points)
  • Telekinesis: when the user stares at a brick for a minimum threshold amount of time (e.g., 2 seconds), telekinesis kicks in. The brick the user stares at is now linked to the user's head, and will move towards the outside or inside of the wall when the user moves their head towards or away from the brick. The physics simulation should realistically make the bricks above the removed one tumble down. Note that the brick should only move along its radial axis (the axis parallel to the radius of the cylinder). (30 points)
  • Add a visual indication of which brick is being selected except when the user is not looking at the wall (e.g., a cursor, highlight, sparks, etc). Change the color of the indicator when telekinesis activates. (10 points)
  • If the user looks away from the selected brick beyond a certain threshold angle, the brick should stop moving. (10 points)
  • You should be able to reset the wall by looking straight up to the sky, within a small threshold around the zenith. (10 points)

Let these images inspire you:

Brick-cylinder.jpg Brick-wall.jpg

Left: brick wall from the outside, brick size is about right. Right: brick wall from user's perspective (but your bricks should be bigger).

Extra Credit (10 Points)

There are two options for extra credit. To get the full 10 points you have to implement both of them, in the given order.

1. Telekinesis trigger indicator: all gaze interactions would benefit from a visual indicator of how long the user has stared at a point and how much longer they need to do it to trigger the action. Any visual progress indicator located by the object that is looked at will be accepted (such as progress bars, pie charts, shapes that fill up with water), but not textual ones (such as a count down). (5 points)

Examples:

Radial widget: Radial.png Slider widget: Slider.png Hexagons: Hexagons

2. Teleport with gaze: This option requires that you already did option 1. Add a method to teleport around the scene by gazing at the ground plane. If there is an intersection of the gaze ray with the ground plane, without an obstruction in between, mark the intersection point, start the gaze progress indicator, and once the time is up move the user's feet to that location. (5 points)