Game Design, Programming and running a one-man games business…

Emergent L33tness

I was just testing a new laser blast graphic I added to the game, and had two big fleets of cruisers and frigates flying towards each other blasting away like mad, and noticed that the front frigate (which was under serious attack) seemed to be drifting backwards.

This puzzled me, because although i did once code support for reverse thrusters, I turned it off, and knew anyway that ship didn’t have any,

Then I realised that it was the physics of the blast effect. The number of enemy blasts piling onto the ships hull was not only damaging it big time, it was knocking it slightly backwards. I had forgotten that could happen :D

I wish this game was finished already so I could just sit down and edit some cool videos of stuff like that…

One of the main changes today was for fighters. To get a better sense of huge ships, I scaled all the fighters down by a fair chunk. Now when you add a fighter squadron, you get 16 ships instead of 9, and they are smaller. It does seem to look a lot better. The cruisers never looked big enough before. The AI is pretty fast and it doesn’t seem to matter with a few hundred ships per side, even with all guns blazing.

Things going zap

I’ve got lots of minor stuff done lately. Tiny animated welding drones that hover around damaged ships when they have auto-repair systems are now done. Plus I added a very basic scoring UI. (some art, such as the playback buttons need to be done properly. The whole battle section is pausable, and you can toggle the UI off entirely to just watch the fun.

Look: things going zap:

I need video clips of amazing space battles. Or decent hi-res images. Post any links here if you have them.

Gratuitous Empire Selection

I’ve got a new ship added today, plus fixed some turret-related fun, and got the interface in for the race-selection screen, where you get to actually choose who to fight as (subject to unlocks). Small screenshot below:

Because that sort of thing isn’t as much fun as coding new weapon types or improving the visual effects, I might treat myself to improving some graphical stuff for the rest of the day. I’m looking forward to the time when all I have to do is balance the weapons and arrange basic ai fleets to fight against, but I suspect that it’s a long while to go yet.

Difficulty levels and other ‘wrapper stuff’

I’ve been trying to avoid acting too much like a graphics junkie and getting some work done on the gamey stuff instead. I’ve put in difficulty levels today, and also made some decisions regarding what race of aliens the player controls.

The main part of the game currently has ten missions, basically defined by a certain backdrop, of a certain size (some maps are bigger than others) which some other variables such as nebula effects on shields etc. These levels also define the maximum fleet size (in ship and pilot terms) and which race the player fights against.

So today, each of these missions has three enemy fleets rather than one, the normal, hard and expert AI fleets, which are of differing sizes. Obviously the bigger fleets are harder :D. During combat, the enemy AI is the same as yours, so the difficulty comes purely from the force that is fielded against you. I may get around to the AI evolving its own fleets, but thats a whole can of worms.

There will be some ‘other stuff’ that will give the game longevity beyond those 3 fleets in 10 different missions, but I’m not talking about that stuff yet :D

The other thing decided today was that the player will fight the game as ‘the federation’ which is a ferengi inspired race whose backstory I’m still mulling over. Once you have beaten every mission on Normal, you will unlock the Rebels as a selectable playable race for each mission, beat them all on Hard and you unlock the Alliance, Beat them all of Expert, and you unlock the Empire. That’s the plan anyway. Any thoughts?

Today’s worklog

8.00AM: Clement Freud has died. He gave me an award at my secondary school many years ago. He was very short. Also he was very funny

9.10AM: All the business email stuff is dealt with, time to start work on putting one of the new ships into the game, one I have declared to be the ‘Imperial Centurion Cruiser’. It looks badass

9.50AM: Most of the graphical stuff is done and dusted. Now I just need to add in the data defining this ships damage textures and module slots, and get it tested and in game

10.30AM: The Centurion cruiser is done and looks great in game. Took a screenshot to give feedback to the artist. Everything seems to look ok, so I don’t need to go back over any artwork. Plus the multiple beam lasers look fantastic. I’m pleased

11.10AM: There is definitely a shutdown problem with the game. Dev Studio churns for ages. Must be a huge and new memory leak somewhere. Damn.

11.50AM: It’s definitely a bug with the main battle screen. But where? The sound? graphics? AI?

12.00AM: Interrupted by door to door salesman, thus killing my efficiency. Time to release the hounds.

12.20PM: I suspect this isn’t a memory leak, but just my debug output backing up bigtime because every time I create a blast glare effect (also used for non-penetrating shield impacts), I tell the debugger about the texture I used. Clearly this code is inefficient anyway, because with dozens of the smaller glares I need to have that texture cached, not be looked up so often. The game now shuts down fine in debug, but I need to fix the underlying inefficiency. In fact, it’s worse than I thought. I need a newer, efficient system for shield impacts

12.35PM: Works fine but forgot the original texture was a quadrant and this one needs not to be. redoing it… Also just spotted a graphics glitch with the conĀ  trails pulsing on and off.

12.45PM: Having crash issues when trying to do some profiling, Grrrr. I will mull it over some wii-jogging and a cup of tea.

1.30PM: Still can’t get profiler to not crash. Time for tea.

2.20PM: it now crashes somewhere else. progress?

2.50PM: Sod it, I have a workaround, and bugs to fix. some lights in the wrong places, and an idea on how to make drawing running lights faster if they are zoomed out. (check rendered size > 1 pixel BEFORE checking if onscreen, which takes longer).

3.30PM: The debug copy no longer links. some obscure ANNOYING linker error to do with debug and not debug Microsoft crap. Very tedious and I’m not getting actual game stuff done :(

4.14PM: Think it’s fixed, plus I tracked down the flashing con trials bug. It was me not setting the render mode correctly before I drew them, and them getting drawn early if they filled up a vertex buffer before I was ready to render them all. Good old Nvdia perfHUD was my saviour. Now back to coding fun stuff.

6.25PM: Finally got the linking stuff fixed by a total wipe and rebuild. Grrrr. Next on the agenda is adding some better parallax effects, which are a nightmare with 2D + zoom + variable screen res and scrolling.