Skip to content
Oct 7 11

D2TM (v0.4.6, unstable, revision 524) released

by stefanhendriks

A new unstable has been released. There are a lot of changes under the hood, but you will not find any changes in functionality. In fact, one major functionality is reduced: playing campaign mode.

I have disabled campaign mode because in the previous unstable a crash bug was found in campaign mode. Since I have not worked on that bug yet, I did not want anyone else to experience it.

Another reason is that this is the last unstable release before ‘refactoring the guts out’ of the current engine. I have set up a bit of boiler plate code that will be the beginning of an implementation of a few design patterns. Tearing apart the global state that exists in the current engine. The most obvious design patterns are: Factory, Delegate, Composite and State.

So what does that mean for all you guys in the next unstable:
– the main menu will be drawn properly regardless of the resolution
– the skirmish menu will be drawn properly regardless of the resolution
– state transitions will be better (the current unstable has some flaws in these transitions)

In the previous news message a question was asked about a roadmap. More information about a roadmap will be published soon as seperate page on this website. Stay tuned!

In the mean time, grab the unstable if you’re curious from here

Oct 4 11

What is going on?

by stefanhendriks

In case you’re wondering if anything is being worked on… Let me shed some light…

You can see for yourself here.

Oct 1 11

Revision number now part of version

by stefanhendriks

Its a tiny feature, but it will make life easier for development.

The next version will tell what revision number is used, this number is generated from the svn tree when the binary is created.

Example:

Sep 26 11

Crash bug in unstable release, revision 488

by stefanhendriks

As reported in one of the comments, the latest unstable release will crash horribly when playing the campaign. Be advised to play the skirmish games only, there are no known crashes there. If you encounter anything crashing, let me know.

Sep 25 11

D2TM (v0.4.6, unstable, revision 488) released

by stefanhendriks

So it has been, almost a year ago I had released an unstable WIP version… So its time to release again!

Grab it from the unstable releases page!

Aug 26 11

Update

by stefanhendriks

I’ve had a holiday and have worked on D2TM from there when I felt like it. The result is actually quite nice.

I have rewritten the selecting box logic, so now all mouse logic is in a Mouse class. Finally. I have also found this memory leak, which really wasnt a memory leak but sloppy initialization.

Also, I have made it far more easier to determine if a mouse is within a specific box of coordinates. Welcome the “rectangle” class. I have used it now in a few places and I intend to update the code where I find similar logic. I love removing code and keeping the game working.

Last but not least I tried to make the credits animation even more fluent. Although the animation did not get more fluent I did refactor the CreditsDrawer class.

I will be working on the GUI related stuff now again, so the menu looks ok and a new version can be wrapped up. Can’t wait? Then just check-out the source code 🙂

Jun 11 11

Whats going on?

by stefanhendriks

I’ve been quite busy with real life things. But D2TM is not far from my mind. Most recently I’ve discovered a memory leak. And its eating up all my time. So do know it is still being developed on.

Mar 17 11

Skirmish mode working again

by stefanhendriks

I had refactored quite a lot. So much that I had broken a few existing features. Like skirmish mode. Just entering skirmish mode caused the game to crash. This is now fixed. I can now continue fixing up the GUI there and then finally release another unstable!

Feb 27 11

Not much news means… lots of development!

by stefanhendriks

You might wonder if there is any progress. Well, wonder no more, but enlight yourself with the google code updates link

So, in short, yes I am working pretty much on the project. I compare it a bit like a operating on a patient: multiple bypasses, a heart surgery, and much more still to be done.

However, although I have officially broken with the old code design and I’m trying to decouple as much of the components. (it really looks like spaghetti code with meatballs sometimes). It does mean I code a lot, but feature wise it will not be much better. In the end the code should be much easier to understand, maintain and so forth. This also means adding new features should be easier.

Currently I’m working on ‘getting skirmish to work again’ as I have broken serious initialization code in my previous commits. Once that works, I’ll fix up the drawing of the menu’s a bit and then release a new unstable.

Stay tuned!

Btw, thanks for visiting my blog post about refactoring. Looks like a lot of people read it. I’d like to hear what you think of it, so leave a comment or mail me. Thanks!

Feb 20 11

Refactoring code, what is it?

by stefanhendriks

Always wondered what is meant by Refactoring code? Basically it means : change the code but without changing the observable behavior. A developer does that to improve readability, reduce complexity, make it easier to maintain (find bugs and fix them).

If you wonder how such a refactoring looks like, you are lucky because this blog post gives you a very nice view on how it is done on Dune II – The Maker.