Skip to main content

Diablo Trees In Game.

I'm going to leave trees and move on with some other stuff for a while.
I think the trees look pretty good and performance is much better than when i was using individual tree sprites.

I'm still conflicted about how to handle alpha in the game. Here's a shot of the trees with clip alpha:


Clip alpha is basically either/or alpha. Either it's 100% transparent or it's not. It's very fast to render, but it gives pretty horrible edges.

Another option is to use alpha sort. This is similar to the alpha blend I use for the infantry sprites (grayscale alpha) but it works to sort the individual polys of the mesh to make sure they get rendered in the right order.


Performance is slightly slower than with clip alpha. But the end result looks much, much nicer. Again this may be something I make a part of the graphics settings, as it would be possible to load different trees from file, some with alpha sort and others with alpha clip and lower resolution.

Comments

Popular posts from this blog

Vinland 1936

What have I been up to this month?

Well you can see it in a couple of development blog videos, here, here and here.

Vinland 1936 is a game I've been working on (on and off) for about 3 years. It is somewhat based on the old Nirval interactive game, Blitzkrieg;





I hope you've played it since it is one of the best games ever!!! (IMHO)
Blitzkrieg was a real time tactics game. You didn't build a base, or spawn units. It wasn't about rushing the enemy. You got a small number of troops and vehicles that could be replenished or repaired if you had access to a supply base and the right supply trucks, but couldn't be replaced if lost. Once your vehicles were destroyed and your infantry killed you were finished. You couldn't just churn out some more from your factory and have another go at rushing the enemy guns. This made you invest a lot in each of your units. They really mattered.

It was also procedurally generated. Each mission (except for the historical missions) was…

Reboot / Remake / Restart

Although the roguelike project was going well I had a few issues with some parts of the code, and the sheer size of the project was something I could see stretching away in front of me for years with no guarantee that people would actually want to play it when it's finished.

It's time to try something a little less ambitious.
I'm going full rogueLITE!

Using a lot of the code from the roguelike project, I started making a more limited game.
There will be a single character, combat will be more arcade like, there will still be a chance to upgrade and develop your character's stats, but they represent only a single class and have fixed equipment.

I've got a fun character, an interesting setting and an exciting story lined up. It still utilizes my low poly style, but things are going to be a little more cartoony.

Game play involves mostly chucking bombs at the enemy.

But there's also a lot of platforming, jumping from multiple levels is part of the game. And you ca…

Materials.

I'm currently working on the inventory and items system.
I've got a good idea of how it's going to work, and I've made a few test demos in blender so I know how it should fit together, but one area I had some trouble with is how to make the items more interesting.

I don't want to have just sword +1, necklace of AC +5 etc... I want items to feel like they are unique. So I'll be designing a few base item types and then having them generate some qualities.



The first quality is status. An old broadsword, or a rusty helm. Or spoiled meat. These will be limited by item type, so you don't end up with rusty meat or rancid chain-mail. They add a modifier to elements of the item's stats, either a positive or a negative modifier.

The second quality is wear and tear. This is more dynamic since it can change, as you take or deal damage. This might not be seen in the item's name, but rather in a status bar or something. However, it could cause the item to lose so…