For the Documentation I did the following:

• I maintained the wiki and set up the current layout to be user friendly for customers

For the Documentation (see ProjectThreeDocs) I did the following:

• Maintained the wiki and set up the current layout to be user friendly for customers

• I wrote the final presentation
• I also wrote up the UML diagrams
• I wrote a decent chunk of the final report with Matt

• Wrote the final presentation
• Also wrote up the UML diagrams
• Wrote the section on design patterns in the final report
• Wrote the FAQ in the ProjectThreeDocs section
• Put together the weekly work breakdown structures so that everyone would be clear what it was that needed to be done

For the Beta Release and Tweaking I did the following:

For the Beta Release and Tweaking (see PrototypeCountry) I did the following:

• I wrote a decent chunk of the final report with Matt

• Tweaked the particle system to make it as CPU non-intensive as possible

• Tweaked the particle system to make it as CPU non-intensive as possible, while billboarded

• 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 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

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
• Played around with the animations to make them as cool as possible
• Set up game ending scenarios and implemented code

• Put together a framework for multiple "views"

• Put together a framework for multiple "views" using a bridge

• Helped Matt architect the collision code and debug memory leaks

• Helped Matt architect the collision code and debug memory leaks, also helped simplify the algorithm (simple is better)

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"
• Instrumented the framework for good controls and helped Mark flesh out the code
• Helped Matt architect the collision code and debug memory leaks

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

• Enabled "dynamic" triangles so that we can move people around

• Enabled "dynamic" boxes/cylinders so that we can move people around

Project Three

For the first prototype (see PrototypeCountry)

• Set up some of the modelling rotation, "sense of direction" and animation
• Enabled "dynamic" triangles 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

• • Mapped out the coordinates for the hole

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

• Added in sound and several sounds that play through out the course
• Added in help menu for user to toggle while playing

-- AaronArvey - 27 Sep 2004

-- AaronArvey - 21 Sep 2004

-- AaronArvey - 15 Sep 2004

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
• Power bar
• Particle system and explosions

• • Style

• • Code style document (in progress)

• • Changed ball drawing code to use quadrics to make it cooler

• • Changed ball drawing code to use quadrics and wire frame to make it cooler

• • 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

• • Collision responses

• Integration of other collisions into one function.

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

Set up lots of stuff.... put it down here...

For the third prototype I did the following:

• Documents
  • Style
• Code
  • Changed ball drawing code to use quadrics to make it cooler
  • Added in camera class

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 function.

Project Two

Set up lots of stuff.... put it down here...

Project One

For the documentation, I did the following:

• RiskAnalysis
• ProjectModels
• ExecutableRecord
• TestPlan
• ProjectPresentations

-- AaronArvey - 27 Sep 2004

• losing conditions
• losing sequence
• intro text description of game

• Changing cursor code (picture is Matt's)

• changing cursor code (picture is Matt's)

• fire spreading

• making fires come out at increasing rates

For the final I added:

• mapping fires to windows
• fire spreading

-- AaronArvey - 21 Sep 2004

• Changing cursor code (picture is Matt's)

For the final I added:

• mapping fires to windows
• fire spreading

-- AaronArvey - 21 Sep 2004

For the final I added:

• mapping fires to windows
• fire spreading

-- AaronArvey - 21 Sep 2004

Set up some stuff on wiki and wrote some code today.

-- AaronArvey - 15 Sep 2004

• damage to player when too much fire is out there (total hack!)
• damage fire (lower fire health) and change fire sprite

• damage to player when too much fire is out there
• damage to fire (lower fire health) and change fire sprite
• drew fire sprite bitmaps

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 (total hack!)
• damage fire (lower fire health) and change fire sprite

-- AaronArvey - 15 Sep 2004

%META:TOPICINFO{author="AaronArvey" date="1095238850" format="1.0" version="1.1"}% %META:TOPICPARENT{name="ProjectPersonnel"}% Set up some stuff on wiki and wrote some code today.

-- AaronArvey - 15 Sep 2004