The work on AMBERs game logic and teams system has turned up a little nugget of eye candy - Team colours.
Using dynamically generated textures, I’ve been able to keep a single base texture for each model, but modify it at run time to apply a team colour and a joint colour.
I have written a few wrappers and objects for OpenGL during the development of AMBER. The first was a general OpenGL wrapper. This used the top left of the screen as the origin for orthographic projections, mainly because I was used to it being there and it avoided problems with mouse coordinates.
Next came the CBFG text class. This was intended to be dropped into other people’s code, so I used a bottom left origin as seems to be standard in OpenGL.
More recently I’ve incorporated my GUI class into the GL wrapper and bolted my text object onto it to provide textboxes, lists, etc…
This is where the problems began, the GL class and the GUI object use the top left as origin and the text class uses the bottom, so all the text in the controls was upside down.
I’ve rewritten the GL class and GUI class to use the bottom as the origin as this is the OpenGL way. However, it seems strange that every other system I’ve used treats the top of the screen as the Y axis origin. Why does GL have to be different? Is there any gain to be had by doing this? Or could I just fudge the projection matrix to use the top as the origin?
Ah well, it’s done now, I may re-visit this during optimisation, but that’s a long way off.
The underlying mechanism of the actual combat within AMBER is starting to come together. Not much to see, so no eye candy I’m afraid. However, it does bring the prospect of a playable version closer.
I’ve ended up using a huge switch/case statement to break the turns down into phases, beyond even the Initative, Move, Attack, Resolve and Heat from the original game. I’m not sure if this is the most efficient method, but it allows me to work on individual states without affecting all the others, plus extra states to be added in easily.
If I can just stay off the eye candy for the time being, I should make some good progress.
AMBER is a long running personal project that aims to produce a 3D multiplayer version of the Battletech board game.
The project started in 1999, and has been developed with Borland C++, MS VC++6, VC.NET, Bloodshed’s Dev-Cpp and Visual Studio. Target platforms have included MS-DOS, Windows GDI, DirectX and OpenGL.
The current version is being developed for Windows with OpenGL and may be ported to Linux.
To say that AMBER is a slow moving project is an understatement. I have a busy job and a young family. Development tends to happen in random chunks whenever I can get 5 minutes to myself.
A small break for a family holiday and some work commitments. Also, I entered the GPWiki.org coding contest last week with a pathfinding demo.
The previous in-game model format was MD3. The format uses snapshots of the mesh for each frame, creating huge model files which require the vertex normals for each frame to be calculated at startup. The normal calculations alone took 30-45 seconds per model. The files were over 1Mb each and had a huge memory footprint. It also made the workflow for modelling a nightmare and very much a one way process.
I’ve decided to create this dev diary as a blog rather than keep updating the ‘News’ page. It’s easier for me to keep this up to date than to keep adding stuff to a webpage.
Currently, AMBER is going slower than ever. I’ve re-jigged the GUI system and I’m in the middle of developing a content manager to ease loading resources into the game.
On the eye candy front, the Locust and Warhammer models are currently getting their UV maps sorted out.