Game Project IMGD 4000 Due Dates and Presentation Guidelines
Learn about the due dates and important milestones for the Game Project IMGD 4000, including forming teams, website treatment, and technical aspects. Get insights on the Alpha release requirements, presentation guidelines, and the importance of practicing presentations. Discover do's and don'ts for a successful presentation and tips for conveying feedback to teams.
Uploaded on | 0 Views
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Game Project IMGD 4000 Due Dates: Form Teams Treatment Website Tech milestone Alpha Beta Final Presentation April 17
Alpha Release Compile cleanly, runnable All required features implemented Physics, Autonomous, force-based steering, Pathfinding, State- based AI May not be working entirely correctly, but code is observable and demonstrable in game Optional tech features may not yet be implemented Game code tested to eliminate critical gameplay flaws Minor glitches/bugs present May have separate levels for separate parts (e.g., some illustrating weapons, other bad guys or boss) Not yet balanced, nor levels designed Placeholder art assets ok (e.g., simple cube)
Presentation (1 of 2) Present game in class Consider this a practice for your final presentation Grading will be light , but with feedback for final presentation (which will not) Alpha presentation is team of 2, final is team of 4 so convey feedback to team! Designed to show off your game Show off your tech (and art for final)
Presentation (2 of 2) Opening Introduce team High concept of game Summary of major features core ideas Can be done with slide(s) (but not too many!) Most time spent demonstrating game! (show, don t tell) Highlight technical aspects as show them Describe details of implementation where needed Can be done live or with a video Bring laptop / test on podium computer ahead of time! Embarrassing things can happen when you don't try out! Both team members should talk Arrange in advance who says what Total time 5 minutes Plan accordingly Practice! Many times content, timing and transitions down
Presentation Notes Why present? You will give many presentations in your career Job interviews, Game pitches, conference/workshop talks Giving a presentation is a skill Like software design or coding You have the training , just need to practice! Embrace the challenge, learn to like it Or, at least, have the confidence you can do a good job
Dos and Donts Do Project your voice Speak with confidence Make eye contact with audience Clearly describe tech Rehearse who says what Have both team mates speak Have clear visuals that show what you want audience to see Don t Mumble Have an "oops" moment Apologize for any part of your presentation/game Use foul language Assume audience understands tech (or game!) Leave out part of presentation (e.g., introduction) Talk too much without visuals
Turn In Build windows executable Put on Web where we can download Zip up source code *.cpp, *.h Screen shots of significant blueprints README.txt file with URL to download executable Directions on how to play the game For each technical element A brief description of its design and functionality
