495 Blog Post 4

 I created more UI text for the game. This task was simple, because I can take previous Photoshop text files and quickly modify them to make new text.

 For loading screens, I took the previous background image I made for the main menu screen and modified the layer styles slightly. This has an appropriate effect that matches what loading screens usually should feel like.

 I also made this small graphic that goes with loading screens, to get the point across.

This is an icon for the game. I took some prior elements, like my main menu background and a cross hair, and put them together. I feel it is effective.

This is a higher resolution edition of the main menu background. I upscaled the image and manually smoothed out aliased edges and other low quality elements to better fit a full sized poster.







This piece is for the splash screen for the development team. I went for a vintage cowboy kid aesthetic.

470 Blog Post 3

For Sprint 5 of our project, Monster Truck Alley, I had to pull my team together and get them to tell me about what they're doing. Two group members are very close, performing many tasks together and making sweeping changes to the game's assets and code without informing me, the team lead, leaving me in the dark about what needs to be done and any issues that have occurred. This sort of behavior culminated during a formal playtest day, where the build we were presenting was broken and unplayable, while two days earlier I had seen it be completely functional.

In order to prevent this from happening again, I have attempted to secure the team's tasks and make them be more transparent about what they are working on at the current moment, and inform me of changes to that or ask me to assign them new tasks instead of nothing at all. I feel that my team should have already been doing this, but earlier attempts were met with middling and muddled agreement, with no follow-through. Now that we are nearing the end of our project timeframe, I feel that this rejuvenated approach will help push out a better product.

495 Blog Post

As I somehow did not make a prior blog post for previous sprints, this will be long and cover several new items that I developed for the 2D art team.

Concepts:


Lantern - Deadeye Desperado:

This was designed using an antique mining lamp as reference. For its purposes in the game, which is holding glowing crystals, about half of the lantern's body was removed, leaving only an extended glass chamber and the top cover as recognizable remnants of the original reference.





Pickaxe - Deadeye Desperado:

This was designed using another reference, and due to the simplicity of a pickaxe there was little to be done to make it look noticeably different. Keeping with the theme of magic crystals everywhere, the pick itself is made of crystal and painted a blueish steel, which has worn on its opposite edges and is also revealed by some crystal growth in the center.





Treasure Chest - Deadeye Desperado:

This was designed using reference of an antique strongbox. I attempted to make it look slightly decayed, with small bends and cracks in its metal and wood structure. The emissions of light is intended to imply something slightly extravagant locked within.




Staff - Senseational:

This was quite difficult. There was little direction as to what it should look like, other than coiled. I had to look up several sources of inspiration, among which included stone columns and hiking sticks. The purpose of the staff is to be the player's primary tool for interacting with the environment, and it displays whatever power is currently selected.



Runes - Deadeye Desperado:

This was a rune system I designed for use as just various environmental detail to mark something important. The developers also wanted to use it as a health bar, but I don't know how that turned out. There are three versions, just for extra variety.

This is a different rune system I made, which is specifically a set of numbers representing 1-6, or 0-5, depending on how you see it. It is intended to denote the order of objects in a puzzle, so the player can keep track of their progress. This also has three versions, for variety.

 These are runes to represent the four different types of bullets the player has at their disposal. In order, they are freeze, blast, flame, and heal. Previous versions were less runic and more vector-like, which meant they had to be redesigned according to those parameters.

Town Concept - Senseational:

This is a concept for the main area the player plays in Senseational. The parameters for its design were limited, including keywords like 'medieval', 'dilapidated', and 'valley'. After completing this line art, I was informed that some parameters had been changed in the meantime, so this concept is mostly outdated and as such it will likely remain unfinished.

Menu UI Text - Deadeye Desperado:

Deadeye Desperado required a number of text-based elements for its various menus, which I provided. If I had it my way, I would have used different fonts, but I was not able to install new fonts on the computers used to design these UI elements. 

These went through a number of variations, as I was informed of additional parameters each time I submitted what I thought was a complete package. This included additional menus and colors needing to be changed.

Title Screen Concept - Deadeye Desperado:

This is a quick concept I generated for use on Deadeye Desperado's main menu screen. It includes what I think the game's title should look like, as well as how I feel the game should, well, feel. I looked to spaghetti western movie posters for inspiration, which explains the strong red and orange hues.

CAGD 377 - Blog Post

During this sprint, I created an animation sprite sheet for the player character, as well as background images, and a dolphin for use as an enemy.

Here is the sprite sheet. It has 3 separate animations, each fairly simple; 4 frames for a forward movement, 3 frames for a jump action, and 3 frames for an attack action. As of yet, the game still uses the placeholder player character, which does not have any animation frames. These were created in Photoshop; I would have preferred to use Adobe Flash, as I feel it is more appropriate and robust in creating a set of animation frames than Photoshop, or at least I am more comfortable doing so with it.

Here is the background. It consists of 3 pieces, one simple gradient for the ocean, and two separate rocky reef outcrop layers. As they are each their own image, this hopefully will allow my team to utilize parallax scrolling. The two rock layers also fade into the background with transparency, which I don't believe will cause issues. Each piece was created by modifying a singular shape I drew using a bezier line tool, which I then cut, recolored, or transformed in any particular way. I used Krita to create these pieces. I feel it has better tools for generating and managing shapes. After this, I began creating foreground pieces that the player would actually walk on.

Here is the dolphin enemy. This is from the original character sketches I did, but had not implemented into a digital image yet as I didn't know if the team wanted it or not. It doesn't completely match the other enemy designs, namely in the outline thickness, which is an easy fix when the time comes to improve each individual image.

CAGD 377 - Blog Post 3

This week, our team presented our first digital prototype build to the rest of the class for a playtest session. The elements that functioned were the player character's jump ability, as well as a level that scrolls forward automatically to keep a quick pace.

My contributions to the team involve art products. After some pencil/pen sketches over the previous sprint work session, I created digital pieces based upon those handdrawn drawings intended to refine their designs as well as choose a color scheme.

  The player character is a knight wearing an underwater diving suit. I tried to incorporate a medieval-looking helm with the waterproof/sealed bodysuit. The character has a sea hare for a mount, which is a type of sea slug. The prongs on its head are antennae that resemble bunny ears.

 The enemies were designed with the intention of being non-standard aquatic adversaries like sharks or crabs or whatever. Since the player is rescuing jellyfish, I wanted some lesser represented creatures.

 First is a giant sea leech, which technically doesn't exist, but I found a strange blog with a fake news story about them, which also had a neat artistic rendition of one. The next is a stonefish, which is a highly poisonous and extremely ugly fish, and as we all know, ugly things are evil things.

 After the first playtest, I will have to figure out how the slug and player move together, as I have been assigned the creation of a set of animations for them. While I have done some small animations before, they aren't anything spectacular.

The program I will be using is Adobe Flash CS3, since I have had it for a long time and am adequately familiar with how it functions, whereas Photoshop's timeline capabilities just don't do it for me.

CAGD 470 Sprint 2 Blog

For Sprint 2 of Monster Truck Alley's development, our team completed many tasks. These tasks included creation and implementation of VFX, player and enemy 2D models, powerup mechanics, and a functioning level. As the team lead, my involvement with the project consisted of managing tasks for team members, making sure they have the necessary tools needed to succeed.

Some other contributions to the project are UI elements.

This is a small overlay for displaying a few text items over a flag graphic. They are for informing the player of when the game is starting, when it started, and when it ended either through the player losing or winning.
Each text element is a separate image, as well as the flag graphic.

The health bar tracks how many hits the player can take before losing. Our team is not set on how many hits that is, though it will likely be three, so I made three separate sections. There are three parts to the bar. The first is just an empty outline, with two lower portions, one green and one red. When the player is damaged, a green section can be removed, revealing the red section underneath, which I feel is a great indication of damage.



For the next sprint, we will be creating new powerups, overhauling the powerup system, implementing additional VFX, and creating better UI elements.

A running issue I have encountered is not having much to do in the way of work to assist in the team's production efforts. Many tasks are taken by two of our members, leaving only a few things to be done for the other two, which realistically are done by one person. This makes me look bad, and there is little to be done in the way of solving this issue.

CAGD 495 - Sprint Blog 1

For CAGD 495, I was positioned into the 2D Concept Art Team, which is separate from other game production teams and will be requisitioned by them when they need design work done. For this first sprint in the project schedule, I produced some concept pieces for two different teams.

The first set was for Deadeye Desperado. One design was for an enemy type, a golem. The other design was for a revolver-esque weapon. Beginning with pencil sketches, I later made digital traces and put in some rudimentary colors.

The second set of designs are for Sensational. Currently, I am working on a design for a staff that the player character will wield. The requested design calls for a coiled body, so I will need to figure out a way to make a shape that is easily reproducible and not too busy.

CAGD 377 - Blog Post 2

In CAGD 377, my team is producing a game called Jellyfish Knight, in which you are an underwater knight tasked with collecting lost jellies while avoiding obstacles and aquatic adversaries in a rhythmic platforming series of levels.

For our first sprint, we focused on creating a paper prototype. This included coming up with a rule sheet, creating a game board and pieces, and figuring out how it all worked together. My assigned tasks were incredibly light; I just had to get some usable pieces and bring them to the playtest sessions. After completing this task, I was left with very little to do until we eventually begin work on the digital prototype, and in the meantime I focused on making some concept designs for characters and such.

Unfortunately, our group had issues with getting the paper prototype to function, as well as having everyone at scheduled meetings at the scheduled time. We found ourselves without a working prototype to playtest before the official playtest time during class, which is quite bad for the project's overall health.

CAGD 470 - Sprint Blog 1

Our team has created a paper prototype for our game, Monster Truck Alley. It uses a DnD board with dry-erase markings to denote important elements. The basic rules of play consist of the player using a turn to maneuver obstacles, after which their piece is moved automatically for a number of spaces forward. The goal is to avoid enemies and obstacles to reach the end of the level.

The paper prototype is the first real task our team has taken on and mostly completed at this time. Our team has done some preliminary playtests, but we will be doing formal playtests with classmates in the next class session.

As we have not been working on any digital aspects, the team has had very little to do in terms of tasks. This will increase upon the team starting work on a digital prototype.

Character and Scene Concept Designs

The following materials are a collection of school projects involving the creation of characters, landscapes, and the like following a set of steps intended to help foster efficient workflows.

These pieces demonstrate my abilities in terms of Photoshop and art design theory.

View post on imgur.com