Projects
Project pages will be available here later.
Rules
- The project has to be executed in groups of 2-3 people.
- The project gives you 30 points. You lose these points by missing deadlines.
- The project consists of:
- A piece of (working) software (a Windows build or a live website), or a rendered video.
- A short written report (in your project page) describing the topic, the tools, and methods used, mentioning the main complications and contributions. Including a 1-2 min video of the result.
- Discussions about the project with one of the instructors (your coach).
- A short (10 min) demo presentation.
- The project code must be hosted openly in a repository (we recommend 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.
- To help you manage your project, feel free to use a project management tool of your choice. We recommend Codecks!
Deadlines
All deadlines are hard. You may miss them, but you pay with points.
- Oct 13. Registering Your Idea. Write down in CGLearn your initial project idea for others to join. Do not miss this deadline, otherwise you risk not getting to a valid team by Oct 21.
- Oct 20. Forming the Team. By this date, the team must be formed, and the project topic chosen in CGLearn.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Nov 10. Coach Meeting #1. By this date, the team should have had their first coach meeting. Before the meeting, the team should have met themselves and put together a solid idea of what the team wants to achieve together. This idea (incl, results of the ideation and existing examples) should be described, illustrated, and well-formatted on the project's courses page. During the coach meeting, the team, by using their courses page, explains the idea and each team member's responsibilities to the coach, who then guides the team toward success. It is the team's responsibility to contact the coach and set up the meeting in a timely way.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- Dec 08. Coach Meeting #2. By this date, the team should have had their second coach meeting. For that meeting, the team should have achieved a 2/3rds working demo, at least 1000 LOCs of equivalent progress, made a Windows demo build (or set up a live webpage), and described their project in their courses page in a clear, illustrated, and well-formatted way. The courses page should have a link to the project's repository, where each team member's contribution is clearly visible from the commit log. The coach will assist in and guide the finalization of the demo into a finished project. It is the team's responsibility to contact the coach and set up the meeting in a timely way.
- Missing the deadline by up to 1 day: -3 pts.
- 1-7 days: -6 pts.
- 8+ days: -9 pts.
- TBA. Final Release. By this date, the team should submit (make available from the project page) the project's final release. The release should include a short, illustrated, and well-formatted report written on your project page. The page must include links to the Windows build (or live webpage), repository, and there must also be a small video that demonstrates your achieved result.
- Every day missed past the deadline: -2 pts.
- TBA. Project Demonstration. All members of the team must be present during the presentation.
- Not presenting your project results in the total project score of 0 pts for you.
Insights
By the end, your project page should be a single, illustrated, and well-formatted final report of the project. During the work, it is a living document that has the most up-to-date information necessary for your team and the coach. It is a good idea to assign this responsibility to one of your team members. Do not forget to update the metadata of your project page (the fbgpmeta tag).
Solo projects can be done, but they can earn up to 21 points maximum (losing 9 points from the first deadline). Team projects may become de facto solo projects during the course. In such a case, they do not lose the first deadline points.
You can only lose points for missing deadlines, not for the quality or size of your project. We understand that everyone has different skill levels. If you work on something suitable for your team's competence, do it consistently, and keep up with the deadlines, these points will be the easiest in this course.
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, animation (CGI, art).
- An interactive data visualization or simulation.
- Some interesting procedural generation approach.
- 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,
- Spore Prototypes - Procedural generation before there was Spore,
- Chrome Experiments - Cool stuff done on the web.
- Notable student projects (pick CG from the filter)