Final Project Submission¶
Due date: 2024-12-15 23:59.
Your final project submission consists of two parts: a live presentation and the submission of your Unity build files. Please carefully review the instructions below for details on how to arrange your live presentation and submit your project files. Additionally, find the grading rubric we will use for your submissions below.
Live Presentations¶
We ask you to present your project live to us on days that will be announced to you later. Typically, these presentations will occur in the last week of the course, possibly during lab sessions, lectures, or both.
Please follow the link to set up the time for your final presentation here: SIGN UP PAGE.
Grading Rubric¶
The projects are graded mainly based on creativity, technical difficulty, and other "wow" factors. The maximum score for the project is 30% of the final grade: 3% for Part 1: Project First Scene, 2% for Part 2: Project Description, and, finally, 25% for this final Part 3 submission.
Name | Points | Description |
Issue 1 | 2 | Issue 1 implemented |
Issue 2 | 2 | Issue 2 implemented |
Issue 3 | 2 | Issue 3 implemented |
Issue 4 | 2 | Issue 4 implemented |
Completeness/usability | 2 | Did you get it working? Is it well polished, or only started working minutes before? Is it running at full frame rate, or are there glitches? |
Creativity | 2 | Did the project involve substantial creative effort, or did you simply throw some standard things together? |
Difficulty | 2 | Using middleware and other existing software, how much work was required for the team? How many obstacles had to be overcome to make everything work? |
Aesthetic/overall quality | 2 | Is this an aesthetically pleasing experience? Is this an enjoyable experience? |
Human factors | 2 | How well the principles of making a comfortable experience are followed. If some are ignored, then it must be explained why (the point of a virtual roller coaster may be discomfort), along with an explanation of the possible side effects of using your project. |
Instructions integrated into the experience | 2 | Ensure clear, visible instructions are embedded directly into your scenes so that future users can easily understand how to navigate and interact with your project. |
Working Unity build | 1 | Your project must be a fully functioning Unity build that can be run independently. If your experience can only be run from the Unity project itself, you will not receive these points. |
Code documentation | 1 | |
Live presentation | 3 | You present your project to us live, and your presentation clearly conveys your project functionality. |
Total | 25 |
Unity Build Files Submission¶
Check the content of the Rubric above to make sure that you have implemented everything we ask from you in this project.
Step 1: Create a Unity3D Package File¶
- Save your Unity scene in the Assets folder with a descriptive title.
- Using the editor, find the created scene in the Project menu
- Right click on the scene and select Export Package
- Export the file using default settings. Make sure that Include dependencies is enabled.
- This will create a
.unitypackage
file. We may use this during grading if your executable does not work, so make sure you also submit the data folder.
Step 2: Create a Standalone Build¶
- Save the project to
C:\Users\<your netid>\<project name>
temporarily, rather than the EWSU:
drive. Local storage is faster when building. - Go to Edit → Project Settings → Player. Make sure the Virtual Reality Supported box under XR Settings is checked.
- Go to File → Build Settings.
- Open the scene with your work for the MP.
- Click Add Open Scenes. You must have saved the scene to the assets folder for this to work.
- Click Build.
- This will create an executable (
.exe
) for running the build, a folder containing your scene data, aMono
folder, andUnityPlayer.dll
.
Step 3: Copy the Input Manager File¶
- Shut down your project.
- In your project folder, navigate to the
ProjectSettings
subfolder. - Find the
InputManager.asset
file, and copy it to your submission folder. This will allow us to replicate any new gamepad buttons or joysticks you mapped.
Step 4: Zip the Files¶
- Create a
.zip
file containing the following items: - The
.unitypackage
created in Step 1. - The
.exe
,.dll
,Mono
, and DATA FOLDER created in Step 2. - The
InputManager.asset
file found in Step 3. - A
README.txt
file containing any special instructions or notes you think are relevant for evaluating your assignment. - Make sure the executable in your submission folder runs correctly on the Rift before submitting.
Give feedback on this content
Comments about this material