Bidness Crads
Get one of these rare KPULV collectors items at Game Developers Conference! :D
No Comments
Get one of these rare KPULV collectors items at Game Developers Conference! :D
Dev Log: Some Shaders
One of the things I miss about working in FlashPunk and working with a bunch of bitmaps and blitting to the screen is the super easy color overlay blending. FlashPunk had an Image blending mode called Tint and it could be used in place of Multiply and it is amazing for doing effects like fading an entire sprite to a specific color. The world of rendering quads and triangles I don't have such a luxury, but I do have shaders.
I've been working on the building islands animation, and here's a really fast version of it:
At the end of it when the island pops out it's silhouetted with solid white. The white fades to cyan, and also fades back to the normal art at the same time. To get this effect I used a simple shader to handle a color overlay.
I also use this code for enemies as well. When they get hit they turn red for a brief moment. I use code in the C# end to determine the color and intensity of the overlay and pass it along to the shader.
Soon I'll probably make some sort of system that allows me to easily add a bunch of color overlays to the shader and automatically figure out the final color for the shader to use. I'll probably also use the shader for a bunch of different effects down the road.
I've been working on the building islands animation, and here's a really fast version of it:
At the end of it when the island pops out it's silhouetted with solid white. The white fades to cyan, and also fades back to the normal art at the same time. To get this effect I used a simple shader to handle a color overlay.
uniform sampler2D texture;
uniform vec4 overlayColor;
void main() {
vec4 pixcol = texture2D(texture, gl_TexCoord[0].xy);
vec4 outcol = mix(pixcol, overlayColor, overlayColor.a);
outcol.a = pixcol.a;
gl_FragColor = outcol;
}
var overlay = Util.ScaleClamp(Combatant.Stun, 0, Combatant.StunMax, 0, 1);
var color = new Color(1, 0.2f, 0.1f, overlay);
ImageSpineAnim.Shader.SetParameter("overlayColor", color);
Dev Log: Slow and Steady
I've been tinkering with a lot of systems over the past couple of days. Mostly stuff involving enemies, and some other things involving building islands and structures on the islands.
At some point last week I sat down and tried to figure out path finding with moderate success. I have something working, but it's pretty dang laggy when it has to figure out a path. As far as I know I'm just doing straight up A* path finding and I copied the psuedocode from Wikipedia right into the game. I started looking into using different data structures for storing things to hopefully speed it up, but honestly I still have no idea what I'm doing and I don't know how to use some of these fancy things that people suggest (priority heaps, or something?)
I took a break from that to tinker with placing structures on islands, and trying to figure out how I want to animate the building process for building a structure on an island. This is also a tough one to solve, and I'm not sure if frame by frame stuff in Flash would be good, or if structures should be animated with skeletons similar to the enemies using Spine.
Back in the world of enemies I've started experimenting with behavior trees for how they should interact with the world. It seems like a good way to do things, but part of me feels like it's over-engineering. Setting up a whole series of classes for the system to run the behaviors, and then every simple little task then has to be a behavior command... I kind of like systems like this, but I wonder if it will be worth it in the end working on a system that takes a lot of up-front work to get running.
It's definitely a very different way of doing things outside of the game jam environment. I've made a lot of cool stuff in game jams, but it's all been on top of really odd code that doesn't leave a lot of room for expansion. I'm trying not to design or code myself into a corner when it comes to working on this new game, so things are going a little slower than they did for Offspring Fling, but it's also probably due to the fact that I'm in pretty unfamiliar territory. Working on something that's not a platformer can be pretty tough!
At some point last week I sat down and tried to figure out path finding with moderate success. I have something working, but it's pretty dang laggy when it has to figure out a path. As far as I know I'm just doing straight up A* path finding and I copied the psuedocode from Wikipedia right into the game. I started looking into using different data structures for storing things to hopefully speed it up, but honestly I still have no idea what I'm doing and I don't know how to use some of these fancy things that people suggest (priority heaps, or something?)
I took a break from that to tinker with placing structures on islands, and trying to figure out how I want to animate the building process for building a structure on an island. This is also a tough one to solve, and I'm not sure if frame by frame stuff in Flash would be good, or if structures should be animated with skeletons similar to the enemies using Spine.
Back in the world of enemies I've started experimenting with behavior trees for how they should interact with the world. It seems like a good way to do things, but part of me feels like it's over-engineering. Setting up a whole series of classes for the system to run the behaviors, and then every simple little task then has to be a behavior command... I kind of like systems like this, but I wonder if it will be worth it in the end working on a system that takes a lot of up-front work to get running.
It's definitely a very different way of doing things outside of the game jam environment. I've made a lot of cool stuff in game jams, but it's all been on top of really odd code that doesn't leave a lot of room for expansion. I'm trying not to design or code myself into a corner when it comes to working on this new game, so things are going a little slower than they did for Offspring Fling, but it's also probably due to the fact that I'm in pretty unfamiliar territory. Working on something that's not a platformer can be pretty tough!
Doodle Post
A self portrait for my business card design for this year's Game Developers Conference.
Dev Log: Workin' Away
I've been pretty heads down on my game project for the past couple of days. I've managed to fix a few bugs in Otter as well, but I'm putting a hold on any official updates due to issues with the Spine license that I'm pretty sad about.
The Spine license only allows people with a full copy of Spine to download and use the official Spine runtimes. I didn't know this at the time when I created a simple Spine graphic type for Otter. The situation I'm in now is trying to figure out how to easily provide that Spine graphic type for people using Otter, but also separate it from Otter so that I can distribute it only to people that have the Spine license... argh.
In the wild world of my new game, I've been just working on some art related tasks. I've been jumping all over the place and working on totally different things on each day, but that ends up working out because it keeps things fresh and interesting.
That's all for now! Things are going to be pretty hectic for me in the next 2 or 3 weeks, as GDC is fast approaching and I'm also going to be traveling a little bit before then. If you're going to GDC, we should hang out and get sushi!
The Spine license only allows people with a full copy of Spine to download and use the official Spine runtimes. I didn't know this at the time when I created a simple Spine graphic type for Otter. The situation I'm in now is trying to figure out how to easily provide that Spine graphic type for people using Otter, but also separate it from Otter so that I can distribute it only to people that have the Spine license... argh.
In the wild world of my new game, I've been just working on some art related tasks. I've been jumping all over the place and working on totally different things on each day, but that ends up working out because it keeps things fresh and interesting.
That's all for now! Things are going to be pretty hectic for me in the next 2 or 3 weeks, as GDC is fast approaching and I'm also going to be traveling a little bit before then. If you're going to GDC, we should hang out and get sushi!
Dev Log: More Explosions
Been having a lot of fun with my workflow of animating in Flash, exporting to a SWF, and then using ShoeBox to convert to a sprite sheet. There are some hiccups in the pipeline still, but hopefully I can get them ironed out before I get any deeper in the art department.
I should really be working on the actual game part of this game, and probably all the systems that are going to be needed to be intertwined, but at this point I'm having way too much fun with particles. I've been bound by the word of Flash and ActionScript 3 for so long. Having 30 particles on the screen in Offspring Fling was a nightmare for performance, but now in the land of SFML, C#, and Otter, I can spawn hundreds of particles and the game doesn't hitch at all -- not even in debug mode!
