2. Dakota Humphries (Project Lead) Thomas Impellitteri (Tech Lead) Daryl McGhee II (Design Lead) Keith Rosier (Asset Lead)

3. Supernova Blindside Turn Based Strategy Game 3 Grids to Strategize and Attack Complete Objectives Capture Planets for Money Customize Ships for Added Strategy Travel through space and progress storyline

4. Gameplay Scout FighterGunship BattleshipCruiser

5. Gameplay (cont’d) Buy ships from shop Objectives are given at the level start Do what you must to win – Destroy planets – Destroy stars – Capture planets for currency – Upgrade ships using currency

6. Dakota Humphries Project Lead Scheduling FMOD Sound – 3D Sound Collision Combat System

7. 3D Sound What is 3D Sound? – Emitter vs Listener – 2D vs 3D Sound Basic 3D sound update

8. 2D vs 3D Sound 2D Sound:

9. 2D vs 3D Sound 3D Sound:

10. 3D Sound Updating Emitters & Listener – 3 Easy steps for updating Update the position Calculate the velocity Send the information to FMOD Current Position Old Position Time

11. 3D Sound Updating Emitters & Listener – 3 Easy steps for updating Update the position Calculate the velocity Send the information to FMOD

12. Thomas Impellitteri Technology Lead AI – Path-finding – Decision Trees Integration Picking Lua Scripting

13. Path-finding – Start to Goal – Simple Distance Checks

14. Path finding, How its done Alone, lost in goals

15. Decision Trees Decision Tree – Brain of the Operation – Decides all options for path-finding – Finds who to shoot

16. Decision Tree, helping hand AI finds its way

17. How its done Nodes with function pointers

18. Daryl McGhee Design Lead Menu System Shop and Upgrade System Camera Object Creation and Management

19. Composed of Two Parts: – Object Factory Creates all objects used in the game – Object Manager Arranges objects deletes them properly

20. Object Factory

21. Object Manager

22. After objects are no longer needed: – Back in the factory for later use – They are deleted in groups

23. Keith Rosier Asset Lead Rendering Effects System Render Engine Texture Manager

24. Death of a Star Have a defined start and end Figure out the major steps that will get you from here to there Figure out what tools (Art, API, Systems) you will need to generate the desired effects

25. Death of a Star Start with a model A “model” is a collection of vertices These vertices form triangles Triangles form the model’s surface

26. Death of a Star Texture the model (in this case a star) Texturing wraps a “skin” around a model to give the appearance of complexity

27. Death of a Star Add particle effects for extra detail Particles first implemented in Star Trek II: The Wrath of Khan Used to generate visuals for things without a defined surface (smoke, water, fire)

28. Death of a Star Change particles and textures to generate a dying star

29. Death of a Star Employ the use of “quads” for blast effects Quads are two triangles used to generate a square

30. Death of a Star Replace the old model with a new one Add more quads and particles to generate new effects Stretch and rotate quads to achieve the desired visual

31. Risks Risk:Affected Resource:PCRF Because we were behind for so long with tech and gameplay a lot of our Upgrade and Weapons system will need to be cut in order to be get a finished game. Team Response or avoidance: Mitigation 1. Continuously implement and test each weapon and corresponding upgrade. Starting with the most fundamental. Backup Plan 1. If a weapon and its corresponding upgrade is not fully implemented and tested by Beta, then it is cut from the game.

32. Risks (cont’d) Risk:Affected Resource:PCRF Billboarded particles are not working and the problem is that the solution is unknown. If billboarded quads are not working with our game then our best effects cannot be put into the game. Keith, Particle Engine Response or avoidance: Mitigation 1. Seek help from Wendy the Direct X teacher. Backup Plan 1. If billboarded particles are not implemented by a week before Beta then hard code the rotations.

33. Risks (cont’d) Risk:Affected Resource:PCRF We are loading meshes and textures multiple times and they are using unnecessary memory. This can cause major slowdown with the game due to many new and delete calls. Keith, Rendering Response or avoidance: Mitigation 1.Create a manager to handle the meshes and textures so that they can be reused after they are done. Backup Plan 1.If the manager is not done a week before Beta then create a hard-coded class that creates instances of the models.

34. Risks (cont’d) Risk:Affected Resource:PCRF We currently do not have a particle editor to create particle effects. This will mean that we don’t have a way to create effects besides hard coding values which will take up time and may prevent effects from getting put into the game. Keith, Particle Engine Response or avoidance: Mitigation 1.Create an editor to create effects with. Backup Plan 1.If the manager is not done a week before Beta then create a Lua script that handles the particle effects.

35. What Was Learned How to deal with losing a team member Learning something new during a project is much more time consuming and adds to resources Gameplay is more important than technology, when tech is done, gameplay should be right after. Modularity is much more important than it seems

36. Questions and Answers