I'm working towards having a working vertical slice of the match segments ASAP (right now I'm still missing too much of the main player moves, an actual opponent with actual IA, and general stuff that makes the whole thing feel off) to showcase in a video to make a better presentation in this thread, but if you like what you see, you can always follow the updates I post on tumblr!
Here is an occlusion that I baked from my high poly model for some girders in the game I'm working on now:
Sounds good
Don't worry about me, I stack up UVs like a mofo whenever the situation calls for it; I'm very particular about maximizing texture space.
Don't worry about me, I stack up UVs like a mofo whenever the situation calls for it; I'm very particular about maximizing texture space.
For this current project though, I'm baking different lighting data into the actual diffuse map and then taking the various results to photoshop and turning them into a more stylized final texture. I set up my lighting so it isn't straight on the level, but it produces more interesting shadows because it's offset. So for many of my assets, stacking UVs isn't an option (except on my character where I did the common half/half thing).
In case you're curious, here is something else I rendered out for that same object:
Hi,
yesterday I got some kind of nostalgic flash and tried to run a project, i had worked on way back in 2006. it was a Zelad-fan game and developed in GameMaker 6. Great times. Here a two small gifs (had better ones, but i didn't know imgur only supports up to 2MB (for unregistered users?)).
Don't worry about me, I stack up UVs like a mofo whenever the situation calls for it; I'm very particular about maximizing texture space.
For this current project though, I'm baking different lighting data into the actual diffuse map and then taking the various results to photoshop and turning them into a more stylized final texture. I set up my lighting so it isn't straight on the level, but it produces more interesting shadows because it's offset. So for many of my assets, stacking UVs isn't an option (except on my character where I did the common half/half thing).
In case you're curious, here is something else I rendered out for that same object:
Yeah, it's certainly the aspect that needs to be designed around. I've done it for one project before and I know it can become unruly fast; my answer to that is simply not having many assets required for this game. And yeah, I don't have many objects that are the same and rotated.
It also helps that I'm working with a fixed camera that will only move up and down, so textures only need to be as large as to support the display resolution.
Wait... for real?! Here I thought I was being efficient using the unlit shaders. I'll have to check with my programmer if he thinks this might be a problem for us. I never checked into the vertex count differing; any idea why it triples it?
Absolutely!
C# feels quite like C++, and you don't have to write a whole load of code to get things to work. The system itself is written for you.
Just have a go!
There's Inkle Writer that was warmly recommended by the Banner Saga team for writing interactive stories with multiple choices. It might work out for you.
Other possibilities include:
Inform 7
Twine
ChoiceScript
Articy: Draft (Commercial)
Admittedly I haven't used any of them personally so I don't have a recommendation beyond what I heard from the TBS people. Let us know what you pick and how well it works.
Now: Linear algebra.As some of you know, I've been coding games for a living since the 90s. I'd like to share some of the things I've learned from the supercool eggheads I've been lucky enough to work with. To this end, I have started to write some game development articles that I hope to be of use to others. Nothing is public yet.
I'm starting with the basics, game loops and state machines, architecture. But, as there are so many up and coming game devs in this thread, I thought it might be an idea to ask what you'd find the most useful topics to have explained? Even if you're not new, what would have been useful to know at the start?
I'm thinking of covering universal topics rather than specific tutorial type of things, to begin with. I'll probably end up writing sample Unity projects as things get more specific. I love Unity, and it should be a great way of demonstrating concepts and implementations.
Any suggestions, or questions, mail me at vamflax@vamflax.com. And if anyone ever wants a Desura key for Chopper Mike, just mail me
As someone who came from C/C++/Java, I also thought that the GameMaker scripting language was surprisingly easy to use and fairly full-featured. I would not want to make a full game with it, but you should be able to do a lot.
xD
Aye. Our 2D project is more or less a "Lite" version of our original concept. Its very Ninja Gaiden NES like so its nothing fancy, should be super simple to nail down. I'm of the mind that getting things up and running quick with drag and drop to start then turning it all (most of it) into script for easier editing. Ease of development is a huge factor and while we are using Unity, its a bit much for something so simple when time is limited - making that time count now is important.
Thanks for the heads-up. We talked earlier and decided we'd gun for GM. I have been scanning the docs most of the day and I find they are pretty good to start with. I'm still a bit perplexed with rooms and views. I have read some games bog down with large rooms but it shouldn't be too much of an issue with tilesets and object management. No need for everything to be spawned and awake the entire time in a room. I'm guessing some people use too many objects. Rule of thumb even in Unity for me was to instantiate off screen when close every chance I had to keep object activity to a minimum.
Interesting idea. I like it. As for the sprite I feel 2 things: he is upright just a bit too much, maybe a slight lean forward and as for his arms, I dont believe they need that much sway, if any. Other than that it looks excellent. A little bit of a lean would accentuate forward momentum visually and less swaying of arms would be an indicator of strength and purpose of character. The current animation makes it seem like he is running FROM something and not actively trying to engage in persistence of movement.
The arms feel off to me. I can't really seem to get them right. I'll probably take a break and come back with some fresh eyes later.
So I feel like getting my idea out there....here it goes.
What is it?
It's a Metroid-style sidescrolling exploration game, with a twist. Rather than going with traditional action combat found in most games like this, I'm opting for a turn-based system.
The combat will be vaguely reminiscent of Press Turn from Shin Megami Tensei: Nocturne. Basically, you will start the battle with a certain number of Action Points. AP dictates any action you do. So attack, defend, and all skills have an associated AP Cost that you must pay to perform that action. You can perform as many actions per turn as long you have the AP to do so. This will allow you to perform combo attacks, which are basically just an extra attack for performing certain actions in a sequence within that turn. So if... we have Fire + Attack set as a combo, it will perform some special attack for more damage and more importantly, an added effect. These effects will range from simple poisoning to impairing AP Regeneration. There also going to be elemental weakness' that will remove turn points from the enemy if hit, or vice versa if yours is hit. There is actually a bit more planned, but these are basic tenants of the combat system which won't really change too much.
Combat is definitely the most fleshed out of my ideas but I know one other design decision I've made is I want any items or skills you obtain to have a use inside and outside of combat. So you get a new weapon, it may provide a double jump. You learn fire, you can burn down that obstacle in your way or initiate combat from a range.
I feel the hardest thing to manage to do is nail pacing between combat, exploration, and platforming. I want combat to be quick so that it doesn't slow it down too much, but that may not be enough. I've got a couple more ideas on how to solve that, but I won't bore anyone who decided to read this any longer.
