Difference between revisions of "Project4W17"
(→Homework Assignment 5: Final Project) |
(→Homework Assignment 4: Final Project) |
||
| (18 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
=Homework Assignment 4: Final Project= | =Homework Assignment 4: Final Project= | ||
| + | |||
| + | '''Update:''' [https://www.youtube.com/playlist?list=PLVeFryXWi1z-5SQkzPS-ytCBaWZdQhdRo Here's the playlist] of the final projects in Winter 2017. | ||
For this assignment you can obtain 100 points, plus up to 10 points for extra credit. | For this assignment you can obtain 100 points, plus up to 10 points for extra credit. | ||
| Line 7: | Line 9: | ||
The project is designed to be a team project for two people, just like the other projects this quarter. | The project is designed to be a team project for two people, just like the other projects this quarter. | ||
| − | The goal of this project is to create a 3D application for the Oculus Rift with either the Touch controllers or the Leap Motion. The following rules apply: | + | The goal of this project is to create a 3D VR application for the Oculus Rift with either the Touch controllers or the Leap Motion. The following rules apply: |
* The application cannot be based on any of the previous homework projects. | * The application cannot be based on any of the previous homework projects. | ||
* The application cannot use input devices other than Touch or Leap. Specifically, it cannot use keyboard or mouse. | * The application cannot use input devices other than Touch or Leap. Specifically, it cannot use keyboard or mouse. | ||
| − | |||
* '''Important:''' If your application uses the Touch controllers, you are only allowed to use two buttons on each controller. Which buttons is your choice. You're not allowed to use the joysticks on the controllers. | * '''Important:''' If your application uses the Touch controllers, you are only allowed to use two buttons on each controller. Which buttons is your choice. You're not allowed to use the joysticks on the controllers. | ||
| + | * Each team (regardless of number of members) has to implement at least 7 skill points worth of technical features, based on the list below. | ||
| + | |||
| + | Technical Features and Skill Points: | ||
| + | |||
| + | * Selection: 1 skill point (+1 for two-handed/flashlight/image plane/go-go/scaled-world-grab/voodoo-doll) | ||
| + | * Manipulation: 1 skill point | ||
| + | * Wayfinding: 1 skill point | ||
| + | * Travel: 1 skill point | ||
| + | * System Control (e.g., menu): 1 skill point for each type of widget, max. 2 skill points: action/toggle button, dial/slider, choice list, sub-menu, etc.) | ||
| + | * Symbolic Input (e.g., text input): 2 skill points | ||
| + | * Custom gesture: 1 skill point (in addition to the points for the technical feature it falls under) | ||
| + | * Audio: 1 skill point (needs to be done throughout the application, not just one effect or background music) | ||
| + | * Pilot study for usability evaluation: 3 skill points (requires user study protocol, at least 5 participants, post-study questionnaire, statistical evaluation; presented as slide show) | ||
| + | * Use of [https://unity3d.com/learn/tutorials/topics/scripting/quaternions quaternions] for all rotation calculations: 1 skill point (need to show code to graders) | ||
| + | * Collaboration: 2 skill points. Link up two computers to allow two users to collaborate in VR. Each user needs to be visible in VR for the other user as an avatar (minimum: head and hands). | ||
| + | |||
| + | We may extend this list throughout the duration of the project. | ||
You are allowed to use Unity, Unreal, Lumberyard, OpenGL/C++ for the implementation. While the use of asset stores is allowed for textures and 3D models, any other use of assets from the asset store requires permission from the instructor or one of the TAs/tutors. | You are allowed to use Unity, Unreal, Lumberyard, OpenGL/C++ for the implementation. While the use of asset stores is allowed for textures and 3D models, any other use of assets from the asset store requires permission from the instructor or one of the TAs/tutors. | ||
| Line 25: | Line 43: | ||
* Presentation (90 points) | * Presentation (90 points) | ||
* Extra Credit (10 points) | * Extra Credit (10 points) | ||
| − | |||
==Documentation (10 Points)== | ==Documentation (10 Points)== | ||
| − | You need to create a blog to report on the progress you're making on your project. You need to make at least two blog entries to get the full score. The first is due on '''Sunday, March 12th at 11:59pm''', the second is due on '''Sunday, March 19th at 11:59pm'''. You also need to make a short video clip of your application, and reference it in your blog. | + | You need to create a blog to report on the progress you're making on your project. You need to make at least two blog entries to get the full score. The first is due on '''Sunday, March 12th at 11:59pm''', the second is due on '''Sunday, March 19th at 11:59pm'''. You also need to make a short video clip of your application, and reference it in your blog. The video is due on '''Tuesday, March 21st at 11:00am'''. |
The first blog entry needs to contain (at a minimum) the following pieces of information: | The first blog entry needs to contain (at a minimum) the following pieces of information: | ||
| Line 36: | Line 53: | ||
* The names of your team members. | * The names of your team members. | ||
* A short description of the project. | * A short description of the project. | ||
| + | * Which technical features you are planning on implementing. | ||
* What you are planning on spending your creative efforts on. | * What you are planning on spending your creative efforts on. | ||
| + | * A screen shot of your application in its current state. | ||
| − | In week 2 you need to write about the progress you made, and mention any changes you have made to team, project title, or implementation plans. You also need to | + | In week 2 you need to write about the progress you made, and mention any changes you have made to team, project title, or implementation plans. You also need to post another screen shot. |
The video is due on presentation day and should be about 1 minute long. You don't need to use editing software, but you should use software to capture your screen to a video file. Screen recording software, such as the [https://obsproject.com/ Open Broadcaster Software], is available free of charge for Windows and Mac, on the Mac you can use [http://www.apple.com/quicktime/download/ QuickTime]. Audio is optional. Embed or link to the video from your blog. | The video is due on presentation day and should be about 1 minute long. You don't need to use editing software, but you should use software to capture your screen to a video file. Screen recording software, such as the [https://obsproject.com/ Open Broadcaster Software], is available free of charge for Windows and Mac, on the Mac you can use [http://www.apple.com/quicktime/download/ QuickTime]. Audio is optional. Embed or link to the video from your blog. | ||
| Line 45: | Line 64: | ||
The points are distributed like this: | The points are distributed like this: | ||
| − | * Blog entry #1: | + | * Blog entry #1: 4 points |
* Blog entry #2: 3 points | * Blog entry #2: 3 points | ||
| − | * Video: | + | * Video: 3 points |
| − | + | ||
| − | + | ||
| − | + | ||
==The Application (90 Points)== | ==The Application (90 Points)== | ||
| − | The final project has to be presented during our final exam slot on ''' | + | The final project has to be presented during our final exam slot on '''Tuesday, March 21st starting 11:30am'''. |
| + | |||
The points for your project are based on the demonstration, and will be distributed as follows: | The points for your project are based on the demonstration, and will be distributed as follows: | ||
| − | * Technical quality: | + | * Technical quality: 70% (10% per skill point) |
| − | * UI Usability: | + | * UI Usability: 15% |
| − | * Creativity: | + | * Creativity: 15% |
| − | The scores will be determined by the course staff (instructor, | + | The scores will be determined by the course staff (instructor, TAs, tutors). You need to let a course staff member try your application so that we can determine the UI usability score. Creativity will be subjectively graded by the course staff. |
| − | + | ||
| − | + | ||
==Extra Credit (10 Points)== | ==Extra Credit (10 Points)== | ||
| − | We want to reward projects that go beyond what we ask for. Please contact the course staff | + | We want to reward projects that go beyond what we ask for. Please contact the course staff with ideas for things you think should qualify for extra credit. We will give you guidance, but the final decision on the extra credit will be made by all graders after the final presentations. |
| − | We | + | |
| + | Even without prior conversations with the course staff, we may decide that you deserve extra credit for your project. | ||
| − | + | Areas we will particularly consider for extra credit are: innovative interaction concepts, overall aesthetics, UI widget design, creativity, exceptional execution of technical features, well thought out usability, entertaining projects. | |
Latest revision as of 20:11, 21 March 2017
Contents |
Homework Assignment 4: Final Project
Update: Here's the playlist of the final projects in Winter 2017.
For this assignment you can obtain 100 points, plus up to 10 points for extra credit.
This homework assignment is due on Tuesday, March 21st at 11:30am.
The project is designed to be a team project for two people, just like the other projects this quarter.
The goal of this project is to create a 3D VR application for the Oculus Rift with either the Touch controllers or the Leap Motion. The following rules apply:
- The application cannot be based on any of the previous homework projects.
- The application cannot use input devices other than Touch or Leap. Specifically, it cannot use keyboard or mouse.
- Important: If your application uses the Touch controllers, you are only allowed to use two buttons on each controller. Which buttons is your choice. You're not allowed to use the joysticks on the controllers.
- Each team (regardless of number of members) has to implement at least 7 skill points worth of technical features, based on the list below.
Technical Features and Skill Points:
- Selection: 1 skill point (+1 for two-handed/flashlight/image plane/go-go/scaled-world-grab/voodoo-doll)
- Manipulation: 1 skill point
- Wayfinding: 1 skill point
- Travel: 1 skill point
- System Control (e.g., menu): 1 skill point for each type of widget, max. 2 skill points: action/toggle button, dial/slider, choice list, sub-menu, etc.)
- Symbolic Input (e.g., text input): 2 skill points
- Custom gesture: 1 skill point (in addition to the points for the technical feature it falls under)
- Audio: 1 skill point (needs to be done throughout the application, not just one effect or background music)
- Pilot study for usability evaluation: 3 skill points (requires user study protocol, at least 5 participants, post-study questionnaire, statistical evaluation; presented as slide show)
- Use of quaternions for all rotation calculations: 1 skill point (need to show code to graders)
- Collaboration: 2 skill points. Link up two computers to allow two users to collaborate in VR. Each user needs to be visible in VR for the other user as an avatar (minimum: head and hands).
We may extend this list throughout the duration of the project.
You are allowed to use Unity, Unreal, Lumberyard, OpenGL/C++ for the implementation. While the use of asset stores is allowed for textures and 3D models, any other use of assets from the asset store requires permission from the instructor or one of the TAs/tutors.
You are welcome to use the TA/tutors' office hours to brainstorm ideas with them, as well as for help during your work on the project, like for the other homework projects.
Grading
Your final project score consists of three parts:
- Documentation (10 points)
- Presentation (90 points)
- Extra Credit (10 points)
Documentation (10 Points)
You need to create a blog to report on the progress you're making on your project. You need to make at least two blog entries to get the full score. The first is due on Sunday, March 12th at 11:59pm, the second is due on Sunday, March 19th at 11:59pm. You also need to make a short video clip of your application, and reference it in your blog. The video is due on Tuesday, March 21st at 11:00am.
The first blog entry needs to contain (at a minimum) the following pieces of information:
- The name of your project.
- The names of your team members.
- A short description of the project.
- Which technical features you are planning on implementing.
- What you are planning on spending your creative efforts on.
- A screen shot of your application in its current state.
In week 2 you need to write about the progress you made, and mention any changes you have made to team, project title, or implementation plans. You also need to post another screen shot.
The video is due on presentation day and should be about 1 minute long. You don't need to use editing software, but you should use software to capture your screen to a video file. Screen recording software, such as the Open Broadcaster Software, is available free of charge for Windows and Mac, on the Mac you can use QuickTime. Audio is optional. Embed or link to the video from your blog.
You are free to create the blog on any web based blog site, such as Blogger or WordPress. You should use the same blog each time and just add new blog entries. You are free to add more entries than the required ones.
The points are distributed like this:
- Blog entry #1: 4 points
- Blog entry #2: 3 points
- Video: 3 points
The Application (90 Points)
The final project has to be presented during our final exam slot on Tuesday, March 21st starting 11:30am.
The points for your project are based on the demonstration, and will be distributed as follows:
- Technical quality: 70% (10% per skill point)
- UI Usability: 15%
- Creativity: 15%
The scores will be determined by the course staff (instructor, TAs, tutors). You need to let a course staff member try your application so that we can determine the UI usability score. Creativity will be subjectively graded by the course staff.
Extra Credit (10 Points)
We want to reward projects that go beyond what we ask for. Please contact the course staff with ideas for things you think should qualify for extra credit. We will give you guidance, but the final decision on the extra credit will be made by all graders after the final presentations.
Even without prior conversations with the course staff, we may decide that you deserve extra credit for your project.
Areas we will particularly consider for extra credit are: innovative interaction concepts, overall aesthetics, UI widget design, creativity, exceptional execution of technical features, well thought out usability, entertaining projects.
