Tag Archives: Beta Testing

Why This Game Is Taking So Long

Why is this wargame taking so long? The short answer is that I made a series of bad decisions. The longer answer involves explaining the bad decisions.

Before I began work on General Staff: Black Powder I had done a project for the US Army called MARS (Military Advanced Real-Time Simulator).

Image from the MARS: Military Advanced Real-Time Simulator feasibility report to the US Army. Screen shot of MARS.

I had used a Microsoft IDE (Integrated Development Environment) called XNA to write MARS in C# and I thought it would be a good environment in which to develop General Staff. XNA, on top of being fairly easy to implement a 3D or 2D game environment, had another interesting advantage: any program created with it was immediately portable to the XBox game console. This dovetailed nicely with my dream of someday bringing wargaming to a larger (and younger) audience.

Consequently, the first version of General Staff – including the Army Editor, Map Editor and Scenario Editor – was written using XNA. I had just begun working on the actual game itself when Microsoft suddenly announced that it was no longer supporting XNA. This, of course, sent shock waves through the XNA game development community.

Since I had already written a great deal of the necessary code in C#, and Windows remained my target audience (Windows makes up >90% of the gaming market) I decided to port (that’s a game development word for rewrite for another environment, but hopefully not rewrite everything) to Microsoft Windows Presentation Foundation (WPF).

I wasn’t thrilled about porting to WPF. First of all, I wasn’t that familiar with it and, secondly, it wasn’t easy (at least for me) to do a lot of the things that needed to be done. The Army Editor was a pretty easy port, but the Map Editor had some very specific, difficult problems having to do with drawing on the screen. Luckily, I found Andy O’Neill, who is a certified expert on WPF. Andy took over and decided to rewrite my code (properly for WPF) and, eventually, the Army Editor, Map Editor and Scenario Editors were completed. If you are an early backer of General Staff: Black Powder you should have these. They are also available for download on Steam.

By this point the General Staff: Black Powder suite of editors had now been rewritten three times for two different environments, but, it was finally completed and in a stable version. I have been using these programs to create numerous scenarios (some of which are already uploaded to Steam).

The Quatre Bras scenario in the General Staff: Black Powder Scenario Editor. Screen shot. Click to enlarge.

The last thing to do to complete General Staff: Black Powder was the actual game, or game engine. Usually, this isn’t too hard because about 80% of the code is recycled from the Army, Map and Scenario editors. Unfortunately, I just wasn’t happy with the how the game looked in WPF. WPF is great for creating business apps but it just wasn’t giving me the 19th century Victorian look and feel that I wanted. About this time I discovered that a number of former XNA users had banded together to maintain and expand the original IDE; it was now called MonoGame. I decided to write the General Staff: Black Powder game engine in MonoGame.

I was making pretty good progress, but ran into some problems and asked the MonoGame community for help (by the way, I’ve found the MonoGame community to be a great group for answering newbie questions and generously providing time and solutions). It was on the MonoGame community forum that I met Matthew T. who is an experienced XNA/MonoGame game developer (he has a game on Steam that has sold over 100,000 copies). Matthew, eventually, decided to rewrite large hunks of my MonoGame code (vastly improving it) and then began to add some wonderful debugging features.

Screen shot of Ligny scenario in General Staff: Black Powder debugger mode. Click to enlarge.

Matthew and Darin Jones also implemented Steam player versus player (PvP) and we’ve done some early playtesting with Matthew in the UK and me in the US playing against each other in real-time (this was an amazing experience and something that I never envisioned that we could pull off).

So, that’s where we are now. We’ve made great progress and we’ve taken far longer to do it than I had hoped or anticipated. A lot of the same code has been written and rewritten for different environments. With 20/20 hindsight I certainly could have managed this a lot better. I think we’re about two months away from a pre-release beta starting with PvP playtesting. This would involve all the early backers who would get new Steam keys.

As always, please feel free to contact me directly with any questions or comments

 

Map Editor Released for Beta-Testing!

We are very pleased to report that the General Staff Black Powder Map Editor has been released into beta-test. This program allows the user to easily create maps for use as a battlefield in the General Staff Wargaming System as shown in this demo:

Important Note: If you were an early backer of the General Staff Wargaming System via Kickstarter or Indiegogo, you should have received an email update informing you of this, the beta test download page and password. If you did not, please contact me directly. Also, a few people became beta testers after the Kickstarter and Indiegogo campaigns. You should have received an email from me with the URL for the download page and password. If you did not, please contact me directly.

Map Editor Documentation Now Available Online!

Screen capture of the Map Editor (working on the battle of Little Bighorn). Click to enlarge.

We are extremely pleased to report that the documentation for the General Staff Map Editor has been completed and is now available online at Famdom (link: https://general-staff-wargaming-system.wikia.com/wiki/The_General_Staff_Black_Powder_Map_Editor). There is also a link from the Map Editor itself to the online documentation (under the Help menu). This, of course, means that the Map Editor will be released for beta-testing in the next day or two.

During the course of my professional career I have worked on numerous programs that create or facilitate the drawing of maps for wargaming and military simulations. These include my own UMS, UMS II, the War College and TIGER / MATE (created for DARPA) as well as an extremely largeĀ  US Army Military simulation with a budget of over a billion dollars.

Creating easy to use military topographical map programs is not a trivial undertaking. Dr. Ken Forbus, and his group at Northwestern, worked for years on the NuSketch project (link here and here).

I believe that the General Staff Map Editor utility is the best program of its type commercially available and, in fact, is superior in ease of use to the billion dollar equivalent. The Map Editor supports digitizing tablet and pen as well as two-button mouse with scroll wheel. Andy O’Neill (see here) did a remarkable job coding the Map Editor.

In essence, the Map Editor is a 3D paint program that allows the user to draw terrain, topography and elevation. The maps are then used in the General Staff Wargaming System and can be printed out for your own use.

If you were an early backer of the General Staff Wargaming System (Kickstarter and Indiegogo) you will be receiving an email shortly to go to the ‘secret beta-test site’ and download the installer for the Map Editor.

Any questions or comments? Please feel to contact me directly.

 

 

Army Design Module Is Out of Beta Test!

We are extremely pleased to report that the General Staff Army Design Module has now completed Beta Test and we are moving on to sending out the Map Design Module to our valiant Beta Testers!

Screen capture of the Army Design Module showing the built-in Help documentation. Click to enlarge.

The Army Design Module allows users to easily create new army Order of Battle Tables that, when combined with a map and another army, become battle scenarios that can be played in the General Staff Wargaming System.