T2G Update : Portfolio Project 1

The Portfolio Projects are split in to various sections. I have been working on Portfolio Project 1 for three months now (on and off). The basis behind it is that I am to create a technical document that will be used to create a 2D game. The project documentation that describes what is required was pretty good giving examples where necessary, but it also left a lot open to be interpreted and lets you put your own spin on things.
So far I have a 17 page document that is still not finished. Sometimes I think I may have thought up a too complex game idea for what is actually being asked of me. But then everything I do and create during this course is going towards my portfolio at the end, so why shouldn’t I take the extra time and effort to create something that is worthwhile!
There are certain areas which I need to cover within this technical document and often I am concentrating on getting one section done that I lose focus on the overall goal and have to keep revisiting the original outline document to figure out what else I need to do.
I’d say overall I’m happy with how things are progressing, and ideally need to get this document completed by August so I can start on Portfolio Project 2 which involves actually coding up solutions to the headings given.


Warning: count(): Parameter must be an array or an object that implements Countable in /homepages/12/d118927167/htdocs/shadowpuma-afts-blog-v2/wp-includes/class-wp-comment-query.php on line 405

2 thoughts on “T2G Update : Portfolio Project 1”

  1. Hi I’m part way through part b of first section just wondering what you have to do in portfolio project 1 and what skills I would be required to know so I can get myself prepared really thanks

    1. Sean, Hi ^_^
      If the Portfolio Projects are still the same as when I did them, Portfolio Project 01 is all about documentation. Think up a simple idea for a game and document all the aspects of it. I chose a simple pairs type game and documented the game flow, the mechanics of what the game was, how to win/lose, breakdown of the game into various functions (eg. time controller, player movement/selection, card images/position/comparison), and also a section of how the game could be split workload wise (graphics, functional code, visual effects code, etc.). The document itself was around 15 pages. It didn’t receive the highest of marks, but was a good all rounder.
      Hope this helps. Good Luck

Leave a Reply

Your email address will not be published. Required fields are marked *