Final Artifact

Artifact winners

Great job this quarter everone! Click here for the final artifacts and winners.

Due dates (all by 11pm)

Team signup: May 13 Proposal: May 18 (signed off May 22) Checkpoint: May 25 Project: June 5

1. Artifact winners
2. Overview
3. Team
4. Project Proposal
5. Checkpoint
6. Project Report and Presentation
7. Grading
8. Turnin

Overview

In this project, you’ll work with a team of other students to create an Artifact – a computer graphics program that does something exciting. It will give you experience building something real in Unity.

Your artifact can be any of the following:

• An interactive game using 3D computer graphics.
• A short film, at least 2 minutes in length.
• An educational cartoon, teaching the concept of your choice. We’d recommend following the guidelines here. It does not have to be limited to computer graphics – e.g., you could explain cryptocurrency, protein folding, black holes, or any other tricky topic!
• A visualization – human anatomy, space, weather, architecture, etc.
• A virtual reality experience. We can lend you VR headsets if you need them.
• Something else that you propose which satisfies the requirements.

The requirements are as follows:

1. You must use Unity (or another 3D graphics package, with permission of instructional staff) in the production of at least part of your artifact.
2. Your artifact should include 3D content
3. You’ll work in a team of (typically) four students.
4. You must include some kind of animation (motion of 3D objects).
5. Difficulty should be appropriate for a two week, 4-person team project. I.e., you should personally spend about as much time as you would for modeler/tracer/simulator.
6. Your project should be interesting/entertaining, and innovative. While it’s fine to be inspired by an existing 3D experience, your version should not be a verbatim copy. E.g., you can’t turn in the result of an existing Unity tutorial :-)
7. Your code should be accessible by the TA team: either turned in on Canvas or linked to e.g., via a public github repo.

Feel free to use ChatGPT to help you come up with ideas (e.g., “Ideas for Unity Games”). You are welcome to incorporate assets (models, materials, textures, etc.) from online resources like the Unity Asset Store, TurboSquid, and others. Many assets are free or inexpensive. If you would like to purchase a more expensive asset, include it in your proposal – we have a small budget and could help cover a few assets for teams.

Team

Your first step is to form a team. We will assign teams for all students who are not already assigned to a 4-person team. Each team will be assigned a TA mentor

Project Proposal

Next, you must submit a project proposal (one per team). Your proposal will be due on Canvas, and require answering a series of questions, asking about your topic, development plan, and split of work among team members. You will need to define a one-week checkpoint that details what you will deliver at the end of week 1. You will be graded on the completion of the checkpoint, against your own checkpoint specifications.

Checkpoint

The checkpoint itself will be a live meeting with your TA mentor, where they will evaluate your completion of the checkpoint, based on what you described in your project proposal.

Project Report and Presentation

Each team will write a report following this template. Each team will create a maximum 5-minute video showcasing your artifact and upload the video to youtube. Projects will also be presented in the class finals slot – you’ll have about 5 minutes to cover your project. By default we will show your 5-minute video but you can also do a live demo - just let us know in advance. During the final slot and everyone will vote on their favorites, with prizes to the top three! Each team will fill out their part of the following slide deck which we will show during the final slot.

Grading

Projects will be graded based on the following rubric:

• Proposal 10%
• Checkpoint 10%
• Satisfies requirements 70% (based on final project report, video and presentation)
• Final presentation 10%

Turnin

• Fill out team signup form (May 13)
• Submit proposal on Canvas (May 18)
• Meet with TA for checkpoint
• Submit final report using this template, your video and your code on Canvas (June 5). The video should be uploaded to YouTube and must be publicly accessible. Submit a link to the youtube video. Your code can be submitted in the form of a link to a public repo (or zipped up and uploaded to canvas).
• Present your group in-class during final slot (June 7th @ 16:30-18:20). By default we will show each group’s video, but you can also do a live demo, just let us know in advance. Fill in the following slide deck which we will show during the final slot.