Island War Day 3

I decided to put some work into creating an editor that I can later use for building the levels and perhaps even include with my game. XNA gave me a hard time getting it to work inside a Windows.Forms application and I had to rewrite several of the XNA classes until I had a properly working XNA UserControl allowing me to render my game world inside the editor window.

Screenshot of a height map editor with dialog controls and a tool panel

Of course, the editor had to look modern and neat, with dockable panels and color gradients all over the place. As it turned out, there is no built-in solution for docking windows in the .NET Framework, so, given my plans to release the game’s source code, I had to find a solution that was both free and provided a decent user experience.

Read More

Island War Day 2

I know, as always, I’m a bit late with updates, but just in case you don’t know yet, the Microsoft guys finally opened www.xna.com. Finally, a complete website dedicated to XNA instead of the cramped MSDN section!

The developer area has been moved to http://creators.xna.com, including a wealth of tutorials and a revamped discussion area.

This weekend, I tried finally getting texture splatting to work for my Island War terrain renderer… and failed miserably :D. Look for yourself:

Screenshot of a height-mapped terrain with lighting and textures

There’s a lot of tuning to do until this crappy… something… looks like believable terrain. I’m not aiming for photorealism, but I’m not settling for a surreal landscape that stands out like a children’s painting would in an art gallery, either :)

Island War Day 1

Alright, my next game is finally on its way. The game’s working title will be “Island War”, which describes the setting of this game pretty well: small islands at war with each other.

And it won’t be like any other strategy title you might have played. I’m planning to remove the tediousness from the RTS genre by getting rid of micro management and unit placement.

I decided to try a different approach to the design of this game than I did with Ball Race. Instead of creating several GameComponents (like SceneGraph, EffectManager and GameStateManager) and spreading the game’s logic between them, I’ll try to model the game world in an object model designed for convenient use, so I can later set up my levels and launch the game with just a few lines of code.

Screenshot of a shaded height-mapped terrain without textures

The code so far incorporates an asset management system, the entire world expressed in an object model with load/save capability and can render dynamic height-mapped terrain allowing for real-time terrain deformation by explosions and other influences. I haven’t written the actual shaders yet, so this will look much better once I can get the shaders going.

CeGui#

If your game needs advanced GUI capabilities, CeGui# might just hit the nail on the head for you. Marketese aside, this is a seriously good GUI library with Buttons, ListBoxes, Scrollbars, ProgressBars, Sliders, ComboBoxes and more.

Screenshot of CEGUI# rendering its GUI into an XNA window

Being a port of the well known CeGui C++ library, it is not bound to a single graphics API but can instead be easily extended to run on a multitude of environments. Out of the box, it already provides extensions to be used with: XNA Framework 1.0, Managed DirectX 1.0, SDL.NET and Tao.OpenGL.

The only real problem for XNA developers might be that it does not yet work on the Xbox 360 due to several restrictions in the functionality of the .NET Compact Framework 2.0 that XNA applications have to build against on the Xbox 360.

Sexy Beach 3 ;-)

Just in case you have never heard of this game, Sexy Beach 3 is an adult title sold exclusively in Japan. In the game, you take the role of some random guy who gets invited for a holiday on “Sexy Island”, a small vacation island populated with a handful of other guests, which, by mere chance, are all good-looking women. You can probably see where this is heading to now… :D

Right, Sexy Beach 3 is basically just another sex simulation game, only that the Japanese are miles and miles ahead of the stuff churned out by western development studios. The game features beautiful anime girls, deforming clothing, real-time skin tanning and realistic boob physics. Yes, really.
Getting this game to install in Windows Vista is quite a headache, so I took the liberty to write down exactly what I did to make it work in a western Windows Vista system.

Read More

Ball Race – Day 14

Today it dawned upon me that I forgot something important in the geometry generation engine of my game: How can the player distinguish the goals from the traps? Both are holes, only that the former one makes you win the game while the latter one makes you lose the game. Oops! :)

After today’s changes, the maze consisted of three parts: The walls, the floor (with donut gaps around holes that are goals) and the goal rings. The goal rings fill the gaps left open in the floor and use a different effect that draws a checkered flag texture so the player can clearly recognize the goal holes.

Screenshot of several maze boards with holes, one hole in each marked by a checkered ring

All that’s left now is to polish the game a bit, add gamepad support and create the 10 challenge mode levels. Looking back at the progress, I have to say that I underestimated the amount of work required quite a bit. It’s great to see some interest from the XNA community, some people have linked me in their blogs and I even got interviewed about my game and my thoughts on XNA. More on that if everything works out as expected.

The release of “Project Balance” will be on December 11th the same day the XNA final is due.

Ball Race – Day 13

Finally got a new graphics card. I had seriously considered buying a GeForce 8800, but given the card’s insane price tag, the fact that I’m developing for XNA (nothing to gain from DirectX 10) and ATI’s recent announcement about their next generation GPU being out soon to lower the prices, I decided to go for a cheap ATI Radeon X1950 card.

Photo of a PowerColor Radeon X1950 and its box

I didn’t totally stop working on the game, however, and wrote a small menu system that I now use to display the game’s main menu and the level selector. Debugging could still be accomplished running the game in a 320×240 window by using the reference rasterizer for rendering, which produces about 1 frame in the time it takes you to wash your car, take a walk or phone a friend…

Aforementioned menu system is already being used to drive the main menu and a level selector, both fully working at the time of this writing. The buttons themselfes are looking rather dull and I’m not sure yet whether I should just try to do my best in Paint.NET or whether I should go looking for an artist…

Screenshot of several maze game boards and buttons to select between them

There will be 10 built-in levels that the player can try to beat in a certain time to complete the game. I think 10 levels are just right to entertain the player for a while and then let him off before the game gets boring. I truly think it’s a nice and fun game, but, after all, it’s just a ball rolling around on a table — hardly enough variety to make 100 levels worthwhile :)

Forced Break for Ball Race

This Monday, my graphics card decided that 18 months of service are more than enough and, well, quit. During bootup, it now displays utter garbage and as soon as windows loads the graphics driver, it hangs. The only good thing is that, as long as I run the generic VGA driver, my desktop displays fine.

I guess I should have taken the scratching noises that the card’s fan made for some months now more serious. The fan is still rotating, but probably not at full speed. Needless to say that this is quite a show stopper for my XNA development during this week, still hoping that the new card I ordered will be here before the weekend…

My 5 Reasons for Going Indie

Becoming an independent software developer is the dream of many people doing their daily 9-to-5 slavery. It is mine, too. However, you can’t just decide to do this step, quit your job and tomorrow you’re an independent developer.

If you decide to walk this path, you will first be forced to give up a lot of your precious free time by working on your own projects on the evenings and weekends in addition to your day job. You’ll have to do this for months or even years to come in order to build a portfolio of products that generate enough additional income so you can switch to only working your day job half-time.

That’s exactly the point I’m at now and I’ve got the feeling that, just like in a marathon race, there will be a time when you reach the thirty kilometer mark and you’ll ask yourself: “Why am I doing this?”. Then you need a good answer that keeps you going, one that gives you drive. My 5 reasons for becoming and indie, for going all the way, will be:

  • I want to set my own times. With a job, I cannot just decide to go out jogging on sunny days or when I feel like it. It’s depressing to get up while it’s dark, work the entire day and drive home in the dark again during the winter months.

  • I want to decide what I do, and why. In the corporate environment, you are assigned a task and then that’s what you’re going to do. Granted, I have quite some influence here in my current job, but I still have to help fulfill the company goal. It’s like driving in a bus: You are free to choose your seat, but you have to cope with other passengers and neither the route nor the time are under your control.

  • I want to be proud of what I produce. At least for me, things produced in the corporate environment never live up to my standards. There are other developers with other priorities that produce tons of uncommented, badly abstracted code all the time. I’m not free to choose whether I accept these people on my team or not. I have to live with them.

  • I want to become rich. You’re reading right. Call me a dreamer then, a heretic even, for thinking that I can become rich as an indie developer. But fact is, I do. One thing should be clear: You will not become rich as a corporate working slave. If you want to get the money, you need to be the one in control. Maybe I’ll have to turn my indie business into a startup game development company some day to achieve this goal. So be it. I will not stop there.

  • I want to be in control. Have a bad feeling about some concept and would rather put it aside to see how it develops before doing the grunt work? Forced to do crunch time but know for sure that the deadline is but an artificial one? It’s not about choosing the easy way out – it’s about who decides what to do!

Ball Race – Day 12

I have found a way to solve the ball-falling-into-hole simulation that I am quite happy with as it won’t let the ball sink into the solid parts of the floor and still looks convincing. As soon as the ball crosses a hole, I remember that hole and start the ball’s downward acceleration. While the ball is falling, I adjust its position towards the holes center as far as needed so it doesn’t intersect with the outline of the hole.

With the gameplay mechanics working well, I spent some more work implementing the actual logic. The gameplay controller now knows the game status and updates it accordingly when the time runs out, the ball falls into a wrong hole or into the exit hole.

Next component to implement was a simple game state management system. Originally I didn’t want to do this, but as I see it now, I would otherwise end up coding all the different states (main menu, level selector, ingame) into several big if or switch statements which would be a very awkward way to handle this.