Hi! It has been a while for sure. I hope you’re doing all ok.
Several things have been worked on the past time. Some on the engine (not much to show), some more graphical stuff. So lets begin with that, its always nice to show things:
Graphical enhancements
I’ve been getting quite some help on the graphical side of things lately from Rozmy. He revisited all structures:
- sharpened them where applicable and tidied things.
- provided new flag animations (instead of the 2 frames you have in dune 2).
- More animation frames for the Outpost, Refinery, Starport, Repair facility, Light-Factory, Heavy-Factory and Hi-Tech
This all required me to redo some drawing logic in the engine so that things can be animated separately. In dune 2 flags were part of the structure frames in Dune 2, but now in D2TM they are not.
Animating the flags independently from the rest of the structure animation gives more flexibility when you have to combine animations. For example: flag animation with “door opens on repair facility” animation.
To give you a “before” and “after” picture, look below. Move the slider to the left to see the new graphics. Move the slider to the right for the current version. Can you spot all the differences?
Options menu, no more ‘instant-quit’
A much wanted feature was to not quit the game when you pressed ESC
.
In the next version there is an introduction of something like a “GUI” (Graphical User Interface). I don’t use a framework for this so I had to build some things myself. Along with this I redid the main menu. finally I made a first version of an “options” menu. Which kind of resembles the one in Dune 2.
A comparison of the main menu (slider works the same as above)
The options menu can be accessed by pressing ESC
anywhere in the game. (except from main menu, that still means exit game).
Aside from rendering stuff this meant the game had to have some sense of “states“. Currently most code does not really have its own “state” code. I am slowly migrating the code to something more contained. Meaning, new things I write are within their own State class. But for having an options state I had to do some work on the ‘old’ code.;
This way I can have one place point to a “current state”. The other (if any) states are being kept in memory so I can switch between them if required. Ie when you press “back” from “options” you want to continue where you left in the previous state (mission select, playing game, etc).
Sometimes you want to go to a new state (ie main menu). All these things were not built in so that also took some work.
With this there is a first step taken.
Once this has been implemented properly, saving and loading the game becomes easier to build as well.
What’s next?
Looking at the project board: A few bugfixes and a few small improvements are on the todo list. I will re-evaluate what really has to go within 0.6.5. As I still intend to release a new version in December.
Comments are closed