10% for Game design and implementation (final submission).
5% for in-class presentation and Github report.
Group formation Submission are due at 11:59pm Friday, Oct 16
Project 2 mid-review is on Monday, Nov 2 (Designing, sketching, and reporting any group issues). You need to submit the project title, abstract, and link to your initial design are due
at 11:59 pm on Sunday, Nov 1: Google form link.
Project screenshot (a 1200 x 800 gif image of your work which should be
named p2.<your_last_name1><your_last_name2>.gif, demo link, Youtube video link, and github link are due
at 11:59 pm on Sunday, Nov 29: Google form link. If you have any problems, please email TA at ngan.v.t.nguyen@ttu.edu.
Each student needs to send a peer evaluation for other teammates by Tuesday, Dec 1 to the TA: ngan.v.t.nguyen@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).
Project 2 is based on the requriements of CHI 2021 Student Game Competition. You should select to work on one of the 2 following tracks:
Games submitted to this category should be games that push the boundaries of current games and game interface practice. Example areas include the use of gesture, multi-touch, multi-screen or haptics; voice input; use of sensors such as breathing or heart rate; augmented reality games, mixed reality games, novel use of game AI and machine learning techniques, or explore novel, thought-provoking forms of interaction.
(Starting at 15:00)
This category attends to the expanding boundaries of play and game design with the emergence of independent games, art games, and political games as well as gamified/playbourised systems that explore the role of play in non-gaming settings. For example, games now play an increasingly important role in areas like education, healthcare, safety, urban planning, sustainability, and other economic, cultural, and societal sectors. Games submitted to this category should draw on these expanding boundaries of game design to create innovative gameplay for non-gaming settings, and critically reflect on challenges.
MPORTANT NOTE: It is not mandatory to have a completely playable game in order to participate in this competition. We are also encouraging innovative ideas, speculative/provocative game designs and early prototypes of the game if authors could demonstrate why their game/idea is innovative and how it could advance the current state-of-the-art. Students submitting speculative and early prototypes should, however, explain the rationale behind their game design with clear positioning within the literature, reasons for not presenting a complete game (e.g., technology is not yet there, need for massive resources or investment), research aims, and envisioned impact in the Extended Abstract document. Speculative submissions have to be supplemented with a Wizard of Oz demonstration of gameplay.
Project 2 is a group (of 3 or 4 students) project, exceptions are allowed with reasonable justification.
Students select their group member and the topic (from the list above). If you can't, the professor will assign your
group. Team formation is due at 11:59pm Friday, Oct 16.
Project evaluation:
Your project will be evaluated on the following dimensions:
Innovative and Transformative (20%)
Educating (10%). Science behind your work such as Water vaporization or social characteristics when proposing a rescue solution
Do I need to test on the hardware?
For this semester, I asked this question. The Dean said "What is the meaning of education if you are not safe."
Do I need to buy the hardware?
You don't have to.
What do we do if one of our teammates isn't doing any work? How does that work? Would we just give them low scores on our feedback and that's it?
People in the same team will receive different scores based on their contributions.
Do we need to make our own assets and songs that we use for project 2?
You can but you don't have to. You can use the assets/music tracks that you like for the game as long as we don't have any license issues.
I also require you to credit any songs or assets that you use for this project in your final report.
You should be focusing on the game's mechanics and Music will add flavors to it.
Is November 2 a mid-project update or is it when we get approval for our project?
Both. You will present
Can we submit a demonstration of our game using mouse and keyboard control? Will any points be docked for using mouse and keyboard?
Yes, you can demonstrate the game using mouse and keyboard control. No point will be subtracted.
Advice:
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.
We will conduct P2 midterm updates for this project (Monday Nov 2). Don't wait until the
last week to implement your project. Especially, don't update your codes in the last minutes.
Don't stuck at some parts of the project: perform the team works in parallel.
This VR project is written Unity, but if you prefer different technologies, you need to justify.
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.
Project report on Github (readme file) Or Unity Teams:
Create a 3- to 5-minute video (mandatory) 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.
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.
In-class presentation:
The presentation is 6 minutes per group (everyone needs to present). It is 3- to 5-minute talk/video and the rest of time for
questions.
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.
