Project 3: Try what you want
The goal of project 3 is to let you work on a VR or AR project of your own choice, subject to my approval. You can also extend project 2 as instructed at your presentation (please list all improvements that you want to do).
Proposal phase - by 11am Saturday, April 21 to me: tommy.dang[at]ttu.edu you should create a github project and the Readme file that describes the project that you want to do.
This project description should include
General description of the project including why VR or AR will be beneficial here.
Which hardware platform or platforms you want to develop your application for
What software you plan to use to write the application
Who is on your team (1-4 people teams) and what their roles in the project are
Links to any datasets or libraries or archives of images or objects that you plan to use
Once I approves of your project you move onto the implementation phase. Otherwise, you need to select a different project and resubmit it by 11am Sunday, April 22.
I will then make links to all those projects available on the class webpages so everyone can see what everyone else is doing.
Project screenshot (a 1200 x 600 jpg image of your work which should be named p3.<your_last_name1><your_last_name2>.jpg, demo link, video link, and github link are due at 11am Sunday, May 6 to the TA: vinh.nguyen[at]ttu.edu.
- This project is 25% of your final grade:
- 15% for design and implementation.
- 5% for in-class presentation.
- 5% for project report on Github.
The presentation schedule should look like this.
You can update your source code and project report until 11am Tuesday, May 8.
Each student needs to send a peer evaluation for other teammates by 11am Thursday, May 10 to the TA: vinh.nguyen[at]ttu.edu. Forget submitting the peer evaluation cost 2% of your total grade. This peer evaluation is significant to your individual project grade. One team member can get A, but another can get D or Fail (team score is the average). The peer evaluation contains:
Group id and teammate name.
Rating from 0 to 10 (10 is best).
One to three sentence review (about how you came up with your teammate rating).
Your presentations start on Tuesday, May 8 (11am). But you may volentter to present a week before.
I will then make links to all those projects available on this page so everyone can see what everyone else is doing.
Your project will be evaluated on the following dimensions:
The main point is creating a strong connection between Virtual and Reality
- Technical challenging
- Educating. Science behind your work such as Water vaporization or social characteristics when proposing a rescue solution
- Visual appealing
- Sound effect
Testing your VR:
Hardware: Google Cardboard, oculus rift, or other VR head sets.
We have 2 cardboards and 2 oculus rifts at our lab (EC CS 305) for testing.
Don't stick with all the bullet points above, but use them as suggestions for your project. Feel free to bring in your own requirements and create your designs/solutions (be creative).
Understand the requirements thoroughly and come up the stategy (design) for the entire project.
Sketching with pen/pencil is a good way to come up with a unified design.
Don't stuck at some parts of the project: perform the team works in parallel.
Other tips on working in groups
Your code should run on all modern browsers/simulator and the VR head set of your choice.
Make sure your code is well commented (this is a good practice since you will work in a team). The instructor may inspect your source code.
It is easier to get your VR working but harder to get working well. Be sure to think carefully with your design decisions and to test them on the actual hardware regularly.
Project report on Github (readme file):
See example here: Simon's Project 1 report
Create a 3-minute video showing the use of your application with your voice over. That video should appear on the top of your github readme file.
The video can be used as a backup during your presentation just in case of something go wrong.
Add a link to your web-based application (right after the video). You can host it on your github or your ttu personal page.
Clearly explain the duties of each student in your group (if you work as a group).
Describe your application by screenshots (with meaningful captions) and text. Make sure you have the list and screenshots of models.
Links to all the source code and any assets (models, textures, sounds). Make sure you source code is well-commented.
The presentation is 6 minutes per group (everyone needs to present). It is 5-minute talk and 1 minute for questions. You can present directly on your report and demo.
Make sure that you are ready to talk right after the person/group in front of you is done.
Show a live demo of your work: Show the basic functionality and emphasize why your VR is different. You should include screenshots in your report as well.
Make sure your demo/app is self-contained: No hidden keyboard/mouse control, no hidden functionality (for example, users might not know that they have to click on the Angry bird to play the sound). In case you have these hidden controls, you need to make them available in the GUI:
Use highlighting principles (such as blinking) in my lecture 4.
A help menu is useful for uses of keyboard/mouse and it can work as a quick manual.
Please practice your talk.
Course Evaluation Link: Evaluate
© Last revised: May 6, 2018