Matrix Games Forums

Hello!

When playing the tutorial scenario "Motozintla Incursion", I only saw enemy helicopters, no ground troops, even though they were supposed to invade over the border. Thinking I must have somehow just missed the enemy, I played the scenario again, changing the use of my assets. I still didn't see any enemy ground forces.

So I loaded the scenario in the editor to see what was happening.

The issue: Enemy ground forces do not take the (probably) intended route straight for their mission area across the mountains and the border. Instead they pathfind a wide circle around the entire mountain range (in an extreme "flanking" maneuver) and never end up in the AO within the scenario time limit.

I assume this must have to do with the changes in pathfinding calculations in CMO.

See the attached picture for the route the enemy takes to reach their mission area.

Cheers!

Logged for investigation.

0013589

ORIGINAL: altazure

Hello!

When playing the tutorial scenario "Motozintla Incursion", I only saw enemy helicopters, no ground troops, even though they were supposed to invade over the border. Thinking I must have somehow just missed the enemy, I played the scenario again, changing the use of my assets. I still didn't see any enemy ground forces.

So I loaded the scenario in the editor to see what was happening.

The issue: Enemy ground forces do not take the (probably) intended route straight for their mission area across the mountains and the border. Instead they pathfind a wide circle around the entire mountain range (in an extreme "flanking" maneuver) and never end up in the AO within the scenario time limit.

I assume this must have to do with the changes in pathfinding calculations in CMO.

See the attached picture for the route the enemy takes to reach their mission area.

Cheers!

Was going to post this as a bug but I see someone has already done it. From my screenshot you can see that the route the Guatemalan force takes is from the initial starting position (shown in the other screenshot in the original post), to the Gulf coast, and then later heads back down almost to the Pacific coast when the scenario ends. With terrain effects off I would think that the units shouldn't try to do this correct? Perhaps an additional doctrine setting could be made so that a ground unit will simply ignore terrain altogether and simply follow the straight line course to it's destination.

Hi, just wondering if this was fixed? I have played the scenario 6 times, my infantry become stuck, unable to move. Only 2 UH1 helicopters ever appear, so also no sign of any Guatemalan ground forces. Maybe I'm doing something wrong? Thank you.

Hi everyone,

I have a handy solution that requires minimal work in the mission editor. Once applied, simply save the template as is.

You need to open this mission up in scenario editor.

1. Switch to Guatemala side.
2. Remove the "incursion" mission. The Guatemalan ground troops are programmed to move towards 4-wp grid but seem to sacrifice their land movement calculations. The result is they reach unaccounted terrain elements that prohibit movement.
3. Create a single, waypoint, for each group (2) of Guatemalan ground forces. Select the waypoint, and ensure that the ground forces are weapons free for land targets, and also select engage opportunity targets to ON. The waypoint should be placed near the target village (near the Mexican marines).
4. Make sure the Guatemalan UNIT PROFICIENCY for both groups is selected at ACE. You could try Veteran, but ACE will cause the ground units to advance to their waypoint. Makes sense, you'd need elite troops to traverse mountains while under threat of air attack.
5. Add value "3" to "days" in the in-game timer. This will allow for the possibility of Guatemalan troops destroying the target. This will also increase the time to intercept the ground convoy, which will be programmed to take a long, circuitous route while utilizing the best terrain. It will eventually arrive if they are ACE in proficiency, and they will blow everything up!

Cheers!

Thank you for taking the time to post a solution Hector90, I will certainly try this now!

The attached updated file should fix the issue. We'll put this out with the next update [:)]

thanks very much, appreciated