Project 2 - Every Day is Halloween

Due 10/22/18 at 8:59pm Chicago time

Project 1 focused on Augmented Reality, looking and interacting with objects at the table-top scale. This project is focused on immersive Virtual Reality at room scale. This project will give you some experience with building virtual worlds for people to move around in and interact with.

As this project is due near the end of October we are going to do a Halloween themed project, and in particular a VR Funhouse. This funhouse will have a number of rooms = 1 X # of undergraduate students in the group + 2 X # of graduate students in the group. The requirements given below in the Implementation section are per room.

The user should be able to move through a series of rooms, usually by walking or crawling, but no teleporting. You may need to have some additional hallways or foyers connecting the rooms which do not count towards the room totals. As in any funhouse the guest can ward off danger, or move away from danger, but cannot fight the danger, so no guns, no swords, no overt weapons.  The user is a human being with reasonable human abilities. All of the rooms should belong to the same theme - it should not look like n different people each did their own thing. That theme is pretty flexible but the funhouse should have G or PG level scares. It could be classic funhouse scares, or maybe big insects, or high-school, or the 80s - it should be some fear that people relate to. While it has potential for great fear, I am declaring this project a politics free zone, so that topic is off limits. Note that unlike the real world, this virtual funhouse does not need to be in enclosed spaces - it could take place in a virtual outdoors, as long as the user is limited to moving in a 3 m by 3m area. Be sure to make use of the full potential field of view including the ground / floor and sky / ceiling.

The user should carry some kind of light in one of their hands - this could be a torch, or a flashlight, or a cellphone acting as a flashlight, or a camera that you can trigger the flash on, or something similar. This object should make some localized sounds (i.e. you hear the sound of the flash powering up, or the sound of the flames of the torch). The user should be able to carry things in their other hand that can help them make their way through the funhouse. To move from room to room the user will need to do some form of interaction, e.g. pick up a key and put it in the lock, open a trap door, move some boards out of the way, break a window, using virtual objects in one or both hands. This interaction should be enjoyable / interesting / exciting / slightly challenging. Since this funhouse is being built in VR it is most likely necessary to have the user move through a series of rooms and hallways that would occupy the same physical space in the real world - i.e. you are reusing the same 3x3 meter space for multiple rooms. With a 2 or 3 person team there needs to be at least one time where the user needs to walk or crawl from one room to another. With a 3 person team there needs to be at least one time where the user needs to jump or fall from one room to another.

The funhouse should include ambient audio (sounds or music) as well as sounds when the user interacts with certain objects, or gets close to certain objects. The Funhouse should have appropriate (likely scary) lighting.

The user should be able to walk through your funhouse, so make sure you are leaving enough space.


If you want to see a commercial version of this kind of interaction and space remapping, try this YouTube video of Unseen Diplomacy - https://www.youtube.com/watch?time_continue=89&v=xzntLYGwWrM




Implementing the Project

This project will be a group project and you should form groups of your choice with 2 or 3 members. As soon as you have formed your group send an email to andy so he can approve it.


You will have a 3 meter by 3 meter (10 foot by 10 foot) area to work where we demoed the VIVE apps in the classroom

To get a C on the project ...


To get a B you need to add to each room ...

To get an A you need to add to each room ...

Be careful when you are collecting or creating models for your space as the polygons start to add up and you want to make sure you maintain a good interactive frame rate in stereo on the classroom VIVE PC

Also, keep in mind that your objects can be at different scales - some of them might be the size of tables that help fill the space but others might be smaller objects on a table, but they all need to be visible at some point (i.e. they could be hidden in drawers). You also want to encourage the user to look around, so the ceiling and the floor are also good places to put objects.

Note that there is a very big difference between getting something working and getting it working well. The first is not that hard. The second takes much more time. You are expected to have things working well, so be sure to test on the actual hardware regularly.

Note that SteamVR was updated to version 2.0 earlier this month which currently breaks VRTK compatibility. For now you should stick with version 1.2.3 of the SteamVR Unity Plugin. All of the versions are available on GitHub at https://github.com/ValveSoftware/steamvr_unity_plugin/releases


Turning in the Project

The classroom VIVE PC will have a folder on the desktop named 491VRAR_Project 2. You should put a copy of your executable and its associated data folder into a folder named after you, and then put that folder into the 491VRAR_Project 2 folder.
Be sure to test and make sure your project runs well through the VIVE and its controllers on that PC as that is where they will be shown in class and officially graded.

You should create a set of public web pages (available to anyone for at least the duration of the course) that describe your work on the project. You can host your web pages at UIC (http://people.uic.edu) or the provider of your choice, as long as they remain publicly available to all. You can use any publicly available templates as long as you cite them, or create your own.

These pages should include:

all of which should have plenty of screenshots with meaningful captions. Web pages like this can be very helpful later on in helping you build up a portfolio of your work when you start looking for a job so please put some effort into it.

You should also create a 2-3 minute YouTube video showing the use of your application including narration with decent audio quality. That video should be in a very obvious place on your main project web page. The easiest way to do this is to interact with the video in the classroom or the EVL main lab in front of the tiled LCD screen showing what you are seeing - this way people watching can see you interacting and what you are seeing. You can try to narrate while interacting but you will most likely find its useful to do some editing afterwards to tighten the video up.

The web page including screen snapshots and video need to be done by the deadline so be sure to leave enough time to get that work done. Once you have your webpage done, send the URL to Andy before the deadline. I will respond to this email as your 'receipt'. I will be linking your web page to the course notes so please send me a nice representative jpg or png image of your application for the web. This should be named p2.<your_last_name>.pg or p2.<your_last_name>.png and be roughly 1024 x 768 in size.

When the project is done, each person in a group should also send Andy a private email with no one else CC'd ranking your coworkers and yourself on the project on a scale from 1 (low) to 5 (high) in terms of how good a coworker they were on the project. If you never want to work with them again, give them a 1. If this person would be a first choice for a partner on a future project then give them a 5. If they did what was expected but nothing particularly good or bad then give them a 3. By default your score should be 3 unless you have a particular reason to increase or decrease the number. Please confine your responses to 1, 2, 3, 4, 5 and no 1/3ds or .5s please.



Presenting the Project

An important part of creating VR applications is getting feedback and using it to improve your design.

We will be spending time in class for each person to show off their work.
Given the number of groups, each group will have <5> minutes to present their project, and then we will have 8 minutes for questions from the other groups.

Teams

1
Takkar, Manchundiya
link
2
Rastogi, Kulkarni link
3
Bellini, Santambrogio, Marziali link
4
Taj, Atra
link
5
Alam, Condrella link

6
Tricarico, Sandrelli link
7
Haynie, Hughes link1

link2
8
Jaiswal, Lee link1

link2
9
Akintoye, Arellano, Norman link
10
Janowski, Stranczek link
11
Krishnamoorthy, Thiruvarpu Neelakantan link
12
Kuhn, Lubek link
13
Datta, Vannia Samy, Phaltankar link
14
Dolat, Almoujahed link

link
15
Jamal, Kidwai, Vega link
16
Bhurani, Jhanwar link
17 Sonzogni, Mantovani link

18
Hruby, Huynh link1

link2

link3
19 Nishimoto, Tran link
20 Molina




last updated 10/7/18 - more groups formed
10/2/18 added more specificity to the B and A range
9/27/18 - Added link to Unseen Diplomacy video
9/24/18 - added note about current VRTK incompatibilities with SteamVR 2.0