Orange Lab D Week of Mar 21 - 26th Lab Update

Accomplished This Week:

Table D1:

• Game engine is in development.
• Researching and implementing GED Content into game.

Table D2:

• Basic game engine implemented.
• Text output, scrolling, collision, and user movement implemented into game engine.

Table D3:

• Engine is completely implemented and functional.
• Tilesets completely created and implemented into the game.
• Setting up combat and other conflict oriented management.
• Implementing quests into the game.

Table D9:

• Spriting for ingame characters in progress.
• Engine is beginning to be developed.
• In game GED content codex is being compiled.

Table D11:

• Group is researching additional GED content to implement into game.
• Game engine is developed and functional.

Table D12:

• Storyline and design confirmed.
• Engine conceptualized.
• Source code collected and examples collected as to how to create the game engine.

Monitoring and Control:

To Be Accomplished Next Week:

Table D1:

• Develop a basic game structure that is semi-playable.
• Have all GED (or most) ready for implementation into game.

Table D2:

• Further development of game engine (more playable).
• Scrolling engine implemented into game.

Table D3:

• Have a finished prototype of the game playable.
• Working towards play testing the game.
• Attempt to finalize in game content.

Table D9:

• Engine finished and one level completed and playable.
• Entire in game GED codex completely finished.

Table D11:

• Implement sprites and tilesets into game engine.
• Have many level developed to demonstrate modularity of game design structure.

Table D12:

• All spriting done.
• Engine implemented (one level with a boss)
• Implement most GED content into working prototype.

Further Notes:

Groups are learning their corresponding game development programs well. Little to no guidance has been necessary and many are making surprising headway.

Many are unsure as to how to tackle the final report until a prototype of their respective engines are developed.

Creating in game content seems to be the largest battle for most groups. Practice implementing and drawing in game sprites and world content will be needed.

Status Report for Orange B Lab - Week of March 22 - March 27

Accomplished This Week:

Team B1:

• Complete functionality report.
• Began work on platform game.

Team B2:

• Completed functionally report.
• Began to design and construct the mini-game.

Team B3:

• Completed functionality report.
• Finalised mini-game design plan.
• Played around with Game Maker program.
• Started to make the mini-game.

Team B5:

• Completed functionality report.
• Finalised mini-game idea.
• Learned about Game Maker software.
• Made prototype of first mini-game.
• Group member went to the Mustard Seed for a tour.

Team B6:

• Functional Requirement report was completed.
• Familiarization with Game Maker 5.

Team B8:

• Sprites and game set was chosen.
• First mini0game 1/4 complete
• Second mini-game idea developed.
• Design Proposal report completed.

Monitoring and Control:

To Be Accomplished Next Week:

Team B1:

• Build multiple platform levels.
• Refining platforms.
• Prepare for integration of mini-games.

Team B2:

• Continue developing knowledge on Game Maker Program.
• Continue to create the mini-game.

Team B3:

• Continuation of making the game.
• Start working on game manual
• Plan the poster

Team B5:

• Test out and improve the mini-game prototype.

Team B6:

• Decide on game style
• Decide on specific theme
• Decide on graphics
• Start programming

Team B8:

• Finish first mini-game.
• Get started on second mini-game.
• Obtain/create game sprites.

Additional Information:

The final report cannot be started to be worked on until some idea of what the program will look like exists, therefore some teams may experience a small delay.

Orange Lab C Status Report for the week of March 26th

Orange Lab C Blog Status Report for the week of March 26^th

Lab :

Accomplished:

· Set some basic specifications for programming

· Went over layout of program

· Discussed expectations for how the program should work

To be Accomplished:

· Produce basic program

· Develop and integrate programs

· Decide on which game platform to use

Additional Information:

· Need to work on communication and organization between the lab groups

· While designing the program the lab needs to keep in mind feasibility

C1:

Accomplished:

· Functionality Report written

· Platforms examined

· Getting familiarized with Blender application

· Downloaded Construct to use as a platform if Blender doesn't work out

· Determined how to split up work between ourselves and C9

· Created specific work for weeks work

To be Accomplished:

· Get the base for the program written

· Receive work from research teams and figure out what and how to integrate it into the game

· Make sure that we are getting more than just a list of questions from the research teams

C2:

Accomplished:

l Assigned roles and to-do lists for the Functional Requirements and Design Proposal

l Finished research for the report

l Compiled everyone's work into an 11 page report to be handed in Thursday March. 25, 2010

l Learned what they want for the testing component

To Be Accomplished:

• Start on questions to give to the game design group
• There isn't a set amount of questions, but there needs to be enough to get the point across (>20)
• Make diagrams and pictures to accompany questions in order to keep the game more interesting
• Make settings for each question (ex. the setting in the game, building floors, etc.)
• Compile these questions, settings, and ideas in a well organized manner and give them to the programming groups as soon as possible so that they can begin.

Additional Information:

• Theme is very important and needs to be focused on in developing each of the questions.
• Focus also needs to directly on not boring the users of the game.

C5:

Accomplished:

· Finished the functionality report and design proposal

· Brainstormed ideas for the game

· Found twelve different facial expressions for which we can test on

To be Accomplished:

· Help programming group with anything they need

· Write down questions and answers specifically for our task (conversation and facial expressions)

C6:

Accomplished:

· established general design for educational program

· examined engineering requirements and how to implement them into program

· began grating question bank for program

To be Accomplished:

· meet with programming team and relay what we want accomplished

· continue creating question bank

· communicate with other teams so that our programs do not overlap too much

Additional Information:

· call group meeting to talk about starting programming as soon as possible

C8:

Accomplished:

· Came up with the artificial hand/ circuit prototype

· Thought of ways to incorporate handshakes into the game

· Split up the functionality report and had finished it/handed it in

To be Accomplished:

· Hopefully finish the artificial hand prototype

o Buy and construct materials

· Know exactly what kind of software/program we will be dealing with

· Incorporate out ideas into the program

C9:

Accomplished:

· determined the framework of the project, main project goals, and integration with other lab groups.

· narrowed the potential development platforms down to two choices; construct or blender.

· finished the functionality report prerequisite.

To be Accomplished:

· deciding on which development platform to use (by Monday).

· deciding on precise details of game framework and graphics (Monday).

· Completing the main model or image (by Wednesday).

· Completing the first interrupt sequence (by Thursday).

· Completing a basic working prototype by Thursday's lab.

· Receiving input and suggestions from the lab on Thursday.