The end is nigh?

Battlestar Galactica
Dave added himself to the recently familiar turnout, making us 5 for Sunday's games. Donald had first choice and he plumped for Battlestar Galactica. I was pleased with this choice despite the anti-climax of our last play. The imminent expansion I wrote about back in June was part of the reason for this: I want to have played the basic set often enough to have gone well beyond first impressions when I get a taste of how the expansion changes the game.

Preliminary testing
Sitting down Monday morning to get to work on the write-up, I decided on pictures of the key cards which'd been part of the Cylons' final onslaught. I set to work with the scanner. The first scan- fullsize at left, was terrible: the pictures were too small and the resolution was terrible. I briefly considered just using them but, remembering recent testing of the ideal setting for scanning miniatures, I decided instead to run a quick settings test. (No prizes to the readers who notice the smidgin of irony here, but cheerful greetings for sure to those who might wish to register their groans at my lame attempt at humour!)

Scantests

You can see above the range of tests (from the left):

• Illustration doctype on screen/web setting.
• Ditto @300dpi.
• Photo doctype @300dpi.
• Magazine doctype @300dpi.

The resolution of the photo doctype scans were good, but the image above shows the problem: the scan automatically cropped the image inconveniently. The magazine doctype proved ideal in the end, which should be hardly surprising I guess: these are full-colour printed images exactly like those in magazines.

What went down
Humanity's last chance on Sunday then rested in the hands of 5 'people':

• Starbuck: Gav, who sought the simplicity of the fighter jock's role- just fly around and shoot things.
• William Adama: Andy, for whom a nuclear arsenal was compensation for the burdens of command.
• Chief Galen Tyrol: Dave, eschewing the complexities of politics in favour of honest sweat and toil.
• Laura Roslin: Donald, because someone has to be President, I guess.
• Helo: me, just looking for something different.

I got that something different immediately: my first experience as an at-start Cylon. For some reason I was marked down from the get-go. At the time I imagined this was sheer arbitrariness based on Helo's Stranded special rule. With hindsight I'm not so sure because, unlike my first game as a Cylon, I fluffed the moment when I looked at my card. I can still remember quietly cursing myself as I over-hastily put down the card only to realise that I'd not even read it properly, and that I dared not pick it up to find out exactly what would happen when I decided to reveal my true colours.

All our best efforts...

My play didn't improve much after this bad start but I'm certainly not going to comment on that in detail because I've no intention of passing on tips that could be used against me by either side in a future game. Sufficeth to say that the humans must've had their god on their side, because they were very lucky in several ways:

• They reached the jump-4 midpoint of their route to Kobol in a mere 2 jumps IIRC.
• Their first jump thereafter was a Cylon Ambush; which may have launched a Cylon attack, but it was a jump 3 which put them just 2 jumps out from home.
• Gav was able to use Starbuck's Secret Destiny to avoid a Cylon Swarm just after they'd made that penultimate jump.

These twists of fate notwithstanding our Cylon god certainly hasn't lost the war: the Centurions landed aboard the Galactica by my Cylon Intruders Super Crisis card might not've been as Donald's Bomb on Colonial 1, but the resource dials were still dangerously low as the humans made their final jump preparations:

• Fuel: 3.
• Food: 2.
• Morale: 1.
• Population: 6.

The pace of the humans' jump preparations told against the Cylons again: Donald's and my options were restricted in those final turns because drawing Crisis cards to attack resources or mobilise the Centurions threatened simultaneously to bring those jump preparations to completion; an eventually we figured was favoured by the odds. Perhaps we should've played aggressively for our own blind luck of the draw, because soon enough our only hope was to buck much worse odds as Dave drew for the Skill card to repair the FTL controls, damage to which was the last thing preventing the last jump out. They made it, naturally enough.

Score
Blind faith and dogma? 1
The appliance of science? 0
:-[

Afterthoughts
This game was more eventful than the last, with a close finish, but we were still left unsatisfied. I think there are 2 possibilities here:

• The potentialities of the procedural gameplay are as limited as I had originally feared because of my experience of Arkham Horror, so that the game has already become stereotyped and dull.
• We simply aren't playing it right; that is to say, we aren't investing enough in our tabletalk as we play, so that experiencing the limitations of bare procedural play in a game of this ilk.

I like the BSG boardgame enough that I hope we can revive our interest by bringing more to the table the next time we play. That game of Gloom Gav and Badger and I played with Keith Baker during his recent visit taught me exactly how much difference you can make with speech play for the simple sake of entering into the spirit of a game. So I'm optimistic I guess.

Settlers of Catan
One good quality of BSG is that it is pretty quick to play, so we had time for something more than just filler to follow. Regular readers will be unsurprised to read that Settlers appeared on the table yet again. The 5/6 player game's expanded map soon appeared, and we were off.

The setup

I was red, and my setup left me feeling uncomfortable as the game began:

• With only 4 different numbers out of 6, I was in a position similar to that from which I'd suffered last month.
• I had no grain, and soon lost all hope of gaining access to it.

A combination of luck and judgement meant that was I feeling better soon enough:

• My first settlement was a 3:1 port.
• I finally remembered to build that quick first city.
• A series of foruitous dice rolls let me build a couple of quick roads and a settlement so that I became a potential ore magnate.

The final position

Unfortunately the 10's from which I'd reaped such rich rewards weren't seen again and I stalled on 7 as Gav (white) and I sought to stop Donald's (orange) advance to victory. We couldn't.

Score
Devious Donald 1Happy humans? 1
Sore loser? 0
X[

Fluxx
We rounded the session off with a few hands of Looney Labs' Fluxx. Dave was new to the game so Gav and I sang its praises to him. One feature we stressed was how tight the rules are. Ironically enough then, one of our games featured a first: a situation in which the interaction of 2 cards was more than not immediately obvious; it even remained open to question after we'd decided what we were going to do.

The 2 cards were:

• Action, Draw 3, play 2 of them.
• New rule, Inflation: X=X+1, where X is any numeral.

The question arose because the action was played, then the new rule; did the Inflation apply to the action? Unable to rule based on the cards' text, we decided to play that it did.

I'm sure that we got it right. The burden of our confusion was that the action had already been played, so we assumed the Inflation was being applied retroactively. The precise wording on the right- first paragraph, corrects our mistake: not discarded until its instructions are completed, the action card was still in play when the new rule was played.

Score
Andy 1
Donald 3
Dave 3
Gav 2
Me 1
:-/
;)

Related@RD/KA!
Battlestar Galactica boardgame:
- My 2009 gaming wishlist #2
- Done down by dastardly Donald's devious duplicity!
- The fickle finger of fate
- Toasters, toasters, everywhere!
- A moment to marvel at...
- What price survival?
- Again, the toasters' offensive

WTF?! WFRP3... & FTW?

An otherwise fruitless trip last week to the big F in Glasgow's FLGS- Static Games, netted me some news which frankly had my mind reeling in horror and tooling me up to join an internet mob of torch-and-pitchfork-wielding heresy hunters. I refer of course, to FFG's announcement on August 12th of the impending Warhammer Fantasy Roleplay 3rd Edition (all rumour of which had completely passed me by). My entire vocabulary of superlatives distilled into ichor would barely summon the merest whiff of my rage, instinctive and despairing, at another oh so typical corporate betrayal in the face of which I was already brewing vituperation and vitriol (all sight unseen, naturally enough).

Kenny, Static's proprietor was pretty astonished himself. Telling me of reports from the FFG WFRP3 seminar at Gencon, he explained that this was going to be a completely new system. What? Why? What was wrong with WFRP2 (except that it wasn't FFG's own product, naturally enough)? We both agreed easily that WFRP2 was an exemplar of how to do a new edition well, and that it had been successful and popular. We discussed the issue at length and I left, none the wiser but determined to remain true to the prejudices awakened by my spasm of geek rage.

The original combat commander

Introduction
Regular readers might remember that the book Infantry Attacks, by the legendary Erwin Rommel, was part of my booty from UK Expo'09. I've finally got round to reading it, finishing it during my journey home from London.

Infantry Attacks (Infanterie greift an) was first published in 1937. It was this book which first brought Rommel to the attention of Adolf Hitler, a fateful moment which was ultimately to prove fatal to Rommel. It was translated into English in 1944 for the US army, one result of which was Patton's memorable remark:

"Rommel, you magnificent bastard! I read your book!"

Between the covers
The book details the actions Rommel participated in during WW1. He fought as a junior field officer on many fronts:

• Belgium and N. France, 1914: 6th Württemberg Infantry Regiment- the unit in which Rommel was a platoon commander, was part of the German 5th Army under Crown Prince Wilhelm of Germany; 5th Army was part of the Schlieffen plan's 'hinge'; these operations included a crossing of the Meuse river which Rommel famously crossed again with his 7th Panzer Division in 1940, at Dinant some 100km north of his 1914 field of operations. (BTW: I know I misspelt 'Schlieffen' on the map's labels!)

• The Argonne, 1915: a forested region just east of Verdun (you can see its location on the small map- above), the Argonne was where Rommel got his main taste of the trench warfare that was infamously to dominate the Western Front for the next 4 years; the picture- above left, is from the aftermath of the heavy fighting in the Argonne, and shows what has since become an archetypal image of the unprecedented destruction wrought by the massed artillery bombardments of WW1.

• The High Vosges, 1916: in October 1915 Rommel was posted to the Württemberg Mountain Battalion with which he served for the rest of the war; after long training the battalion went into the line in the Higher Vosges- a range of mountains in France close to the Franco-German border.

• Rumania, 1916: Rumania entered the war on the Allied side on August 27th 1916; as a result Rommel's Württemberg Mountain Battalion was transferred to Transylvania (in German: Siebenbürgen); there the battalion took part in several successful mountain attacks.

• Carpathians, 1917: the Württemberg Mountain Battalion was again transferred, to be part of a summer offensive to close down the Russian front after the revolution of February 1917; although still a junior officer, Rommel played a significant role in two weeks' heavy fighting to take and hold Mount Cosna.

• Carinthia, 1917: Rommel's last operation as a field commander in WW1 was the 12th Battle of Isonzo- better known as the Battle of Caporetto, and referred to by Rommel as the Tolmein offensive, for the town near the Württemberg Mountain Battalion's assembly area (this can be seen as 'Tolmino' on the map- above right); the offensive was a huge success for the Central Powers, and a complete vindication of the new stormtrooper and infiltration tactics which Germany had developed.

In each chapter Rommel details his orders; describes the dispositions of his forces and the terrain across which they would be fighting; details and explains the resulting plans; and gives an account of how the action developed and how he responded to events. These technical details are filled out with some anecdotes from the fighting and from frontline life. Most chapters conclude with "Observations", in which Rommel draws conclusions about what happened and why.

There are illustrations in addition to the text. These are not the photographs so familiar from many campaign histories. They are are sketches and maps of the battlefield, of a style which makes them look like they were drawn by Rommel himself. This impression is strengthened by the fact that many of the illustrations aren't maps; rather they are views of the battlefield from vantage points I can only assume Rommel actually occupied at the time.

And?
I must confess that I was a little disappointed with this book at first. It is extremely dry, written in a very curt style which provides little more than the barest account of the matters Rommel covers. This wasn't helped for me by the nationalistic tone of the book: to read Rommel in Nazi Germany singing the praises of German soldiery in what I knew was going to be an account of his role in the slaughter of WW1; a book written as a careerist manoeuvre as he sought advancement for the sake of playing a bigger part in the war he must already've seen on the horizon; well, let me just say that didn't capture my enthusiasm.

Soon enough though the book began to grow on me. The first thing that came to my attention were hints of the character of the man well-known from his exploits in the Western Desert in WW2; namely his penchant for getting into the thick of the action and so losing sight of the overall picture. Something for which he has sometimes been criticised, this was no doubt more forgivable in a junior field officer in any case.

My interest was further piqued by the commonplace references to 'squads'. I've long believed that platoons were the basic low-level tactical units on the WW1 battlefield, and that squads didn't come to fill that role until 1918. Rommel contradicts this with references to squads being given mission objectives essentially from the very start. Wikipedia's coverage of the development of infantry tactics in WW1 breaks the subject down into:

• Stormtroopers: a formation first devised by the Germans in 1915 and first used on a large scale by the Russians (this surprised me: the Russians in WW1 are generally known for their infantry tactics the same way that the British were known for tank design in WW2; ie. not at all!) in 1916.
• Infiltration tactics (or Hutier tactics, for Oskar von Hutier, the German general who devised them).

It is worth noting that neither of these have anything to say about the move to squad-based tactics as such, although a key feature distinguishing infiltration tactics from what had gone before was the use of smaller units.

In any event, once this issue had got me to consider the book more favourably, I soon realised that I had been labouring under the impact of false expectations. I'd unwittingly been expecting a frontline commander's version of a campaign history of the sort I've read so often. Infantry Actions is a very different book. Instead of the campaign overview with telling details and vivid anecdotes to fill out an account of all levels of the action, it is a field commander's account of how he went about the business of commanding his forces in battle.

What Rommel typically gives us therefore is something like this:

• We marched all day, bivouaced late and ate little.
• Orders came through in the dead of night and we set off.
• Reaching our objective we (I) conducted reconnaisance to determine:

1. A breakthrough point for the assault units.
2. Positions for the fire support units.
3. Avenues of approach.

• A plan was formulated, eg.:

1. 1st platoon would be the assault force.
2. A company on the left, and B company with 3rd and 4th HMG platoons on the right would provide fire support.
3. D company plus 5th HMG platoon would be in reserve.

• Orders were given, my units moved into position, and the action began.
• As the action developed:

1. The fire support plan pinned the enemy as expected, the assault forces broke into the enemy position, and I ordered a platoon from D company forward to exploit the breakthrough.
2. A company was pinned down by heavy fire and strong enemy forces appeared, threatening to turn our left flank, so I ordered another platoon from D company plus the 5th HMG platoon up to hold the line.
3. The initial breakthrough secured, I ordered 2 platoons of B company plus 3rd HMG platoon to consolidate on the assault platoon to prepare for further exploitation.

• And so on and so on until the action was concluded.

This isn't an actual example. It's just to give a flavour of Rommel's treatment of his subject matter; namely a technical account of his role in his units' exploits. The book is chock full of this sort of stuff, all written in the professional soldier's clipped jargon to boot. When Rommel does break out of this vein to bring in anecdotes, they are often about the fate of crucial or particularly popular NCO's and officers, or about the situations in which he found himself as he made his way about the battlefield.

Sometimes Rommel is in the thick of the action; other times he is talking about the sound of gunfire and the conduct of squads, platoons or companies from the perspective of a company or a battalion commander who often can't see these units. In all cases he is talking about the tactical situation; the demands it placed on himself and his men; how he organised, commanded and led his men to meet those demands; and whether or not it looked as if those demands could be met in pursuit of the objectives which had to be gained in fulfilment of his orders.

In other words: precisely because it is dry compared to the more familiar campaign histories, Rommel succeeds admirably in putting the reader neatly inside the head of a field officer in command of his units during intense action. Therefore this is a very good book indeed for anyone who has any interest at all in that subject matter. The breakdown of its parts also makes it ideal for dipping into, to read about this or that action. So it's no surprise that Infantry Attacks was recommended reading in the US military for several decades. I expect I'll read it again myself. ;)

Heavy metal highlights

I was down in London for a family wedding last weekend. I had some time on my hands before my return journey on the Monday, so I hooked up with a friend and we paid a visit to the Imperial War Museum. I've only been to the IWM once before, many years ago. I had less time on that visit than the couple of hours at my disposal on Monday and I didn't have a digital camera then either, naturally enough. Here are a few of the pictures from that Monday afternoon.

Me with the famous 15" naval guns in the background

Panzerjäger V Jadgpanther

The information panel at the IWM and the wiki article both note that "many military historians consider the Jagdpanther to be the best tank destroyer" of WW2. This is an opinion I share:

• Its 88mm L/71 main armament was simply the best gun in its class in the entire war, able to destroy any Allied tank at any range (L/71 means that the gun barrel is 71 calibre lengths long, ie. 71x88mm= ~6.25m; the longer a gun in calibre lengths the greater the muzzle velocity its shells achieve; the greater the muzzle velocity of solid AP shot the greater its penetration).
• The thick and well-sloped armour gave the Jagdpanther one of the best defence profiles of any AFV to see action.
• It was also fast, with good cross country performance.

The Jagdtiger was better armoured and had a more powerful gun, but was far less mobile and therefore easier to deal with; and the Tiger is more famous, naturally enough. Still, I would have to say that an encounter with a Jagdpanther would probably've offered the worst chance of survival for Allied tankers, especially in the infamously vulnerable tanks of the Anglo-American armoured divisions in Normandy and beyond during 1944-45.

Given all that, just imagine the bollock-shrinking fear of the Cromwell crew in Normandy whose tank came out from behind cover to find this very specimen right in front of them. Imagine too their sheer relief when their puny OQF 75mm scored several quick penetrations in the weaker side armour- picture above left, to put the Jagdpanther out of action.

Readers the slightest bit familiar with modern ground warfare will know that AFV's are disadvantaged in urban settings because buildings constrain their movement and their fire arcs. AFV's with fixed mount weapons, like the Jagdpanther, are even more hampered because they have no rotating turret. A few shots taken from the 1st floor balcony should give you some sense of this.

Above right you can see a couple of views that any bazooka man or PIAT gunner would've wanted to see: high flank shots with the vehicle's vulnerable rear-decking exposed to fire. Infantry support or sheer dumb luck would be the Jagdpanther's only hope in a situation like this. The picture above left shows though that simple height advantage wouldn't always work. Here a quick pivot is all that would be needed to bring the Jagdpanther's main armament to bear. In this case the poor bloody infantry would've been praying for divine intervention.

Assorted pictures

Daimler armoured car

The British army was apparently much better at making armoured cars in WW2 than it was at making tanks, as exemplified both by the general high opinion of the Daimler armoured car, and by the fact that it outlived its own replacement. Phrases like "it incorporated some of the most advanced design concepts of the time" are simply not commonly associated with British AFV's of the period. I suspect that this might have something to do with the usefulness of armoured cars in colonial policing, which would've given the British army experience of armoured car deployment which could've served to prevent development of these AFV's being stymied by spurious doctrines as was the case with the tank.

Matilda II infantry tank

The Matilda II was a prime example of those spurious doctrines in action. It was an 'infantry tank', ie. a tank whose purpose was to support the infantry, hence eg. it was very slow because it wasn't expected to travel much faster than infantry's walking speed. Yet its main armament- a 40mm gun, wasn't provided with HE, so that the tank couldn't actually effectively support infantry in their main role, namely assaulting enemy infantry to seize ground. Thus it was essentially designed to support infantry against tank attacks, a role which wasn't part of the very doctrine which produced the Matilda itself. With thinking like this behind tank procurement it is hardly surprising that Germany's blitzkrieg of the early war years mesmerised its opponents.

Sherman tank

Ubiquitous and reliable, the US M4 Sherman was the mainstay of Allied armoured forces from 1943 onwards. No match for the superior Panther and Tiger tanks, it was also outclassed by its German opposite number, the Panzer IV.

T34/85 tank

Widely regarded to be the best tank of WW2 (though not by yours truly who reserves that accolade for the Panther), the T34 was probably the most influential design of the period, and certainly the most numerous production tank of the war. Unlike the Matilda, the T34 was able to be upgraded, an 85mm gun replacing its original 76mm main armament in 1944.

25 pounder

Field artillery was another area in which British designs excelled, the 25pdr being perhaps the most famous field gun of WW2. Anglo-American fire control was very advanced and well-trained crews using the 25pdr could bring down a truly astonishing weight of fire. The story goes that captured Germans in Normandy in 1944 asked to see the 'belt-fed field guns' so great was the pounding to which they had been subjected.

That's it for the selection of pictures from my recent visit to the IWM. I'm sure I'll be back, and that it'll be somewhat sooner than the 20-odd years since my last visit. Fingers crossed I guess. ;)

Fighting Formations preview #2: The frakkin' game!

(A quick note: this post was supposed to go up soon after the first part, posted a fortnight ago. Unfortunately the CSW website crashed for more than a week so that I couldn't get the information I needed to complete the article, hence the long delay.)

**********

Fighting Formations went live on the GMT P500 at the end of June. It crossed the 500 preorders line in mid-August (17th AFAIK), meaning that will go into production. An xmas release is possible although I'm not holding my breath on that score to be honest: it's just a bit too much to hope for.

Opening FF@CSW last November, Chad announced:

I'll begin by answering the obvious question first: "No, this is not Combat Commander with tanks."

The most obvious difference was made clear immediately: FF is not card-driven. This should've been obvious to fans of CC who've followed Chad's oft rehearsed explanations of why the inclusion of tanks would quickly overload and crash the CC card engine.

It's for real; it's big; and it's incoming!

The GW company blog yesterday confirmed the rumours that've been floating round the net for some 6 months now: there is to be a new edition of the classic boardgame Space Hulk; and it will be about as spectacular as some were predicting. That this much is true can be seen from the pictures below, which I culled from the GW site. First, a look at the promotional video clip.


Next, a selection of the pictures (you'll find the rest on GW's site, naturally enough).

The box and its contents

The game will be released on September 5th, in what GW is calling "strictly limited numbers". I confess find myself wondering how GW might choose to define the term "strictly limited", if only for the simple reason that I can easily imagine a print run of several tens of thousands selling out via internet preorders in the scant 3 weeks before the new Space Hulk 'hits the shelves' (I preordered 2 myself thanks to Andy's kind offices; I know from the B&C that I'm not the only person in Glasgow to do so; and I'd even think about turning up and queueing on the day to get a 3rd set- yep, it's one of those games dear readers!).

In any event, months of rumour and anticipation coupled with some last minute stoking of the fires with talk of a 40K 'mystery box' means that however large a print run GW have prepared (and the company must've figured on having at least a day or two's stock available for their stores and their distribution chain, surely?), it will sell out in no time at all as fans old and new clamber over each other to get their hands on copies. Assuming this is what happens, will we I wonder see GW resort to this marketing strategy again?

Meanwhile, what about the contents of the box? I won't repeat the list of goodies which you can find on GW's site. Sufficeth to say that 40K fans are only too aware that the samples here are very high quality pieces even by GW's standards. The posing on that Terminator is extremely dynamic and I imagine modellers the world over will be setting to work in the weeks and months to come to make their regular Terminator minis look similiar. This all looks very promising.

Key questions right now for this ardent fan of the previous editions are:

• Will the board pieces be backward compatible with those from the previous editions? There is no reason why they shouldn't be, but you don't have to have been a GW customer all that long to be only too familiar with the built-in obsolescence at the heart of their marketing model. I guess we just have to hope that the design team will have proved every bit as keen to expand on their own existing Space Hulk layouts as are the rest of us.
• What will the heavy flamer rules be like with the obvious return to the larger flame templates as used in 1st edition? I confess I'll need something special to persuade me that these rules will be better than the 2nd edition flamer rules, which were one of the better features of the new edition.
• How will the extra wargear and characters work? There'll always be the option, as with the flamer rules, of returning to older rules or bringing using homebrews, but your silver tongue might fail you in the face of opponents who prefer the current official version.

But this is mere speculation right now. All these and other mysteries will be revealed very soon. ;)

Addendum, 19/08/09
One of Andy's comments referred to more pictures over at the Warseer forum. For those who are interested, they can be found here. It's also worth keeping a regular check on GW's Space Hulk product page, because it's being updated daily with new pictures until the end of this week.

Related @RD/KA!
- Part 1. In the beginning was the hulk
- Part 2. The timer rule and player point-of-view
- Part 3. Tactics, tactics, tactics!

Happy birthday to RD/KA!

Four years and counting
Today is RD/KA!'s 4th birthday. My gaming blog began life on Saturday 13th August 2005 with the first of a series of reports on the 63rd Worldcon. In those 4 years 350 posts have covered games, comics, movies, books, food, and sundry other topics of interest to gamers; but as the 'Labels' list at the bottom of the page shows, writing about the games I've played has been staple fare. There have been highs and lows as regular readers will know, but you can be sure of one thing: as long as I'm playing games, I'll have something to say about them. Onwards and upwards! :-)

Another Sunday session
We were the four for Sunday games we'd been the last time. Gav was keen for more Risk and Andy was hankering after a game of Roborally, which I fancied too. So that made a plan.

Roborally

Designed by Richard Garfield of Magic: the Gathering fame, and first published by Garfield Games in 1994, Roborally was published in a new edition by Hasbro/Avalon Hill in 2005. I own the original edition and 3 out of 4 of its expansion sets. I've not had a chance to look over the new edition in detail, but I confess I don't like the look of it too much. Or, to be more precise: there are 2 features of the new edition I don't much like the look of.

The first of these is the replacement of the original virtual bots- ie. counters representing each bot, with the docking bay. Virtual bots are a solution to the impossibility of stacking the bot miniatures when the situation demands 2 or more bots occupy the same square, eg. at the start. I'll freely grant that the new rules might be simpler than the originals, but I'm not sure they're more fun. That is to say: I'd like to think there is an extra layer of potential chaos offered by the old virtual bot rules.

One amusing example I can remember involved a bot, a virtual bot and a proximity mine. The 2 bots were adjacent to each other and the real bot dropped a proximity mine. The question arose: would the virtual bot set off the proximity mine? We perused the rules:

• Virtual bots don't interact at all with other bots, virtual or otherwise; they interact normally with everything else.
• Dropped/launched devices are active as soon as they are dropped except to the bot that set them, which has until the end of that register phase to move away.

And so the proximity mine went off under the bot which had dropped it!

The other feature of the new game I'm not keen on is the timer: a 30 second timer is set when the penultimate player has finished programing their bot. I have stoutly resisted suggestions to use time turns in Roborally for years; I'm hardly going to applaud when a new edition makes their use official.

For Sunday's game I canvassed for a board a lot simpler than that we had raced across the last time we played. Winning assent I chose a layout which was fairly open and which used simple board elements, but on which there were still enough different elements for maximum entertainment value. The result was the layout below.

Back Stretch and Pit Row

I cleverly neglected to record the flag locations; but I can remember the start and the 1st flag, because Twonky reached those 2 locations.

The game was entertaining as ever. Highlights among the hijinks were:

• Donald lost his life on the first turn.
• Gav was the first to reach a flag.
• Gav's bot remained virtual for an unprecedented 4 turns.

Most entertaining perhaps were Donald and Andy's encounters with an express conveyor belt. Donald arrived there first. Calculating his move, he figured that he was doomed:

• From the start point (X marks the spot) they were unable to get off the belt.
• Whichever card they played then, the conveyor was going to move them to the edge of the board.
• Once there, they faced 3 equally destructive choices:

1. Let the belt carry them off the edge of the board.
2. Move onto the pit.
3. Move onto the oil slick, from where they would slide across to the conveyor, which would carry them off the edge of the board.

Fortunately for Donald, it turned out that he had an option which could save him: Overload Override which allowed him to rotate and move in the same register phase, thus handily escaping the express conveyor before it carried him to his doom. Andy wasn't so fortunate.

The final insult for Andy was that it was Donald's fault that Andy's bot had ended up on the conveyor in the first place. Andy had picked up the Robocopter option. He had finally decided to use it and his bot began to move at a fair clip. Then he was lasered by Donald: his Robocopter was shot off: and his bot was dumped back on the factory floor. His curses were colourful.

Gav was making solid progress while all these hijinks were going on. He won the game with a solid lead:

• Gav: 4 flags.
• Andy: 2 flags.
• Me: 1 flag.
• Donald: 0 flags.

Score
C++ CPU: 1
COBOL CPU's: 0
:-(

Afterthoughts
I really like Roborally, and this game was no exception. I'd like to play more often, to which end I think we'd have to consider how to stage the game as filler. The key to this is single board layouts, and choosing the right number of flags according to the difficulty of the board.

Risk

With time still at our disposal we turned to Risk as Gav had requested. With hindsight Gav might be regretting this because he was the number victim of circumstance in our game: he was playing yellow; eliminating all yellow armies was my mission; so Gav was the consistent target of my unrelenting attacks.

Missions

• Andy: occupy Asia and S. America.
• Donald: occupy Australasia, Europe, and 1 other continent.
• Gav: eliminate all red armies (Andy).
• Me: eliminate all yellow armies (Gav).

The turn order didn't favour Gav because his turn was after mine. I was able to pick 3 or 4 lone yellow armies with some opportunistic attacks in my first turn. After that I quickly took S. America, which gave me a solid base which was never seriously challenged. Nobody had paid any attention to N. America during setup and it was left untouched until the endgame, so I was able to leave a minor frontier force to secure the South and turn my attention to Africa. This too soon fell to my green hordes.

Meanwhile, Andy was trying to secure Asia. Unfortunately for him his efforts were constantly foiled by Donald's and my attacks from Australasia and Africa respectively; neither of us were keen to see 7 armies/turn appear on our borders.

Elsewhere, Gav finally bit the bullet and launched an attack against my strong Icelandic outpost. No one could understand why I was holding Iceland in such strength. The answer was simple: Gav had territories nearby and I was massing for an attack. Gav pre-empted me and broke through Iceland into the virgin lands of N. America, from where he later fought his way through into central Asia in an effort to put as much distance as possible between his armies and mine.

By this time my position was largely unassailable. I was eventually able to seize N. America with the help of a timely set of Risk cards. My mission long since evident to all, Andy tried to stave off my increasingly inevitable victory by finishing Gav off himself. This failed. I won the game next turn, cashing in another set of Risk cards to amass a huge army which I promptly sent through Kamchatka to finish off the handful of yellow units still on the board.

Final position

• Andy: 9 territories (all in Asia).
• Donald: 11 territories (Australasia and Europe).
• Gav: -
• Me: 22 territories (Africa, S. America, N. America, Kamchatka and Japan).

Score
Puny microprocessor 1
Glorious world conqueror 1
Grunts still counting on their fingers 0
:-)

Afterthoughts
I think I was well served by my mission which, barring lucky setups, I feel is a bit easier than one which involves controlling continents. This is because:

• The mission isn't geographically defined so that it is less susceptible to bad setups.
• Other players's attacks on the player you must eliminate contribute directly to your victory.

It'll take a few more games with these missions in play before I can be sure. ;)

Back to the beastly badger baiting!

Memoir'44

Badger's visit for gaming last night saw me still in the mood for light relief so we again eschewed Combat Commander. Left to choose, Badger opted for our old favourite, Memoir'44. We considered playing an Overlord game but we were starting late and Badger wanted to be sure we'd play more than one game. So we decided to start with the first scenario from the Air Pack, and to proceed from there.


Yellow Beach
The first scenario took us to France in August 1942 for the ill-fated Operation Jubilee, the experimental amphibious assault on Dieppe. Operation Jubilee is best known for the heavy casualties suffered by the 2nd Canadian Infantry Division in the main assault: a frontal attack on the port itself. The Yellow Beach scenario covers one of the flanking attacks made by British commandos.

The long road back to the painting table

Gearing up and clearing the decks

It's been three months since I wrote about returning to the miniatures hobby I'd put aside a few years ago. I still haven't picked up a paintbrush in anger in those weeks, but I'm getting close. In the meantime I had to empty a large walk-in cupboard to clear the space to reestablish my painting table. Although everything's packed away again so that I finally have a functional workspace I'm going to have to unpack and reorganise everything again at least once before I'm satisfied.

For the sake of the bloggery I've invested in the finishing touches to my layout for miniatures photography:

• A nifty wee tabletop tripod.
• A quality PVC backdrop.
• And a pair of cheap halogen spots; I'd've thought these would give bad light, but the guy in the camera shop where I bought the backdrop pointed out that digital image manipulation makes it easy to correct the light.

The picture at the top of the article shows the new layout in action this afternoon, when I was taking pictures of my Penumbra's Talons DIY space marines. And the picture above right shows some of the results after the original shots were processed through google's Picasa. I confess I think the pictures aren't bad: the colours are quite true to life, and the yellow glare of the halogen spots is gone; all very easy to achieve using Picasa. I've been using Picasa as my default picture viewer for the best part of a year now and I like it quite a lot. It's the best program for managed images I've used, and it's pretty good for basic retouching work too.

All of these labours, those recent vicissitudes and other diversions notwithstanding, my scanner has been the source of the major problem with which I've had to deal. When I began posting pictures of my miniatures to the web a digital camera was way beyond my means, so that I had to rely on my scanner to take my pictures.

The pictures- above and right, show that this produced surprisingly good results; notice, eg. the depth of field in these 2 samples. So I was disappointed to find that my new scanner was much worse. Why worry you might ask? I've finally got a digicam and a half decent photographic layout after all. It's just that scanning can still be convenient for taking pictures of sprues, parts, and so on; all the sort of stuff that I'll need for blogging in other words.

Rising to the challenge

So, wishing to use the scanner for some miniatures pictures, I set out thoroughly to investigate the parameters of my scanner (an Epson Stylus DX3850 printer/scanner), to find the best settings for my purposes. The figure I used- painted version below, was Bosun Grogspar from Privateer Press' Warmachine. Grogspar was part of the swag from Saturday's Claymore.

I went round all the minis traders twice before I finally chose it: I was looking for a mini for August's painting challenge at the Sheffield Irregulars. The Sheffield Irregulars are a fB group I joined a few months ago in one of those random bouts of networking that you do on a social networking site. They have monthly challenges in which entrants must paint a mini (or minis) of their choice according to an agreed theme; August's theme is 'swashbuckling', and I was girding my loins to join in.

I'd been looking for the inevitable pirates but all I'd been able to find was Grogspar. On my second trip round the traders I saw Grogspar and his piratical mercenary mateys at the Edinburgh League of Gamers' Warmachine particpation game (highly commended), and I knew they would fit the bill. Grogspar it was then.

Testing, testing
1. Background
I'd started doing this with other minis but it had turned out that I wasn't going to be using them for RD/KA! so I decided to start all over again with the Bosun. That first run had at least taught me a few lessons about going about the task systematically, so I was able to work more quickly.

Backgrounds

When I was scanning my first minis pictures back in the 90's I just used a handerchief (clean, naturally enough!) to cover the minis on the flatbed. Later I used a box. So I tried several different backgrounds; box and paper looks to be the best. Notice how poor is the depth of field on these images compared to those from my previous scanner. I wish I knew the technical specifications which are responsible for this.

2. Document type
My background set, I next had to determine the best document type setting: photograph was my instinct but I was being thorough after all.

Document types

The illustration document type aside (a bigger file size and poorer image quality), there was nothing to choose between the remaining 4 document types. No reason then to change from photo I figured.

3. Image type and resolution
Image type was going to be colour or grayscale; resolution (AKA. destination) was screen/web or an 'Other' setting allowing me to choose the image's dpi resolution. Screen/web seemed the obvious choice.

Image types and resolution

There is no appreciable quality lost across the various settings. The greyscale screen/web image is the most compact- 810x1105 pixels and 877Kb; as opposed to 2532x 3456 and 25MB for the colour 300dpi image (the largest). Greyscale screen/web it was then.

4. Brightness
I hadn't noticed the brightness control on the scanner control panel before, so I was quite pleased with myself when I started experimenting with it during my first attempt at this task.

Brightness

These are low quality images so that you can't improve them much by changing the brightness setting. Still, brightness 50 seems not too bad: these images are really only to show off parts; WIP shots will be proper photos. And so the scan settings are:

• Paper background and box cover.
• Photograph document type.
• Greyscale screen/web.
• Brightness 50.

I wish I still had that old scanner though. ;)