Project Three

For the Documentation I did the following:

• I maintained the wiki and set up the current layout to be user friendly for customers
• The wiki also has the following process elements:
  • Milestones
  • Work Breakdown for each prototype
  • Risk Analysis
• I wrote the final presentation
• I also wrote up the UML diagrams
• I wrote a decent chunk of the final report with Matt

For the Beta Release and Tweaking I did the following:

• Put together the theme song (background wave)
• Found all the sounds that homer and lara make
• Tweaked the particle system to make it as CPU non-intensive as possible, while billboarded
• Played around with the animations to make them as cool as possible
• Set up game ending scenarios and implemented code
• Created a few nice textures for graphics
• Met with Matt one night then Mark the next several times because schedules were drawn thin

For the Fourth prototype and Alpha release (see PrototypeCountry)

• Put together the heads-up display (number of lives left, number of balls left, target, etc)
• Put together a framework for multiple "views" using a bridge
• Instrumented the framework for good controls and helped Mark flesh out the code
• Helped Matt architect the collision code and debug memory leaks, also helped simplify the algorithm (simple is better)

For the third prototype (see PrototypeCountry)

• Got some cool texturing to work
• Helped Mark flesh out some of the AI code

For the second prototype (see PrototypeCountry)

• Wrote a frameword for the AI with inheritance, bridging and good overall design
• Created a team framework for adding players to opposing teams
• Enabled players to throw balls

For the first prototype (see PrototypeCountry)

• Set up some of the modelling rotation, "sense of direction" and animation
• Enabled "dynamic" boxes/cylinders so that we can move people around

For the concept I did the following:

• Performed thorough risk/feasability analysis
• Layout implementation steps so there are concrete debugging/prototyping places

Project Two

For the code clean up and documentation I did the following:

• I went through and thouroughly cleaned up the world idle function so that it would be intuitive and easy to read
• I commented every header file
• I removed old code from all source files
• I posted the risk analysis and other planning documents on the wiki

For the golf game I did the following:

• Terrain
  • I loaded in a height map
  • I also did a translation to triangles for collision detection
  • Mapped out the coordinates for the hole
• Power bar
• Particle system and explosions
• Added in sound and several sounds that play through out the course
• Added in help menu for user to toggle while playing

For the third prototype I did the following:

• Documents
  • Code style document (in progress)
• Code
  • Changed ball drawing code to use quadrics and wire frame to make it cooler
  • Added in camera class
  • Collision responses
  • Concept of iterative collision response versus averaged - When and how to do this
    • Wrote a sorting function for collisions in order to determine when
    • Edited the main idle loop to iterate over a collision list while staying with with the same ball.
  • Designed a test or two (Matt did most of the work here)
  • Worked on collision detection (Worked with Mark on this)
  • Extended the parser to handle cubes, quads, and other shapes

For the second prototype I did the following:

• Diagrams
  • Gantt
  • Work Breakdown
  • PERT CHART
• Code
  • CSV (excel ouput) parser for balls and triangles

For the first prototype I did the following:

• Face collision
• Integration of other collisions into one modular function.
• Set up wiki site

Project One

For the documentation, I did the following:

• RiskAnalysis
• ProjectModels
• ExecutableRecord
• TestPlan
• ProjectPresentations

For the final I added:

• mapping fires to windows
• making fires come out at increasing rates
• losing conditions
• losing sequence
• intro text description of game

For the prototype I've done the following:

• score and losing conditions (no winning conditions yet)
• damage to player when too much fire is out there
• damage to fire (lower fire health) and change fire sprite
• drew fire sprite bitmaps
• changing cursor code (picture is Matt's)