We are descending on the fair city of Cologne, Germany this week to attend Gamescom, the world's biggest gaming expo. Our chosen screenshot should be appropriate then, as one of the objectives for the Rhine crossings of March 1945 was indeed Cologne and its bridges.

The major reveal here are the support cards. This is a new mechanic for the UoC series, and it lets us show a side of the war that can’t be represented as units on a map. The player can buy the cards with prestige, or receive them as rewards for taking bonus objectives.


Theater asset cards are the simplest, yet very powerful. The B-26 gives you an additional air attack for the duration of a scenario, which can be enough to turn the situation around if played at the right time.

GMC CCKW (truck) card is interesting because it can be used in two ways: to increase the range of your supply network or to motorize the units (of one HQ). This “motor pool” ability simulates the superior transport capabilities of the Allies, but there is a real tradeoff with supply, especially in 1944 France scenarios.

The really cool option is taking control of the Red Devils. Cards like this are the most expensive, and don’t come up often. They let you make divisional para drops about once every three scenarios, providing your unit doesn’t get killed in the drop. This is a quiet nod to what happened in Market Garden so don’t be reckless with your paras there.

We have a new trailer, which is up to date with the current state of development. It’s already on our steam page, or you can check it out on youtube right now:
https://youtu.be/S_5VF-hwu_0

Release Update: we have updated our release target to “Fall 2019” (also in the trailer). A full release before the end of Q3 now looks unlikely, but we’re still on track to at least go into beta. The plan, as always, is to make the best game possible. We will continue to keep you updated on our release plans as we go along. Thanks for your patience 🙏.

Our Gamescom live stream will be available here on UoCII Steam page on Wednesday, August 21 at 8 pm CEST.
Daniel Mellbin, our scenario designer, will be playing UoC2 live for the first time ever, so save the date if UoC2 is your thing.

We will be in the trade visitor section at Gamescom, so if you’re lucky enough to be in attendance, be sure to drop by the Croatian booth and say hi! (Booth A-011, Hall 3.2)


Cheers,
Tomislav

In recent weeks, we put a lot of effort into making sure that seaborne invasions play well in the game. This is important because these air/naval operations were such a feature of the Allied campaign. Counting just the historical ones, there’s six: Torch, Husky, Salerno, Anzio, Normandy, and Dragoon.

Granted, we have decided to start the campaign at Wadi Akarit, after the Torch landings, but that still leaves us with five so… invasions aplenty. Speaking of Torch, the period between it and the allied link-up in Tunisia will now feature in the tutorial, not the main campaign. Sadly this leaves Kasserine Pass outside the campaign, but we’ll try to make it up with a standalone scenario.

We’ve been working on the campaign quite a lot, and since campaign play revolves around HQ upgrades, I feel that it’s time to do a proper Headquarters deep dive. In fact, the bulk of this post will be about HQs and the campaign, but let’s quickly talk about invasions first because there is a screenshot, and it is a-mazing.

The invasion force in the screenshot below is typical for Allied operations of this kind. It has battleships providing naval defensive fire, LCVP landing craft ferrying the units involved in the naval assault, and a plane carrying paratroopers. It should really be a C-47 but we don’t have them in the game yet (can you tell which plane we’re using instead? Also, which bb?)



Mechanically, naval assaults and para drops basically do “what it says on the tin”. Assuming an assault goes well, the unit lands with no MPs and no AP, or with its AP locked if the landing was unopposed. This is consistent with other game mechanics, such as river crossings.

On the following enemy turn, the battleships will be providing naval defensive fire, covering the landing beach hexes. This works out to a -3 artillery (-like) shift against any enemy units attacking our units on the beach.

We already mentioned HQs in earlier diaries, and described how they are used for various command and support actions. The actions include everything from bridge repairs to unit reorganization, and performing each one costs some number of command points (CPs).

The number of command points available per turn represents overall commander and staff proficiency of an HQ – there are only so many things an organization can do at once. While coordinating a set piece attack at the front, the HQ can’t also be building fortifications or doing emergency supply runs.

As the campaign game progresses, the number of CPs per turn can be increased. This represents an improvement in HQ staff skill, and happens at times when its units have earned enough xp to merit an upgrade. At that point, the player may choose to increase the number of CPs per turn (overall skill) or to reduce the CP cost of one specific action (specialize).

HQs are divided into five branches: Force Pool, Intel, Operations, Logistics, and Engineering. Every action belongs to some branch: for example, bridge repair to engineering. Branches are further divided into three levels, not all of which are always unlocked.

In the screenshot, the US II Corps HQ has Level-1 Force Pool, meaning only deploy and reorg actions are available. The higher levels of this branch are locked, and so transfer step and security unit actions are not available to the player.

The player can unlock higher branch levels at conferences, which are breaks in the campaign game that happen once every six months or so. At a conference the player can, among other things, spend prestige to unlock higher levels of HQ branches.



In the screenshot, you can see that HQ range for the US II Corps equals 10 movement points (MPs) or 3 trucks. The trucks represent transport assets, which are also used in the supply system. Upgrading to add more trucks is possible, but it increases the MPs less and less (5 – 8 – 10 – 11 – 12). This is because increasing HQ range needs to cover an ever larger area.

When an HQ moves, it generally uses the same number of MPs as its range (10 in this case). It then gets 3 more MPs if it moves via uninterrupted rail movement. This is the case for all the HQs we’re actually using in this campaign, but we’ve built some additional flexibility into the system.

Just to give you a taste: one of the possibilities left open for future development is a “mobile” HQ that has a fixed, smaller range, but whose movement is fully upgradeable. This is something we would want to use for a German panzer corps for example, or maybe a late-war Soviet cavalry mechanized group.

We released another mini-trailer last week. You can find it in the announcements section here: Death from Above – AI and Airpower Trailer. We are doing a lot of work on localization, testing with a small group of languages to make sure the translations don’t break UI layouts etc. There’s a lot of tweaking ongoing (tweakage?), many fixes and generally the game starting to look like the real thing.

The work continues!
Tom

https://store.steampowered.com/app/809230/Unity_of_Command_II/

November 1944. The city of Metz, located near the German border, still stands in the way of Allied push across France towards the heart of the Third Reich.

Patton’s Third Army had been fighting fiercely since early September to dislodge the Germans from the heavily fortified city, suffering casualties that approached 50%. Hitler had ordered that the city, and the fortress complex around it, were to “hold at all costs”.

Metz did hold. It was one of the greatest shows of resistance by the Third Reich in World War II.

That is, of course, until December when the last of the city’s defenders were forced to surrender. To help put things into perspective, Americans had more than 3.500 fighter planes and even more bombers available. Together with the Royal Air Force, the combined Allied air strength on the Western Front was almost 14.000 planes.

Luftflotte 3, protecting the German armies on the Western Front, had less than 600 available aircraft. It’s safe to say that Allied air forces held overwhelming superiority over the Luftwaffe in western Europe. German commanders pleaded with Hitler to allocate at least 700 more planes to the area. There was even talk of Luftwaffe’s secret weapon, one so powerful that it could turn the tide of war: world’s first operational jet fighter!

Messerschmitt 262 jets were real and deadly, but in reality jets were barely operational by the time the Battle of Metz took place and were too few in numbers to make a difference. The rest of the requested planes never arrived.

Even with clear air superiority, the Third Army was still bogged down in the mud, unable to advance. There were several reasons for this:

• P–47’s carried 500-pound bombs that had little effect on reinforced concrete and bunkers around Metz
  
• Tactical Air Command that supported the Third Army was too dispersed (flying both Metz and Brest, almost 800 kilometers apart)
  
• Metz would open up a route to Frankfurt and Saar, and the Saar route was a lower priority compared to the lower Rhine and the Ruhr. Ruhr>Saar.
  
• Finally, and most importantly - the bad weather

Unity of Command II takes Allied air superiority into account throughout the campaign. Let’s take a look at the trailer:
https://youtu.be/vEpQiXJxp2Y
As soon as the weather clears, the player is given control over thee off-map tactical air force actions that provide recon, air cover and close tactical support for the attacking units on the ground. Bombers are called into action in the video, but Unity of Command II will feature more aerial actions, such as air reconnaissance. Airdrops will also be available, depending on the scenario, date, and your progress in the campaign. As long as there aren’t any large scale ops, attempts to supplement ground transport with the air transport proved effective on the Western Front and the game will mimic these solutions as well.

The trailer ends with the encirclement of Metz, an outcome that wouldn’t be possible without air support. The enemy counter-attack was fierce and, depending on the difficulty settings, a solid show of what the game’s AI is capable of. Or indeed, what the German generals were capable of.

The game’s AI takes into account mission objectives, player’s moves and also consults some of the historical moves before taking action. The brutal panzer counterattack that the AI selected as the best option in the trailer mimics the Schild und Schwert (Shield and Sword) tactic mastered by the best defensive commanders of the Third Reich, and is a precursor of what the Allies will have to endure in the Ardennes in December.

Defensive tactics managed to keep the Third Army at Metz for almost three months, which bought time for Hitler to shore up the Siegfried line where many more lives were lost. Still, was Patton’s decision to order a frontal attack on one of the most heavily fortified cities in Western Europe necessary? What would have happened if the fortress was bypassed? Or was there a way to encircle it and take the city in, shall we say, few turns less? Unity of Command II will be out soon - what will be your strategy for Metz?

A full development update is due next week on our blog (will also be re-posted here on Steam). In the meantime, as usual, feel free to AMA in the comments.

Cheers,
Tomislav
https://store.steampowered.com/app/809230/Unity_of_Command_II/

September 1944. Hitler’s armies are retreating in disorder after their defeat in the Normandy hedgerows. The Allies keep up the chase across France, but General George Patton’s 3rd US Army is beset by supply difficulties. The Germans finally manage to re-establish a defensive line around the heavily fortified medieval city of Metz. According to orders issued by Hitler, fortress commanders are to hold this position at all costs…

Encouraged by good feedback from our previous post, we decided to start on a series of short trailers about our game mechanics, old and new. The story starts with the 3rd Army actions following the long and bloody stalemate at Metz. It is through a series of coincidences that we are again going on about stragglers (sorry!) but I hope the trailer is worth it for everybody. There is also a lengthy development update at the end of the post, as usual.

The Battle of Metz resulted in heavy casualties on both sides, and while the exact German losses remain uncertain, it is known that the 3rd US Army took at least 75.000 prisoners during the operation. For the US forces bogged down in the mud, this created a significant logistical problem, in addition to other hardships.

The scenario starts in November, after weeks of horrific stalemate. The Germans had a moment to regroup and now they’re dug-in. The confluence of rain-swollen rivers of Moselle and Seille creates a natural obstacle to frontal assault and the terrain has all turned to mud. There won’t be any grand sweeping maneuvers here. The battle of Metz will be a slugfest.

https://youtu.be/VQXbNybumIY

The city itself is protected by a deadly network of heavily armed forts with siege guns, some of them complete with medieval moats (that still work perfectly against tanks). The two US divisions shown in the video have the right idea as they go into the attack, trying to outflank the fortification.

Advancing US forces are taking prisoners along the way. If they take enough during one turn, they will provide valuable intel. In this case, the 6th Armored managed to gather that intel, but it’s just more bad news for the 3rd Army: the road to Saarbrücken is heavily guarded by German armor. Airpower could help with this threat, but the weather would need to improve first.

What would you do? Would you wait for air support to deal with the panzers? Order a full frontal attack on Metz? Bypass the city entirely, waiting for lack of supply to catch up with the defenders? With every passing day the industrial production of the Ruhr and the Saar continues contributing to enemy war effort or, in game terms, your prestige sinks lower and lower.

Realistically, most of our time is spent working on the UI. It is simply the most important aspect of a strategy game, period. However great you make the game mechanically, most of the good stuff will remain forever buried unless you make it accessible. With that in mind, we keep adding and streamlining stuff, so here it goes.



We have asked the 3rd Army HQ to highlight any bridges that can be blown in this turn. This removes all units from the map for clarity, highlights the bridges, and shows the orange banner in upper right. We’ve found that the banner is often needed. Sometimes via the hotkeys and UI buttons you’ll switch the game to some unknown state and be left wondering: where on earth have my units gone?!

The HQ itself is shown in a pretty basic configuration, with all of its branches at default levels, i.e. not upgraded. This HQ provides the following actions (left to right): bridge repair, bridge destruction, entrenchment, emergency re-supply, suppressive fire, no retreat, deploy and reorg. Actions are then grouped into branches: Force Pool, Intel, Operations, Logistics and Engineering.

The division into branches is inspired by the general staff system used in western militaries: G-1 for personel, G-2 for intel etc. Each HQ can be upgraded differently during the campaign, giving the player some interesting choices about how to adapt to the situation and his own play style. In general, upgrades will provide the HQ with new and advanced actions, such as recon-in-force, security units, etc.

The work continues on many fronts, and I’m never sure how useful are these short updates that I give at the end of my blog posts. Let me know in the comments if you think they are. But first, here is a screenshot of the Italian peninsula from way above. It’s pretty to look at, eh?



We’ve kept adding more and more workflows of the “bridge destroy” type shown above (and mentioned in Developer Diary 20 to number around 36). To be honest, I’ve lost count of them, but now that we understand how to add them systematically, we just keep adding more wherever we feel it’s needed.

We also started working on a human-readable AI Playbook. To explain: our AI has always been a heuristic one, not the deep learning kind that’s getting all the media coverage lately. We’d translate some part of a player’s thought process into computer code, which we then call a tactic. The job of the AI is to look for tactics that are applicable in any given situation.

The playbook is the next step in our AI development: it’s a human-readable catalog of tactics that is accessible to team members who are not programmers. It took some time to nail the correct format, and I don’t think scenario designers and players will be able to contribute to the playbook directly just yet. It should be a great tool for this though: when the AI programmer and the scenario designer sit down to discuss, they will have a common language to describe what the AI is doing. Even better, they will be able to record any new tactical ideas in a way that’s understandable to both. I expect great things!

At the last minute Daniel has noticed there is a historical error in one of the images in this post. Can you spot it?

The work continues!

Cheers,
Tomislav

August 1944: after months of hard fighting, the Allies are finally out of Normandy. In front of them, the Wehrmacht has all but disintegrated, having stood its ground up until the breaking point. Supply is now the biggest concern for the Allies. Taking the large port of Antwerp will allow them to freely operate their vast armies and air forces in months to come.

Now that the game has been officially announced, I’ve decided to change the post format for this diary a little. Previously, I focused heavily on what we were doing internally. I was giving a lot of technical info, and even airing our own doubts if the project was going to get completed at all. Big thanks to all who’ve had the patience to bear with these “developer confessions”. The new format should be much more player oriented. We will be going through concrete examples of play, the historical context, and how the game mechanics tie everything together. I hope you enjoy it!

If you’ve been reading our previous developer diaries, you’re likely already familiar with some of the key new features in Unity of Command II, like fog of war, HQ intel, and stragglers. Today we’ll show how these new features tie together to form a tight little gameplay loop, that gives an entirely new dimension to the game.

In the screenshot, US 1st Army is in position on the left bank of the Seine estuary, and is looking to jump across the river at Rouen. En route to Rouen however, they need to deal with German forces stationed around the town of Évreux.


Check out the blue dots just north of Évreux: center of the map, right behind that panzer IV. Those are stragglers: routed enemy elements trying to make their way back to their HQ. We’ve talked about the idea of stragglers in our very first dev diary. The blue icon shows their approximate strength in steps, and the orange symbol on the 3-step straggler is important – but read on.

Usually, you want to capture enemy stragglers anyway, before the enemy gets to reorganize them and use as reinforcements. There’s an added bonus though: prisoners provide valuable intel to your HQ. After you capture a set number of stragglers (in one turn) they reveal locations of enemy units hidden within Fog of War. Let’s take a look at how that works.


In this example, first the 30th US infantry division attacks an armor kampfgruppe. The attack is successful and the enemy unit is removed from the map. It’s not completely destroyed though, and you can see the routed troops join an existing group of stragglers in the rear. To make sure they don’t reorganize, the Sherman moves in and mops up, taking prisoners and clearing the road. This results in valuable new intel, and some enemy units are located on the map, just across the river. Turns out, the road from Paris to Rouen is swarming with enemies!

As the Sherman (actually, 5th US Armored) moves in and takes the 3-step enemy straggler as prisoners, the prisoner counter on the HQ sheet (bottom right of screen) reflects this change. The prisoner target, set by HQ intel, has been reached, which means that HQ intel can now locate enemy units one hex inside fog of war. These units are shown on the map as intel markers. You also get a notification in the bottom left of the screen, just above the quick-select HQ buttons.



The stragglers mechanic not only prevents bloody, wipeout scenarios, and thus addresses one of the main issues from the original Unity of Command. It also gives you more tactical choices: attack head-on, encircle, or mop up routed enemy units? Gather valuable intel and prepare for the next turn, or rush forward without full knowledge of what lays ahead?

Sometimes you will have to deal with stragglers simply to keep the roads open, and be able to advance. One or two steps of enemy stragglers shouldn’t be a problem. Your units are able to capture them simply by moving over them while advancing:


On the other hand, three stragglers on the map represent 5.000 to 10.000 routed and disorganized enemy soldiers, and that’s a problem that needs to be dealt with! Moving right through them will cost at least 3 movement points. Alternatively, you can go around those stragglers, but either way sometimes that means that the prize will remain just outside your reach. Here’s that same Sherman unit, in a slightly different situation, with 3 stragglers instead of 2 on the road. Notice the choice to go around or mop up:



How many stragglers need to be captured to reveal enemy units in FoW? Will HQ intel only reveal units close to the frontline or further away? This is all still in active testing, and we’re tweaking some of this stuff heavily.

There are further interesting tie-ins, to other game systems, but those will have to wait for another post. As a teaser, HQ intel can be upgraded as part of the campaign game, and it becomes temporarily suppressed when the HQ is out of supply or gets routed.

We’re really trying to load this one with depth folks, and I hope you all like the final product.

Take care and AMA in comments as usual.

Cheers,
Tom

https://store.steampowered.com/app/809230/Unity_of_Command_II/

It’s no secret that we’ve been working hard for many years on our second game. Today we’re happy to officially announce that Unity of Command II is coming in Q3 2019.

Steam store page went live today and we’ll be sharing more details on the brand new engine, game mechanics, and eye candy there, as development progresses. Check out the announcement trailer and new screenshots here:
https://store.steampowered.com/app/809230/Unity_of_Command_II/

This is a big day for us and we’d like to thank all wargamers and fans of UoC who supported us. You gave us courage to soldier on with this project! The best is yet to come and we can’t wait to show you the full game. Please support us by wishlisting the game!

By now, a lot of the people following this diary must be thinking “so anyway, this game is practically done, right?”

I guess it depends on your definition of “practically”. It is certainly playable, there are very few features that are outright missing, and the scenario count is up to around 20-ish. On the other hand, we’re trying to make a game that’s better than merely playable, so expect more diaries from me until we’re judged release-ready.

As an example, the deformed Union Jack in the picture is not an attempt at cheeky political commentary, it’s actually what we need to do to make the flag readable in its wavy shape. I was not even aware of this process until Goran, our lead artist, showed me how we do this for almost every flag in the game.

It’s a good illustration, I think, of the type of detailing work that we’re doing right now. We take the game to be mechanically solid, and we’re making rule changes only exceptionally. Our current focus is on the (many!) details that make up the flow and feeling of the game. Eventually, the plan is for the final round of scenario and balancing work to be done on a near-finalized, comfortably playable version of the game.

Here’s another one of our cheerfully over-engineered™ features: we’ve made all the in-game boundaries (front line, movement range, etc.) tightly follow river banks. The readability improvements from this are indisputable, as you can see in the screenshot below, of an early Allied push to the Rhine.

It gets even better in difficult terrain such as in the Ardennes, which were a real concern to me. A lot of the action happens on that least-readable part of the map, and we were actively looking for solutions. I feel this not only does the trick, but also looks pretty attractive.



(click image for full size)

From a technical standpoint, you can see that the basic idea already existed in Developer Diary 8. Even back then, the front line lies on the near bank, and the movement boundary is set on the far bank. This worked without a hitch in practice, and even the first implementation pass was not so bad.

That was when we hit the edge cases though: river confluences, boundaries hopping from river to river, poorly drawn rivers which confused the algorithm… you know, the works. We ended up throwing an insane amount of computational geometry at this (cheers @Ante) and let no one in the comments tell me it was not worth it. Seriously, I double dare you and all that.

Neatly contradicting my own words from the top of this very post, we made some important changes to the HQ mechanics. Previously, HQ areas were not allowed to overlap, and we had a map view that showed all HQ areas together. This looked pretty good – similar to a military situation map, and I still think it’s not a bad idea in simulation terms.

Unfortunately, it turned out it was impossible to find an HQ movement mechanic that does not play hell with that neat picture. The scenario setups were great, but the playthrough that followed not so much. Our solution was to remove the no-overlap rule, while at the same time shrinking HQ range. In practice, this removes most of the “unrealistic” overlap and is an OK, though not perfect, solution.

While we were at it, we solved another issue that kept popping up: it was not easy for us to see which units belong to which HQ. To this end, we are now showing subordinated units and the HQ range when it’s selected (screen below). Out-of-range units are shown in red, and actually now as I’m writing this, that red icon looks a bit more screaming than it should be.

Units being out of HQ range are nowhere near as bad as being out of supply. Yes, they can’t get reinforcements, and their HQ can’t help them with e.g. entrenchment, but mostly they can fight alright. Overall, I feel this new system works and feels better than any sort of tedious OOB-accounting we might have put in its place.

I haven’t forgotten the people who hate squinting at tiny fonts, and so the UI scaling shakedown continues. Parts of the UI where this works look glorious when zoomed-in, the ones that don’t (yet) keep shrieking at me menacingly. The work continues!

We’ve added core localization support, with an eye to supporting not only our own content, but also community scenarios and mods. A few tests were run to confirm that, at least, cyrillic and chinese scripts work and don’t break anything major.

We’ve added and/or tweaked many of the in-game icons in our perpetual quest for readability: in the main screenshot you can see the new objective markers (red), and an improved version of the road-blocking stragglers icon. Every little thing makes a difference.

The team is quietly winding things down for the year. There’s a good feeling all around, especially when we consider the progress we’ve made – as can be seen simply by comparison our December ’17 dev diary.

We wish you all a Merry Christmas, and to ourselves, a release date in the coming year 😄

Best, Tomislav 🙏

Hello and welcome to Unity of Command 2 Development Diaries!

We’ll be posting a brand new Development Diary #19 shortly, here on Steam’s announcement section, but here’s a short recap in case you missed any of the previous entries.

While it’s true that Unity of Command 2 hasn’t been properly announced it’s no secret that we’ve been working on the game and, in fact, have been at it for quite some time.

The sequel is on its way, we confirmed that much in this Anniversary post in the Blogs section on Unity of Command web quite some time ago.

The very first Development Diary (‘No More Wipeouts!') was published just a couple of months later and can give you an idea of what to expect from the upgraded mechanics, while the second diary entry (Objectives) weights the pros and cons of timed objectives in the game (spoiler alert: it looks like we’re keeping those).

Excellent reads, both of those, but Tom, our Project Lead on UoC2, has set a high standard for himself and decided to start from scratch. “I’m restarting the dev diary series” announced Tom and then proceeded to explain the envisioned changes to the losses management system in both a scenario and a campaign. The third diary entry (Are You Experienced?) also hints at tweaks to the familiar veterancy levels and mentions upgrades between scenarios for the very first time!

A brand new feature, headquarters, was announced and explained in Report to HQ, ASAP!, while The Supply Network and Move it, Soldier! shed some light on the refining process of the defining mechanics in Unity of Command; planned changes to supply logistics, fighting and maneuvering are detailed in Dev Diaries 5 to 7.

Campaign drops the bomb with the first ever Art Preview, but the excitement doesn’t stop there as Tom announces the switch to a brand new in-house 3D engine built on Python while staying recognizably Unity of Command. Developer Diary 9 (Map Making) takes the next logical step and explains the process of map building, apparently a tedious task with a very limited room for automation. We use the word ‘shader’ for the very first time, marking a new chapter in the development of Development Diaries.

Performance diary answers the age-old question - will this game run on my age-old PC? - with a resounding ‘probably yes!’ but please don’t tell that to anyone just yet as we’re still tweaking things in hopes of making the game look even better and running on lower spec hardware. Oh, and if you read the comments section in Dev Diary 10, there’s also a brief mention of planned additional content for the game which is a politically correct way of saying yes, there will be DLCs!

A rather novel game development technique was introduced last year in the Summer of Systems: the team decided to ditch any low-level system that wasn’t implemented by the end of August. Good news: team crunched and ended up implementing most of the planned systems. Steam release is casually confirmed.

An open invitation to modders was sent out in So over with Under-The-Hood, a Dev Diary 13 that also publishes a new screenshot, describing an interesting problem: the units were drowning in the terrain, which is kind of a point of military uniforms, but apparently not really good for gameplay. The solution? You’ll have to read to blog, unfortunately.

Alternatively, you could start browsing through Dev Diaries 14 -17 that namely discuss new features like The Fog of War, Intel system or the weather modifiers, but truth be told are just excuses for the team to show off a bunch of new visuals: while the subtleties of screen space ambient occlusion are hard to notice, the Unity of Command 2 is starting to look just plain gorgeous! Case in point - this Trick or Treat screenshot.

TL; DR
Not bad for a game that hasn’t even been properly announced, eh? If you read between the lines, we’ve spilled the beans on pretty much all major improvements to gameplay, explained the reasoning behind new features and even gave a hint to the release date - check out the brand new Dev Diary #19.

The work continues!