Campaign Series Event Engine in Vietnam 1.0: Accessing Adaptive AI

Welcome to the second Developer Diary on how to use CS Event Engine in Vietnam 1.0. In the first part we talked about the latest CSEE version in CS Vietnam 1.0, now let us have a look how the new CSEE Lua library interacts with another Campaign Series gem: the Adaptive AI database.

Note: This is meant as an introductory blog about the coming features. There will be a complete CS Event Engine manual shipping out together with the game install. 

Adaptive AI in a nutshell

Adaptive AI became available as of Campaign Series: Middle East 2.0. Here’s what our Lead programmer Berto wrote at the time, emphasis mine:

The Campaign Series AI — One size does not fit all!

Arabs did not fight the same way as Israelis. Jordanians outclassed the Egyptians, who outclassed the Syrians. Israel’s combat doctrines changed from 1948 to 1956 to 1967 to 1973 and beyond. The cocky Israelis at the beginning of the Yom Kippur War learned to give their revitalized Egyptian foes newfound respect and learned to change their ways. Adapt or die.

From nation to nation, from war to war, from year to year, even from one battle to the next — they all differed, so much evolved. But in the traditional Campaign Series, as in most (all?) war games, there is one and only one AI. Locked down tight. Mostly inaccessible to the scenario designer, much less to the player. Until now…

We have devised a new customizable AI System. Customizable by side, by nation, by scenario. Open to the scenario designer’s tweaking. Also to modder’s. We call this new system: “Adaptive AI.” As in: An AI that adapts to the side, the nation, the era, the individual scenario. (Not as in: Adapts real-time to changing game play circumstances. But that too will be implemented in future updates.)

The purposes of the Adaptive AI are:

  • To coach the AI in ways and things it is too dumb to figure out by itself.
  • To achieve game play “balance”.
  • Not so much to improve the AI play as to better simulate actual combatant and scenario conditions.
  • To achieve greater “realism” and “historical fidelity”.
  • To add randomness.
  • Thereby increasing replayability.

These cross purposes are often at odds with one another. Some Adaptive AI parameters will make the AI opponent “better”; others will make it “worse”. It all depends. Some players will like the increased uncertainty; others will not. It all depends. That’s why the Adaptive AI is optional. Select it or not as you wish.

Looking back at Adaptive AI: yes, it was static, required creating and adjusting scenario specific *.ai files, but at the same time: it truly opened the game parameter database for the scenario designers. If only it would have been easier to use…

Adaptive AI in Vietnam 1.0

Fast forward to CS: Vietnam 1.0, and the Adaptive Ai database itself got a thorough upgrade for Vietnam 1.0. At the time of writing this there’s a template file now with a slot for 200 adaptive AI parameters. So many new aspects the scenario designer can adjust on a per-scenario basis!

Campaign Series Vietnam Adaptive AI

But what is completely new is the ability to access these parameters as the scenario plays on – from the CSEE Lua code, dynamically throughout the scenario play!

Now, the AI truly adapts itself as how the events take place during the play if the scenario designer so chooses. Have all the SAI controlled troops change their stance from a rear-guard action with Opportunity Fire set at sniping at long ranges to Ambush stance, where they only fire when they see the white of the eyes of their opponent! How cool is that!

Accessing AI parameters from CSEE Lua code

As a recap, here’s how the Adaptive AI was used with CS Middle East 2.0. See below for an example of how it worked at the time: first create a scenario specific *.ai file from the template, then tweak the parameters you want to change.

Here’s how some changes to Opportunity fire settings were made with CS: Middle East 2.0. A bit crude perhaps, but it got the job done:

Campaign Series Middle East Adaptive AI

So, what happens there, exactly? Here’s what the Sirte scenario specific AI file sets to play it out:

  • opfire_sam2_helo_prob defines the likelihood Opportunity Fire kicks on against an aerial target. Think of this as SAM Radar noticing the target, and giving the firing co-ordinates to SAM batteries
  • opfire_sam2_helolow_prob and opfire_sam2_helohigh_prob then define the likelihood the individual SAM battery being able to lock on to target, and to launch their missiles against the target.

In CS Vietnam 1.0, you can set those values you want changes within the scenario specific Lua file.

Here’s an example of how you set up Opportunity Fire values per generic level. This snippet shows just the part for setting Op Fire for all your armored units:

Campaign Series Vietnam CSEE Adaptive AI

Let us look at available CSEE functions in detail. There’s one for setting a value anew and another one for increasing or decreasing the existing value per the parameter provided:

  • set_adaptive_ai (side, nation, index, value)
  • inc_adaptive_ai (side, nation, index, increment)

Here are the parameters, explained:

  • side — “a”, “b”, or some function or expression evaluating to either of those side values
  • nation — integer, or some function or expression evaluating to an integer; from 0 to 99
  • index — integer, or some function or expression evaluating to an integer; from 0 to max Adaptive AI parameter #
  • value — integer, -1 or greater
  • increment — integer; 0, positive or negative

Let us then look at the first call from the code example:

  • set_adaptive_ai (“nil”, FRENCH_NATION, 30, OP_MEDIUM)

And here’s what the parameters mean:

  • “nil” – most AI parameters are set either per nation, or per side. Opportunity fire is per Nation, so side is not provided, ie. nil.
  • FRENCH_NATION – there’s just two values for side, side “a” or side “b”. FRENCH_NATION is a variable with a value of “a”, used as a mnemonic and for ease of use. One could simply say “a” here as well.
  • 30 – this is the Adaptive AI parameter index. 30 is for tanks firing at hard targets, 31 is for tanks firing at soft targets, etc. Parameters are explained in the manual, and in the Init-ai database file for baseline values.
  • OP_MEDIUM – this is a mnemonic for a number value for medium range, ie. 2.

… and that’s all there is to access any of the circa 200 Adaptive AI parameters via CSEE Lua code, at any time, for any reason.

Here’s another example, this time from the CS: Middle East 3.0 early BETA. This is actually an equivalent of what was shown above per how these parameters were accessed via the *.ai files. This time, totally dynamic, with an ability to set and change these values per how the scenario play ebbs and flows.

Campaign Series Vietnam CSEE Adaptive AI

To quote Berto again: Totally dynamic, no time restrictions whatsoever.

Thank you for reading this far!

In part 3 of the CSEE Developer Diary we will ber talking about how to program the computer opponent, or Scripted AI (SAI), to have a keen operational sense, in addition to how legacy AI handles the tactical situations.

Stay tuned!

 

 

 

 

The French Indochina War in Vietnam 1.0

Running through the years from 1948 to 1967, Campaign Series: Vietnam 1.0 will cover the three wars of the time period, the French Indochina War, the Vietnamese Civil War, and the first years of US involvement in Vietnam. And with 100+ scenarios, we hope there’s something for everyone to dive in.

We’ll start this new countdown to Vietnam 1.0 blog series with the French Indochina War. Here goes (with a disclaimer we are still with a late BETA version of the game)!

The French Indochina War in Vietnam 1.0

Rewind your clock back to 1948, as that’s where the French Indochina War kicks off in the battle of Giong Dinh. Here’s the Scenario Selection dialog with the current beta:

From the Sky – Battle of Giong Dinh

At Giong Dinh, it is still relatively low key, with a quick company sized jump to clear out a suspect Viet Minh operations center there:

French Paras at Giong Dinh

Looks innocent enough?

Building up from there, the battle of Mao Khe in 1951 is covered next. Defending Mao Khe is approximately a Battalion sized French formation against the elements of the Viet Minh 308th, 312th and 316th Divisions.

Day River Campaign

After Mao Khe, the war – and scenarios depicting it – escalate quickly. What follows then is a five-scenario long coverage of the Day River Campaign, where if playing vs computer you actually get to play both sides. First as Viet Minh, for the first two scenarios, it is important you’ll quickly learn the tactics to overwhelm the French positions. Using the cover of the night shall be important as well.

The Day River Campaign

Playing the French side, next, you will soon learn this war will actually take some serious effort if the French rule over Indochina is to be preserved. After the French counterattack, there’s two more Side B  first scenarios with Viet Minh with the initiative.

Day River campaign is also covered in scenario designer David Galster’s excellent de Lattre’s Line series: with the first blog covering the Day River Campaign itself. Recommended reading!

Hoa Binh – Operations Tulipe and Lotus

Having fought your hardest at Day River, the Hoa Binh Campaign and the two scenarios covering it await next:

Hoa Binh Campaign – Operations Tulipe and Lotus

There’s still some linear battling to be had before the Viet Minh learns to master the asymmetrical nature of the war in the latter years.

Operation Tulipe provides the French player with a nice chance to deploy some Hammer-and-Anvil tactics…

Operation Tulipe in Action

…while Operation Lotus and the road to  Kem Pass scenario will have them on the ropes trying to keep the few routes open against a clever and cunning enemy.

Road to Kem Pass, with a widescreen view – Can’t be that difficult, can it?

Both Hoa Binh scenarios have the French with the initiative, vs a stubborn Viet Minh element on the map.

Street Without Joy

Then, three more individual battles, first at Tu Vu where the Viet Minh is about to attack a French outpost, and Na San, a larger battle with the French player defending a hedgehog perimeter around Na San against a determined Viet Minh opponent.

Then, Street Without A Joy in a large, complexity 8 scenario by Jason Petho …

The Street Without Joy

,,, together with a huge map of the area, where under Operation Camargue, one the largest use of French forces set to clear the area:

Street Without Joy in its full glory (night graphics)

Definitively a chance for some misery and lack of joy, trying to find the evasive enemy before they vanish to the darkness of the night!

Operation Castor – Dien Bien Phu

From street without joy then to Operation Castor and Dien Bien Phu.

We all know how that will end, but hopefully there will be some joy to be had, with the scenarios available in the game? Dien Bien Phu is actually covered with a hugely excting ten-scenario series!

From parachuting to valley and  taking over the objectives there, towards a siege operation the medieval warlords would be jealous of. As the Viet Minh noose tightens, there’s less and less room to maneuver for the French troops. They won’t be sitting it out though, a good few French initiatives covered here as well:

Operation Castor – a happier time

With Dien Bien Phu series, you will again have a chance to play scenarios against computer both as the French or Viet Minh player. The French player is with the initiative with Bruno Arrives, Breakthrough to Isabelle, Bruno’s FlaK Raid, and the Battle of Five Hills, while the Viet Minh player has the first go with the rest, first assaulting the Beatrice strongpoint with scenario #2, and finally putting an end to it all with scenario #10, Castor Dies.

Worth a shout here are also the articles covering the famous battle by David Galster and available at CSLegion.com, as part of Bruno’s Bunker series, for instance Operation Castor describing the French strategy behind Fortress Dien Bien Phu, and from the beginning of Bruno Arrives, to  the bitter end with Castor Dies.

KP 15

Also worth a shout – a lot of shouting going on here it seems – is the battle at the Kilometre Post 15, available here with yet another chance to have the French being ambushed by Viet Minh.

Kilometre Post 15

As per the scenario information above, tagged as ALL, the computer player shall be well equipped to handle either side here. ALL covers the head to head play against a friend as well, there will be plenty of Play by email or Hot Seat fun with all of these scenarios as well.

Missing a Battle?

Thanks for reading this far!

That’s twenty+ historical, thoroughly researched Indochina War battles covered in the game. Viet Minh, French formations, ARVN, and other troops such as the Catholic Militia, they all shall play a part.

Should that not be enough, should that one favorite historical skirmish miss from the set, worry not. While there’s over 100 scenarios included in Vietnam 1.0, there’s also the full set of editors available, per our usual standards. Complete with Orders of Battle for the era and a set of HUGE master maps to assist in creation of any new scenarios you’d like to see there.

Another set of blog posts is covering the new Campaign Series Event Engine to spiff those new creations even more up.

Next Stop: the Vietnamese Civil War

In the next blog post for this series we’ll be introducing the Vietnamese Civil War scenarios included in Vietnam 1.0.

Until then!

Campaign Series Event Engine in Vietnam 1.0: Triggering Events

Campaign Series Event Engine (CSEE) is a new system that allows scenario designers to script events in their scenarios to add more capabilities not seen before in the Campaign Series games. This system uses programmed Lua files to determine what the events are and how they interact with the scenario.

Triggering Events with CSEE

All of the scenarios that are included with Vietnam have a large component of the AI using the Campaign Series Event Engine where one side is fully scripted, providing an exciting opponent to play against. For the purposes of this Developer Diary series, I will look at what CSEE brings to Campaign Series from three viewpoints:

  • How Events are triggered in scenario Lua file
  • How Lua provides an easy to Adaptive AI settings, and
  • How the computer player with Scripted AI is a new kind of a foe.

In this post, I cover the first capability: how events are triggered and what you can do when that happens. Before that, a few words on the anatomy of CSEE itself.

Note: This is meant as an introductory blog about the coming features. There will be a complete CS Event Engine manual shipping out together with the game install. 

Campaign Series Modern Wars game engine vs. Campaign Series Event Engine

While there has been quite a few additions and enhancements built to Campaign Series game engine itself, none of them has been as exciting as the ability to react to anything happening in game – ie. having an event to taking place – in a scenario specific manner. And even though we combine the CS Lua Event engine with the game engine into one integrated game executable, on game launch, it is useful to think of the two engines as two separate programs running side by side. As an event takes place in the Campaign Series “Modern Wars engine” (built with MS Visual C++) it forks out a call to Campaign Series Event Engine “Lua engine”, running in parallel in the same process space. This is very efficient, too: you’d expect to see a little delay perhaps but no, it all plays together very smoothly.

Specifically, there’s a scenario specific Lua file available to catch these game event  calls, in any and all of the event functions now available. Once said event function has been processed in Lua engine, the control then returns to CS Modern Wars engine to continue with the game play there.

As with previous Campaign Series games, CS Vietnam 1948-1967 comes with a full set of editors. You can create your own scenario just like you did with previous games and their editors. Only now – it is an option – you can add a Lua programme file to the scenario you have designed. In that Lua file you can handle any game event in a manner that is relevant in the battle you are depicting.

Reacting to game events

Triggers available

Once an event takes place in the game, the game triggers an event function in the scenario specific lua code. Here are the event functions available at the time of writing this post. It is rather lengthy, but that’s the whole point, so here they are in all their glory:

  • on_air_attack (hc, pid, name, side, nation, points, strength)
  • on_arty_attack (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_build_barrier (hc, trackid, pid, name, side, nation, oid, orgname)
  • on_build_light_bridge (hc, dir, trackid, pid, name, side, nation, oid, orgname)
  • on_build_vehicle_bridge (hc, dir, trackid, pid, name, side, nation, oid, orgname)
  • on_clear_hex (hc)
  • on_clear_lz (hc, trackid, pid, name, side, nation, oid, orgname)
  • on_damage (hc, trackid, pid, name, side, nation, oid, orgname)
  • on_entrench_hex (hc, trackid, pid, name, side, nation, oid, orgname)
  • on_hex_assault (hc, side)
  • on_hex_attack (hc, side, nation, attype)
  • on_ied_attack (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_improve_hex (hc, trackid, pid, name, side, nation, oid, orgname)
  • on_lay_mine_field (hc, trackid, pid, name, side, nation, oid, orgname)
  • on_mine_attack (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_next_phase (turn, side)
  • on_next_turn (turn)
  • on_objective_capture (hc, values, side)
  • on_resume ()
  • on_set_ied (hc, trackid, pid, name, side, nation, oid, orgname)
  • on_shutdown ()
  • on_startup ()
  • on_unit_arty_fire (hc, trackid, pid, name, side, nation, oid, orgname, strength)
  • on_unit_attack (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader, attype)
  • on_unit_clockwise (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_unit_counterclockwise (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_unit_fire (hc, trackid, pid, name, side, nation, oid, orgname, strength)
  • on_unit_kill (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_unit_merge (hc, trackid0, pid0, name0, side0, nation0, oid0, orgname0, points0, strength0, HQ0, Leader0, trackid1, pid1, name1, side1, nation1, oid1, orgname1, points1, strength1, HQ1, Leader1)
  • on_unit_move (hc_from, hc_to, trackid)
  • on_unit_reduce (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader, loss)
  • on_unit_reinforce (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_unit_release (trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_unit_remove (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_unit_to_top (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)
  • on_unit_to_bottom (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)

Compare this to how it was with Campaign Series: Middle East 2.0 and you’ll find there’s approximately three times the events now as compared to CSEE’s first iteration back in the day!

On Objective Capture

Let us pick perhaps an obvious one: on_objective_capture (hc, values, side). Here’s how it looks in the scenario lua file:

On Objective Capture

So what happens is that each and every time an objective changes hands in the scenario played, there’s – in this particular implementation – a 2-in-3 chance the player would get an encouragement for his brave deed. See here:

Objective taken – commendations!

Also, note the parameters you receive in this particular event to have a look at:

  1. What were the hex co-ordinates of the objective (“hc”)
  2. What was the value, in Victory Points, of said objective (“value”)
  3. Which side captured said objective (“side”)

With that knowledge, what else could take place? Well, anything!

  • Loss of an important objective might lower everyone’s Morale by 1 step,
  • Certain reserves might receive an order to counter attack the objective viciously to win it back, or
  • This might actually trigger the Scripted AI to revert from battle plan “A” to plan “B”, what ever that plan then is.

On Unit Kill

Another example: on_unit_kill (hc, trackid, pid, name, side, nation, oid, orgname, points, strength, HQ, Leader)

A more complex example, yet nothing too complex right? With HQ units in Campaign Series representing bot the C3 (command, control, communications) capabilities as well as logistics (logistic chain as well as handling the rate of consumption), it might be prudent that a loss of any of your HQs triggers an penalty. It could be an Event Points penalty, as the standard code snippet suggests, or in this case, depending how important your HQ was there’s loss to logistics in that the base ammo levels go down. Supply does not flow to your troops as efficiently anymore!

HQ lost – logistics take a hit!

Stay tuned for more CSEE under the covers!

To summarise, with all those event functions available to be triggered, as that particular event takes place in the game play, sky’s the limit to enrich the playing experience.

In my next blog, then, I will talk about how to access the Adaptive AI parameters from CSEE Lua code. Here’s how it was available in its first iteration with Campaign Series: Middle East 2.0. Effective, but quite cumbersome. Now: way much easier, and, adaptive to game events to top it off!

 

 

de Lattre’s Line #6: COMMANDOS NORD-VIETNAM

Campaign Series Vietnam | de Lattre's Line

Mes amis des jeux de guerre,

A French “Special Forces” was organized by General de Lattre in 1951. It was named “COMMANDOS NORD-VIETNAM.” This article provides more insight, and its relationship to the larger GCMA or Groupe Commandos Mixte Aeroporte, commanded by Colonel Roger Trinquier.

Origin of COMMANDOS NORD-VIETNAM

General de Lattre realized that a commando force was needed. He saw the need for unconventional forces, and wanted to improve equipment, weaponry, and living conditions for the indigeneous Vietnamese troops. Based on experience with Japanese resistance, and also that of the Marine and Dinassaut units, he wanted light units made up mainly of auxiliaries supervised by a few Europeans,  determined volunteers, specially trained in night and jungle combat, to strike at the Viet Minh, using their same methods. This was seen as a way to regain confidence of the Vietnamese people, of the “rice fields or the mountains,” to encourage them to return to French loyalty.

So, on 2 July, 1951, eight auxiliary commandos were created in North Vietnam. This was signed under “Decision N° 1546 / EMIFT / 1. (EMIFT =  État-Major Interarmées et des Forces Terrestres.) On 10 July,1951, this was increased to thirty, and later forty-five on 19 November, 1951.

(Decision N° 802 / EMIFT / 3 / SC)

Colonel Louis Fourcade was assigned as commander of the entire COMMANDOS NORD-VIETNAM. He was known as the “le grande Patron.” (Big Boss) Previously, Fourcade had in 1945 led Commando Conus, fighting in Cochinchina, Cambodia, and then in Laos. This unit was in liaison with Colonel de la Bollardière’s 1st SAS parachute brigade. Upon his return to Metropole in 1946, he commanded the GITCM Commando School in Frejus, France.

The GCMA airborne commandos (Groupe Commando Mixte Aéroporté,) were Vietnamese ethnic minorities or Laotian montagnard partisans led by paratrooper officers of the SDECE French intelligence agency. Colonel Roger Trinquier was the legendary leader of this rather large organization. Some of them would be used as cadres in COMMANDO NORD-VIETNAM. But, these were still two separate organizations. COMMANDO NORD-VIETNAM operated in the Tonkin Delta areas, and perhaps a little beyond. GCMA operated all over Indochina.

Insignia, COMMANDOS NORD-VIETNAM

Insignia, COMMANDOS NORD-VIETNAM

Organization Structure

Each “Commando” was a company sized unit, and numbered and named, for example, like Commando 24. Some of these were alternatively referred to by the commander name such as Commando “Rusconi.” Some commandos had nicknames, such as “Tigres Noirs,” or “Black Tigers.”

Leadership usually consisted of nine French soldiers, mostly from the “Parachutistes Coloniaux.” The commander was an officer or or Adjudant Chef or Adjudant  (warrant officer). Four NCOs would lead the sections, with one acting as the executive officer. Two junior ranks were radiomen, and two others were medics.

The remainder were indigenous troops, numbering up to 120 men per Commando. These troops were volunteers that come from companies of existing auxiliaries, or from militias in villages, or from young Vietnamese civilians. The auxiliaries or Légères de Supplétifs Militaires, (CLSM) were companies that formed the basis for many Commandos. These CLSM had typically served as garrison troops on the de Lattre line, but with additional training.

There were also former PIMs (Prisonniers et internés militaires) arrested as suspects during operations, preferring to fight rather than hang out as “coolies” in labor camps. Some commando leaders recruited former Viet Minh soldiers. These were often experienced guerilla fighters, but their loyalty was not always certain.

Mission Types

Commando units were organized, equipped, and trained for one of three mission types: Shock (Choc,)  Marine, and Guerilla.

‘Shock Commandos’ were reserves that carried out deep raids, with a view to destroying enemy bases, and the Viet Minh territorial organization. They disrupted logistics and reinforcements. They acted alone or in cooperation with mobile groups in large-scale operations (ARTOIS, GERFAUT, etc.)

The group of “Landing Commandos” or “Marines”, were called upon to work frequently in liaison with Navy formations for landing missions on the coasts or along the rivers and arroyos of the delta. (OPERATIONS GRASSE, ROCHEFORT, etc.)

.Finally, the group of so-called Zone Commandos, were oriented towards the search for intelligence, and the actions of “guerrilla – counter-guerrilla” warfare, mainly in their areas. They provided assistance for the Zone or Sector Commanders, helping with clean-up or sweeping operations.

Uniforms and Weapons

Combat uniforms were often French M47 uniforms or “black pajama uniforms,” with French army leather army boots, jungle boots called “pataugas,” or the civilian trainers called “baskets”. Head gear was black beret, (red beret was tolerated for paratroopers,) the French bush hat, (Le Chapeau de Brousse,) as well as Viet Minh helmets (sun hats) were often worn on operations.

The Commandos were lightly armed with Thompson, MAT 49, MAS 36, M1 carbine, and FM24/29 with sometimes a few 50 or 60mm Mortars. Radios were one SCR690, three to four SCR300, and  four to five SCR536 per Commando company.

Commando 9, Bac Ninh, North Vietnam

Commando 9, Bac Ninh, North Vietnam

Training

Given the diversity of recruitment, Col. Fourcade planned to involve “Commandos” in a training and cohesion course. Ecole de Vat Chay was set up for this purpose in 1951, with Capitaine Michel Legrand commanding. Operational requirements did not allow everyone to participate. New recruits were trained by their officers.

Marksmanship Training at Ecole Vat Chay

Marksmanship Training at Ecole Vat Chay

Commando 24 “Vandenberghe”

This was one of the more well-known Commandos and was one of the original eight formed in July 1951. Roger Vandenberghe, I’adjudant‐chef, (Chief Warrant Officer) organized this unit from the 11e CLSM. A precursor to this unit participated in the Day River Campaign at Ninh Binh.

Vandenberghe was born in Paris on October 27, 1927 in an extremely modest environment. His father suffered from turberculosis, and his mother, a Spanish Jew, struggled to support the family. With his brother, Vandenberghe was placed in a public boarding school, where he sometimes defied the authorities. In 1939, his father died, and in 1943, his mother was arrested by the Nazis.

Roger joined the Resistance, and was in a surveillance unit on the Franco-Spanish border. When WWII ended, he joined the French Army.  In January 1947, he embarked with the 49th Infantry Regiment, headed to Indochina. He was later assigned to the 10th Company, 6th Colonial Infantry Regiment. He rose to the rank of Sergeant and commanded a section of Vietnamese “suppletifs.”

In 1949, Vandenberghe was hit in the chest with a bullet, and repatriated to France. He survived and recovered. His actions earned the Knight of the Legion of Honour, at age 21. Returning to Indochina a few months later, he continued as section leader. Then in 1951, he was in the 5th Company of the 6th Colonial Regiment, stationed around Nam Dinh

Roger Vandenberghe, I'adjudant‐chef

Roger Vandenberghe, I’adjudant‐chef

Vandenberghe at Ninh Binh

At the time of the Viet Minh attack on Ninh Binh on 29 May 1951, the French were scrambling to get reinforcments into the battle. On 30 May, Vandenberghe’s reconnaissance group scouted for Groupe Mobile No 1, that retook the high crag south of Ninh Binh. This was when the body of Bernard de Lattre was found. He was the son of General de Lattre, and had commanded the 8th armored squadron of the 1er Regiment Chasseurs de Cheval.

Formation of Commando 24

Subsequent to the Day River Campaign, the 11e CLSM was reorganized by Vandenberghe, as Commando 24. Modeled on the “guerilla” type of units, they were trained and equipped for reconnaissance and covert operations. Their uniforms were similar to Viet Minh, so they could confuse the enemy.

Commando 24 on Patrol - Note similarity to Viet Minh Uniforms

Commando 24 on Patrol – Note similarity to Viet Minh Uniforms

In one mission into a deep enemy zone, Vandenberghe himself pretended to be a prisoner, and was led by his troops, disguised as Viet Minh, to openly march to a VM Commissar. The Viet Minh were too gullible, and at the right moment Commando 24 soldiers emerged and opened fire. They retrieved weapons and documents, including communications of an impending VM attack. This type of operation earned Commando 24 the name of “Tigres Noirs” or “Black Tigers.”

Commando 24 took part in the Hoa Binh Campaign in late 1951. They operated with Groupe Mobile No. 2, under Colonel Christian de Castries. (Later, the Dien Bien Phu Commander)

But, tragedy struck on the night of 5 January, 1952. Since former Viet Minh regulars were recruited as part of the Commando, occasional betrayal happened. At age 24, Roger Vandenberghe was murdered in his sleep by Nguien Tinh Khoi, former assault unit commander in the Viet Minh 36th Regiment.  Vandenberghe was posthumorously awarded yet another Croix de Guerre with palms.

Commando 24 Insignia Motto: "Tha Chet Hon La Chiu Nhuc" (Plutôt la mort que la honte) (Death before dishonor)

Commando 24 Insignia

Motto: “Tha Chet Hon La Chiu Nhuc”

(Plutôt la mort que la honte)

(Death before dishonor)

Commando 25 “Romary”

This unit was formed from the 170e CLSM, and initially commanded by Lt. Michel Romary. Organized as a Marine Commando, it participated in the Day River Campaign.

On 30 May, Commando 25 landed at Yen Cu Ha to reinforce the garrison there. This poste had been defended by Catholic Militia and Hung Yen partisans. On 5 June, the Viet Minh 88th Regiment attacked. Viet Minh gunners bludgeoned the position for two hours with “SKZ” (Sung Khong Zat: Chinese guns without recoil,) and mortars. This was also the first time they used WP, white phosphorus shells. Suicide sappers, called “death volunteers” undermined the walls with hollow loads,  and the general assault overwhelmed the position, but it changed hands four times.

As the handful of fighters, led by Lt. Romary (injured by two bullets and multiple shrapnel,) realized their desperate situation, LSSL No. 6 of Dinassaut “A” appears on the River Day, firing machine guns. This pushes the enemy back, and allows room for the reinforcements from 7BPC and 4/7RTA to land. The wounded Lt. Romary was later awarded the  Légion d’Honneur.

Lt. Romary awarded Legion of Honor by Gen. de Lattre

Lt. Romary awarded Legion of Honor by Gen. de Lattre

Lt. Besnard succeeded Lt. Romary as chef of Commando 25. This unit continued operations in the Tonkin delta region.

Lt. Besnard with Commando 25

Lt. Besnard with Commando 25

Commando 25 Insignia

Commando 25 Insignia

References

Commandos Nord Vietnam, A. Lebreton

http://archive.wikiwix.com/cache/index2.php?url=http%3A%2F%2Fwww.acuf.fr%2FArticle%2FCommandos%2520Nord%2520Vietnam.htm

COMMANDOS NORD-VIETNAM 1951-1954,  Jean-Pierre Pissardy, Casemate Publishers, 2003 (hardcopy only)

French Indochina Website

http://www.gia-vuc.com/indo/INDOCHINE%20commandos.htm

Héros de la guerre d’Indochine

http://unacitaistres.n.u.f.unblog.fr/files/2015/01/vandenberghe.pdf

Les Partisans et Supplétifs Website

https://indochinefrancaise.xooit.com/t601-Les-Partisans-et-Suppletifs.htm

Campaign Series Vietnam | de Lattre's Line

General Jean de Lattre de Tassigny


De Lattre’s Line is new series of articles by David Galster that covers the Day River Campaign of 1951 in Indochina. The articles provide some interesting background information for the upcoming release of Campaign Series: Vietnam.

.