Conclusion

04:00Z: Turning the sensors off almost cost me, as a lone Fitter managed to get close undetected, thankfully going Bingo before attacking. As soon as the radars were switched-on, a distant SEAD Foxbat appeared, so we went dark again.

At 04:30Z, a Runway Repair event occurred. As this ...

Day 2

05:00Z: Sydney joined BR-HK01.

Spartan detected a Chinese DDG 30nm to her SE and moved to steer around it. Something else that will probably attack us without provocation. The Americans belatedly told us that 1-3 Ming subs are operating S of Hong Kong.

10:00Z: The B-52s reverted to AI ...

Situation and Available Forces

This one assumes that Scenario 4 worked-out much as it did in my playthrough, with the Endeavour convoy making it intact to Brunei and the Soviet convoy to Camranh Bay coming to grief. As a result, the Soviet forces in Vietnam have been passive in the interim and ...

This kind of thing happens a LOT in the Fury scenarios (and not much anywhere else). In Out on a Limb, it turned a serious defeat into a 'victory'. I've mentioned it to Bart several times but we are no nearer to a solution.

In Pacific Fury 6, something happened to me early on which might provide a ...

Thanks for the support. That sounds like a good division of labour, as my previous attempts to post fault reports were none-too-successful. I remember raising an issue on Persian Pounce and being told that the file attached as evidence was too big to be analysed (surprisingly enough, as it's a big ...

Regarding scenarios with performance problems, try any large Fury series offering e.g. Persian Pounce (Indian 1), Caught Flat Footed (Pacific 3). You only have to look at the huge amount of memory the game takes-up (via Task Manager) to know that you're going to have problems unless you have a ...

Hannibal seems an appropriate name for such a change. While improving the ground combat gameplay would be a good thing in many ways, it is primarily a naval and air warfare simulation and we should be wary of going too far down that route. CMO is already a massive game with performance issues in big ...

Then again, I could have altered the Withdraw and Redeploy instructions in Doctrine without using the Editor - I think. I did have a look at the time and couldn't find the right place to do it, but perhaps I didn't look hard enough.

Yes, I was puzzled by the Missouri's being affected like that myself. She was fully-armed and combat-ready, so it has to be a bug. I rationalised it in the report by suggesting that the US Government wouldn't have wanted such a valuable asset to be endangered with a crucial election campaign in ...

Balance of Forces

This is one of a pair of scenarios depicting a Russian attack on the Baltic States in 2016, with the West potentially distracted by the US elections and Britain’s vote on EU membership. As I’m playing the Command Live scenarios (roughly) in alphabetical order as the default ...

In this one, the USSR reacts to US raids on the Crimea with a politically-motivated strike on the Aleutian island of Shemya. While Eareckson airbase is reachable by Soviet bombers, the island also houses the COBRA DANE anti-ballistic early warning radar. Russia is anxious not to damage this, as ...

Balance of Forces

The rather unlikely premise for this one is that a populist government takes power in Japan and decides to go to war with Russia over the Kuril Islands, which extend NE from Hokkaido towards Kamchatka and were ceded to the USSR at the end of WW2. So far, hostilities have been ...

What I don't like about this feature is that it makes no allowance for initiative on the part of the isolated unit, which proceeds to behave stupidly or even suicidally in most cases. Granted, some players would role-play this honestly if allowed to continue controlling the unit, while others wouldn ...

Day 4

06:00Z: The Endeavour convoy fell foul of the game’s lousy automatic navigation (Pathfinder) system while trying to weave through the Buliluyan Strait and decided to go the long way around. Corrected this by moving it in small stages at a time.

08:00Z: I realised belatedly that, despite ...

Day 3
04:00Z: Day 3 started chaotically as the buggy nature of the scenario asserted itself. First, the damaged Orion that was limping back to Guam simply vanished when I re-loaded the game – at least it wasn’t recorded or scored as lost and it would have been out for the duration, anyway.

More ...

Interesting.

The problem with the Skyhawks and the Sampsons was that the Yankee Notch's strike happened during my attack on the Russian convoy, so I didn't see the missiles coming until it was too late. It's the sort of simultaneous timing I tend to suffer from and, the bigger the scenario, the ...

Day 2

Well, as Bart was keen for me to continue into Day 2 and I’m happy to help with his project in any way I can, here it is. Overall, it was an improvement on Day 1.

03:00Z: The Berget Danuto duly sank which, of course, wrongly cost us 25VP (a poor reward for saving Darwin). It also caused ...

You're probably right. After all, the Fury series is essentially 'the game of the book that might be written sometime' and a lot of it is about the story. Nonetheless, it does take a long time to play, with the performance issues sometimes bringing my machine to a complete stop and the bugs don't ...

Balance of Power
Three days into WW3, Combined Task Force 165 is formed with the intention of reinforcing Western-aligned and oil-rich Brunei, which is threatened with isolation by various threats. The Soviets have been permitted to use the Vietnamese base at Camranh Bay, even though Vietnam has ...

Order of Battle
This scenario assumes that the Russo-Ukrainian War broke-out in 2016 and that NATO got involved from Day 1. It covers the opening 24 hours of the conflict. You can play either side, but NATO is the default, so I chose accordingly.

NATO is limited to air and naval forces, as ground ...