Aaron Hogan

Reading 5 After last weeks reading, I was very confused on what to do, but luckily I got to speak to Shaun today in a face to face meeting which helped me a lot. Before I was unsure what the matrix was for and what articles to be reading but now after the help from Shaun I feel like I have a much better understanding to what I have to do. For this weeks reading I wont have as much work was I would like to because I only really understood today what I have to do. For next weeks reading, I feel like I will be much more prepared and will have way more work because I now know much more work that I have to do. For todays reading as I only found out today what to do is about the articles I found and will get headings from to be included in next weeks reading when I have more time to gather information. Some articles I found interesting include: -Methods and apparatus for input devices for instruments and/or game controllers: https://patents.google.com/patent/US8198526B2/en -Game ...

Game Vision Statement This week for my progress on my game design project, I read and learnt about vision documents. I read an article called "The anatomy of a design document, part 1 : Documentation guidelines for the game concept and proposal". I enjoyed reading this article as I feel like it benefited me as I learned new things about game designing that I never knew went into the development of a game. I didn't think as much detail and research went into making a game before starting my journey into making a game but after reading this article, I realised there's a lot of information to know about. The purpose of a documentation for a game is to communicate your vision in detail. It helps the programmers, designers and artists to know what their supposed to do instead of asking. Adding specific guidelines will benefit your project. Theres 4 reasons for adding guidelines :  - Elimination of hype: guidelines eliminate hype by forcing the designers to define th...

Unity Tutorial 03 In this tutorial for this week,  I had to create a clock on Unity.  I thought this type of tutorial was easier to follow, I felt like I worked better doing the tutorial with screenshots and text  rather than watching a video. I just find it easier in my opinion to work on the challenge while looking at screenshots. This was the most enjoyable tutorial I've done because it was easier to follow the steps than the other ones. I'd much rather steps in this form than videos in the future. I found while I was doing the tutorial that I would miss a word or two a few times while filling out the script, which would not make it work the way I wanted to and I wouldn't know where I was going wrong with the tutorial but I realised after a few minutes that I missed a word in the script.  I also had a problem with creating the arms on the clock but after a few tries I got it to work. Other than that I really enjoyed this tutorial and I was happy to see my clo...