Projects
Teams
- 3D Fractals – Tanel Marran, Mattias Aksli, Robert Joonas
- Island Rendering – Bohdan Romashchenko, Joonas Praks, Mehis Taevere
- Animated Weapons – Allan Alikas, Jaanus Arukask, Siim Anderson
- Heightmap Landscape Generation – Martin Munck, Kristina Kevel, Rauno Jaaska
- Road Crossing Simulator – Rytis Valiukas, Frederik Raud, Remi Sebastian Kits
- ESTCube-2 Visualization – Magnus Karlson, Adrian Kirikal, Hei Chun Shum
- 3D Interactive House – Markel Azpeitia Loiti, Aitor Zubillaga Unsain, Yaiza Rubio Chavida
- RPG with Procedural Generation – Henri Suokas, Anett-Kristin Palmar, Bogdan Mihhailjuk
- Brain Data Visualization – Fedor Stomakhin, Siim Parring, Hain Zuppur (sprv. Ilya Kuzovkin)
- CGVR VR Demo – Jelizaveta Kunetsova, Hugo Coutier (sprv. Madis Vasser)
- VR Live Racing for RC Cars – Mait Lättekivi (sprv. Rainer Paat)
- Blank page
You must be a student in this course to see the projects spreadsheet.
Rules
- The project has to be executed in groups of 2-3 people.
- The project provides up to 30 points. You lose points by missing deadlines.
- The project consists of
- A piece of (working) software,
- A short written report (in your project page) describing the topic, the tools and methods used, mentioning the main complications and contributions. Should include a 1-2 min video of the result.
- Discussion about the project with one of the instructors
- A short (10 min) demo presentation.
- The project code must be hosted openly in a repository (I strongly suggest Github or GitLab) and preferably as open source. Meaningful contribution from all team members needs to show in the repo log.
- Exceptions to the rules are possible via personal requests. E.g. if you really think you need 4 people on the team, come and explain why, presenting your plan and preliminary task list.
Deadlines
All deadlines are hard. You may miss them, but you pay with points.
- Oct 18. Registering your idea. Write down [You must be a student in this course to see the link] your initial project idea for others to join. Do not miss this deadline, otherwise you risk not getting to a valid team by Oct 25.
- Oct 25. Forming the team. By this date (23:59 the latest) the team must be formed and project topic chosen. The corresponding information should be [You must be a student in this course to see the link].
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Nov 15. Initial progress. By this date the team should be able to demonstrate something beyond "Hello World", that can be compiled / launched. At this stage all your team-members must have started working together and produced a proof of concept result. At least 500 LOC (or equivalent). Code + compilation / launching guide should be available in the repository. Also your project's course page should have a link to the repository and a brief illustrated description of your project.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Dec 13. Coach Meeting. During the first half of December the entire team needs to meet with one of the instructors and discuss the issues they are having. Instructors will assume to see a 2/3 completed project from you then in order to have a meaningful discussion. Team-specific meetings will be scheduled in November.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Jan 3. Final release. By this date the team should submit (make available from the project page) the final release of the project. The release should include a short (1-2 page) report, that can be written on the project page, in the git's readme.md file, or made otherwise easily accessible. Also add a small video, which demonstrates your achieved result.
- Every day missed past the deadline: -2 pts.
- Jan 7 (12:00 - 20:00). Project demonstration. All members of the team must be present during the presentation.
- Not presenting a demo results in the overall score of 0 pts for the project.
- In Zoom (log in to see link)
- Team leads pick a section of the day to present in.
- Vote for the best projects here.
Potential topics
You are free to choose the topic on your own, as long as the resulting project is exciting enough for you, and requires at least 1 full working week (around 40 hrs) per person to complete. Naturally, it should be (at least in part) related to computer graphics. We will discuss your registered ideas in the recap lecture.
Possible ideas
- A game with a sufficient graphical component.
- A created 3D scene, environment, objects (CGI, art).
- An interactive data visualization or simulation.
- Some interesting game mechanic or procedural generation.
- Here are some lists for ideas:
- Three.js - Showcase of things done with Three.js,
- Paul's Projects - Graphics algorithms implemented,
- CG Meetup Gallery - Beautiful short renders,
- The Graphics Codex Projects - More graphics algorithms implemented,
- Spore Prototypes - Procedural generation before there was Spore,
- Chrome Experiments - Cool stuff done on the web.
- Join an ongoing project from the APT Game Generator group: projects.
- Here are the projects from the last times: Fall 2019; Fall 2018; Fall 2017; Fall 2016; Fall 2015; Spring 2015; Fall 2013.
- Notable student projects