HW8

Homework 8, from Blender to Unreal to Git

Homework 8, from Blender to Unreal to Git
Assigned: Thur. Oct. 13, 2016
Due: Thur. Oct. 20, 2016

In this homework, each of you will create one (or more) object(s) in Blender that will be a part of your team's game. You have total freedom in the creation of this object. In your blog, describe the function/role this object(s) plays in the game and how it will be used. Include at least two pictures of your object: one when the object is in Blender, and a second image of your object in Unreal.  Import your object into your scene in Unreal, "push" your Unreal project to your git repository, and finally, provide a picture with all your team objects in your scene in Unreal.

In summary:

1) create one or more objects in Blender (15 pts)
2) Import these into Unreal  (15 pts)
3) Describe how these objects are used in your game (use your blog). The description should be in English prose, with full sentences/paragraphs. (20 pts)
4) Include two pictures of your objects (one in Blender, one in Unreal) (15 pts)
5) Upload your Unreal project to Git (git push or use the Desktop interface) (20 pts)
6) Once all the team members have uploaded their project, "pull" your project from git, and take a picture of all the objects within your scene.  (15 pts)

hw5

With the pitch document written and presented, it is time to start developing the game. To this end, each team member will choose to develop a small component of the game. Of course, task assignments will be the results of a team discussion. These tasks are left up to the team member. Examples of valid tasks are the building of a game asset (HUD, object, arg, music, game mechanic). The assets need not be implemented in Unreal, but they must be implemented in some program (Photoshop, Blender, Unreal, or yet another.) Please describe in writing what you have done in your blog, and how it relates to the team game. Provide pictures and/or video to support the description.

You will be graded on 1) the implementation, 2) the description, and 3) the images/videos that you  provide.



I created a super simple heart in blender for the game. We will use this asset as the "life"/ energy for the dog to collect. Gives the "open-world" roaming game some purpose and direction (and small "wins") through the game. Equivalent to collecting coins in Mario or something 

https://drive.google.com/drive/folders/0B6lazF2IAmLHd0thWTFzTUVOYms?usp=sharing
Link to google drive with images and model

HW 11

Given what you have learned about game design so far, identify two great games that you have played, and two games that you played and did not like (and thus did not play for long), and describe what it is about the game that you either liked or did not like.

Your answer should address game mechanics (not discussed in class, but read the relevant book chapter), game balance, experience, aesthetics, etc.


Growing up, I used to play a lot more games using my Nintendo 64, Game Boy and the occassional Playstation or Game Cube. As I got older, my attention span shortened and I did not enjoy games the way I did growing uo

Liked: 
Growing up, my favorite game was Mario Cart. It was an easy enough experience, but being the best or winning ever race was not always possible as levels and terrains gave the player different sensations and courses to conquer. Also, playing multi-player made it all the more interacting. Aesthetically, I remember different courses to be geared to different tastes. One, was rainbow themed whilst others were minimally aesthetically "in your face"

Non-console game- Uno. The cards are easily read, colorful and appealing to all ages. The game is also pretty self explanatory and players can jump in and out of the game easily. The game is simple, but has a good balance of "challenges" with wild cards, 'reverse' cards and 'pick-up' cards. The experience is just an enjoyable game. There is a level of just enjoyin the game that requires little strategy and doesn't overly push for competitiveness


Disliked:
When I got older, gaming become more exclusive to mobile games. Games like Temple Runner and simple iOS Games. Flappy Bird was my absolute least favorite and I could never get behind the fad. The design and overall aestheic was simple and I appreciate that on a mobile game. However, it was crazy imbalance. It was difficult right from the start, and the user had to start literally from the start after dying which was incredibly infuriating

Battleship was incredibly infuriating. There is no strategy. There should be a balance of strategy and luck, but it leans heavily on luck. However, only two players can play and there is not constant satisfaction where most of it results into disappointmnet. It's not interactive enough. The player is literally looking at their "set" and game pieces the entirety of the game. The only "fun" is putting in little pegs. Aesthetically, the little ship holders (?) looks nice and it is simple to put in pieces, but the pieces don't encourage much interaction betewen players aside from announcing coordinates