After a week of some really good coding, I had GP3/GP4 loading completed PERFECTLY, so it was time for a release!
Except I hadn't. Lying in bed, I rose from my position as if possessed by a Bloodhound... buggery, I had forgotten to implement the "repeat" flag.

So, when next I get time, it's fixing that, and then writing documentation on how to use Drumpster.
Not that it's difficult (it can be as simple as putting a folder called "songs" in the executable folder), it's just... very configurable... via INI files, which I want to document.
I am considering making an INI generator, using Delphi or something similar, so I can do it quickly, it won't look too much like ass, and it will run under WINE perfectly (but Linux users will welcome hand crafting INI files, right?).

As it stands, I'm quite proud of what I have achieved. Using KKrunchy (an executable compressor), I got the executable down to 96Kb, that's with the built in meshes!
Anyway, it's a single executable, reads MIDI and (some) Guitar Pro files, and shows them like a Rock Band clone would.
Input will come later, for now it's a perfectly barely usable little learning utility.

How Drumpster looks right now (the game screen can be themed on a song-by-song basis):

Playing vanilla MIDI/GP3/GP4 files with built in meshes and textures. Isn't it just preciously ghastly?
It does show that open and closed hi-hat states are supported though.

This shows that every song can have a custom background and set of meshes for the notes.

This, well, I just wanted to put a Pantera song up really. And it shows you can change the neck texture, and colour meshes individually.

( 314 views ) permalink print article