Operation Absolute Resolve : Insertion & Extraction in Caracas

[Nikel]

Hi Nikel, thank you for the link and the detailed analysis. You are spot on regarding the operational doctrine. I've read the thread and I'm implementing your suggestions for the next hotfix/update:
​1. ARG Escort (The "Fireworks" Fix):
You are right, the LPD and Iwo Jima were too exposed. I am adding an Arleigh Burke DDG to the Amphibious Group for close protection.
​Technical Note: To solve the issue of the DDG engaging Venezuelan F-16s immediately upon scenario start (which ruins the infiltration phase), I will set the DDG's Air-WRA to "HOLD / Self-Defense". It will be there for ASW/ASuW protection, but won't start WW3 automatically unless the player authorizes it or it is fired upon.
​2. Tomahawks (TLAM) Removed:
Agreed. Using massive TLAM strikes trivializes the SEAD challenge. I have removed them from the magazines. This forces the player to rely on air power and the new drone tech, as discussed in the article.
​3. Project LUCAS (Drone Swarm):
Since the "LUCAS" system isn't in the DB, I'm following your advice. I'm adding 50x Shahed-136s (renamed as "LUCAS Swarm Payload") to the USS Iwo Jima.
​Tactical use: They will act as proxies for the swarming capability intended to saturate the Venezuelan S-300s. Do you think 50 units is a balanced number for the current IADS, or should I push for more?
​Thanks again for the feedback, it's really shaping the realism of the scenario! Wait for upload this night.

The number of available Shaheds is relative because there are more weapons to do the job, testing will tell

Regarding the automatic engaging of the Venezuelan ACs, is it not a good idea to create a bug report?

There is a never ending bark if you change WCS to hold.

NEB.gif (765.08 KiB) Viewed 290 times

[Knightpawn]

Regarding the automatic engaging of the Venezuelan ACs, is it not a good idea to create a bug report?

There is a never ending bark if you change WRA to hold.

I was thinking about reporting but I held back because I noticed that firing up was based on detection from IR sensors on the ships (no EMCON going active) and this my be WAD. Your suggestion of switching to unfriendly worked for me (hold works as well)

[Correcaminos]

Regarding the automatic engaging of the Venezuelan ACs, is it not a good idea to create a bug report?

There is a never ending bark if you change WRA to hold.

I was thinking about reporting but I held back because I noticed that firing up was based on detection from IR sensors on the ships (no EMCON going active) and this my be WAD. Your suggestion of switching to unfriendly worked for me (hold works as well)

Note on the Fleet: I am considering leaving the Iwo Jima group as is and keeping the USS Gerald R. Ford carrier strike group about 300nm away.

The reason is simple: if I move them closer, their automated defenses (RIM-66) become way too aggressive the moment the enemy status flips to "Hostile," wiping everything out before your planes even arrive and ruining the air combat experience. Even when forcing a "Weapons Hold," the spam of doctrine error messages in the log becomes unbearable. Using a trigger to change the status from "Unfriendly" to "Hostile" won't stop the fireworks either. If this "ignore doctrine" behavior gets fixed in the future, everything would be much easier, but in its current state, it's just a headache.

@knightpawn, could you upload an example of how you’ve configured it so I can take a look?

[Knightpawn]

@knightpawn, could you upload an example of how you’ve configured it so I can take a look?

I just start Venezuela as Unfriendly (i dont overcomplicate).
And considering the 21 hrs window now, I would position the IwoJima group away as the CVBG. It would be on the player to decide how close to approach and when

[Nikel]

Try this.

WCS (Air) Hold for the CSG.

And in the Options, map display, do not show barking.

I like the bark messages, but not if they are annoying.

[Correcaminos]

Try this.

WCS (Air) Hold for the CSG.

And in the Options, map display, do not show barking.

I like the bark messages, but not if they are annoying.

We have it, it works correctly, but wouldn't this affect performance? Keep in mind that it's still processing data internally about this issue every 5 seconds.




The Iwo Jima group is positioned 160nm from the coast so that the SSN Vermont can protect both groups and the player can decide from where to launch the helicopter operation

[Nikel]

We have it, it works correctly, but wouldn't this affect performance? Keep in mind that it's still processing data internally about this issue every 5 seconds.

What do you mean?

[Correcaminos]

I was initially worried that the AI constantly calculating firing solutions in the background (while on HOLD) might stress the CPU. But thinking about it, rendering all that "barking" text on the map and calculating the physics for dozens of missiles actually consumes way more resources than a simple logic check.

So, this solution should actually improve performance and keep the simulation smooth and the log clean.

[Nikel]

OK, yes I think the same.

[Correcaminos]

v1.95 Changelog - Operation Absolute Resolve

- Operational Freedom (Iwo Jima Group): The Iwo Jima Amphibious Ready Group (ARG) has been repositioned, allowing the player to decide the optimal starting point for helicopter operations. This adds a new layer of tactical planning regarding transit times and fuel management.

- Strict Air Operation Focus: Removed all Tomahawk (TLAM) cruise missiles to enforce a strictly aerial operation.

- Experimental LUCAS System: Added the LUCAS Swarm System (simulated via Shahed-136) to compensate for the lack of Tomahawks. Players must now use these swarming munitions to saturate enemy IADS.

- Escort Reinforcement: The USS Mason (DDG 87) has been officially added to the Iwo Jima ARG to provide realistic escort and sensor support.

- AAW Behavior Fix: Resolved the issue of escort ships spontaneously firing RIM-66 missiles at enemy aircraft. The fleet will now follow a stricter "Weapons Hold" doctrine, ensuring the mission remains focused on player-controlled air assets.

- Performance Optimization: Applied "Unit Behaviour Bark" silencing techniques to reduce log spam and improve simulation fluidity during high-intensity combat.

- HTML Briefing Overhaul: Completely restructured the briefing with a new visual layout, including technical identification of threats and high-resolution mission imagery.

- Description Update: Revised the scenario description to reflect the new 2026 timeline, logistics requirements, and updated fleet composition.

- Updated Credits: Special thanks to Knightpawn, Benefant, and Nikel for finalizing mission content, technical polish, and for their dedicated playtesting and feedback.

[Nikel]

Well, what can I say.

The LUCAS (Shaheds) are so slow, you have added so much stuff to the Venezuelan side that it is much more difficult now, instead of Maduro's compound, it looks more like Hitler's Wolfsschanze.

Where have my Tomahawks gone

Will try again.

[Nikel]

I do not know how, but managed to do the extraction with much of the Venezuelan stuff on the ground still intact, it was really engaging.

The scenario is completely different now.

the path used to infiltrate, that required more fuel for the Black-Hawks and 2 refuels.

S.png (64.66 KiB) Viewed 152 times

The Chinook alone and landed, before running away.

L.png (49.39 KiB) Viewed 161 times

Still the losses were too heavy for a successful operation. Disaster with -150 points due to the loss of 3 Black-Hawks, not for the fuel, but cleaning a path to the Chinook. Not a disaster for me as the mission was accomplished.

Note that you have added a lot of stuff and still the points are counted the same way.

Perhaps you should add/remove points per ship, AC,... for both sides?

Also consider rewriting the first screen that appears, becase you changed the name of the scenario and perhaps because the execution is not immediate (21 hs to go).

SIDE: VENEZUELA
===========================================================

LOSSES:
-------------------------------
1x C-802 Twin
1x F 21 Mariscal Sucre [Lupo]
4x F-16A Falcon
1x K-8W Karakorum
4x Peykaap III [Zolfaghar]
1x PO 11 Guaiqueri [Avante 2200 Combatant]
2x Radar (Bill Board B [9S15M Obzor])
1x Radar (China JY-27A)
1x Radar (China JYL-1)
2x Radar (High Screen B [9S19M2 Imbir])
4x Radar (Mys-M1E)
1x Radar (Snow Drift [9S18M1])
1x Radar (Spoon Rest D [P-18])
1x S 31 Sabalo [Type 209-1300]
2x SA-17 Grizzly [9A310M1-2] TELAR
1x SA-17 Grizzly [9A39M1-2] LLV
7x SA-23a Gladiator [9A83M] TELAR
2x SA-23a Gladiator [9A84] LLV
3x SA-23b Giant [9A82M] TELAR
2x SA-23b Giant [9A85] LLV
5x Su-30MK2 Flanker G
1x T 91 Los Frailes [Damen Stan Lander 5612]
1x Vehicle (Grill Pan [9S32M])


EXPENDITURES:
------------------
1x 30mm Gsh-30-1 Burst [30 rnds]
7x AA-11 Archer [R-73M1]
62x AA-12 Adder A [R-77, RVV-AE]
8x CSS-N-8 Saccade [YJ-83]
1x Generic Chaff Salvo [4x Cartridges]
8x Otomat Mk2 Mod I
15x Python 4
92x SA-17 Grizzly [9M317]
34x SA-23a Gladiator [9M83M]
18x SA-24 Grinch [9M342]
4x SST-4 Mod 0 Seeaal



SIDE: EEUU
===========================================================

LOSSES:
-------------------------------
1x B-1B Lancer
1x EA-18G Growler
8x F/A-18E Super Hornet Blk III
3x MH-60L Blackhawk DAP


EXPENDITURES:
------------------
2x 20mm/85 Mk15 Phalanx Blk 0 Burst [200 rnds]
24x AGM-114K Hellfire II
16x AGM-154A JSOW [145 x BLU-97/B Dual Purpose]
8x AGM-154C-1 JSOW [BROACH]
36x AGM-158B JASSM-ER
6x AGM-88E AARGM
45x AIM-120D AMRAAM P3I.4
1x AIM-9X Sidewinder
2x AN/ALE-55 FOTD
6x GBU-32(V)2/B JDAM [Mk83]
10x Generic Chaff Salvo [5x Cartridges]
1x Generic Chaff Salvo [8x Cartridges]
12x Generic Flare Salvo [3x Cartridges, Single Spectral]
103x HYDRA 70mm Rocket
16x Mk182 SRBOC Chaff [Seduction]
4x Mk48 Mod 7 ADCAP CBASS
8x RIM-156A SM-2ER Blk IV
22x RIM-174A ERAM SM-6 Blk I
10x RIM-174A ERAM SM-6 Blk I Dual I
8x RIM-174A ERAM SM-6 Blk IA Dual II
4x RIM-174A ERAM SM-6 Blk IB
1x RUM-139C VLA [Mk54]
5x Shahed-136
25x Shahed-136

[Correcaminos]

​Thanks for the insight. These were simple but necessary changes to tighten the scenario. I specifically added coastal radars and defenses, as well as infantry with automatic weapons at Fuerte Tiuna, because the target area felt a bit too "naked" before.
​A question on balance: I currently have the swarm set to 55 drones. How did that number feel during your run? I'm worried it might be too much (or too little) given the defenses.
​Also, I've received some feedback/criticism regarding the removal of Tomahawks and the addition of the "LUCAS" system. Some players feel it's unrealistic, but the article regarding the use of US loitering munitions in this specific theater really justifies the lore.
​I think I'm going to update the briefing one more time to include that link or a reference to it. Providing that context upfront should help clear up the confusion and explain why the TLAMs are gone.

[Nikel]

Sure, it is fun to destroy everything around with Tomahawks, I enjoyed doing it

The infiltration with the cavalry is then swift and easy.

But it is not realistic.

The drones where used in RL, even though it is a pain to use them in the scenario because they are slow.

I think there is now a lack of enough weapons to destroy all the stuff you have added to the Venezuelan side. Or perhaps I was bored of using the slow Shaheds, I did not use all of them.

This is the reason I decided to proceed with the infiltration even though it was risky, to my surprise it was successful even though 3 Black-Hawks were shot down.

What also happened in RL was some kind of cyber action that allowed the infiltration.

I do not know how this can be simulated through a special action.

I have also noticed this lua history message when you start the scenario.

Function:ScenEdit_DeleteUnit (0) Error:Can't find Unit 'S 32 Caribe [Type 209-1300]' on Side 'Venezuela'
El S 32 Caribe [Type 209-1300] no participará en esta misión.

[Correcaminos]

At the end of the day, this is a game and it should be accessible and fun.
​Here is the plan for the final version:
​The Tomahawks are back: I'm restoring them to the inventory. I’ll just add a note in the briefing saying they weren't used in the "real" operation due to collateral damage concerns, but as the Commander, you are free to play it your way. If you want to use drones, great; if you prefer to level the place with TLAMs to save your pilots, go for it! (The final score/log might actually note if you resorted to them, just for flavor).
​LUCAS Drones & Lore: I'm keeping the drones as they are, but I'll update the briefing with the link I found regarding their use in the theater. That should settle the "realism" debate—they are part of the 2026 lore now!
​Bug Squashing:
​Lua Error: Fixing the S-32 Caribe script (it was crashing because it tried to delete a unit that didn't spawn due to the 25% RNG).
​Geometry Crash: Fixing the issue Knightpawn reported with the patrol zones.
​I think this will wrap up Operation Absolute Resolve nicely. I want to leave this one polished and "closed" so I can shift 100% of my focus to the new, massive full-theater Venezuela scenario I'm building.
​Thanks for the push to make it more fun!

[Correcaminos]

CHANGELOG V1.96

[SCORING] Losing an escort helicopter now carries a -75 point penalty, emphasizing the value of aircrews and tactical caution.

[WEAPONS] Tomahawks Restored: The USS Gerald R. Ford now retains its full TLAM inventory. The Briefing has been rewritten to reflect that while High Command discourages their use (lore), the Mission Commander has full discretion to employ them if the tactical situation deteriorates.

[CONTENT] LUCAS Drones (Experimental): Added the LUCAS Swarm system (simulated via Shahed-136) to the USS Iwo Jima. The briefing now details their "Combat Evaluation" status and includes real-world intel on their presence in the theater.

[CONTENT] Narcotics Traffic: Added random "Narco-Subs" (LPV) and "Go-Fast" boats to the civilian traffic layer. These contacts require careful Positive Identification (PID).

[MAP] Unit Relocation: Relocated VENEZOLAN and other assets to improved starting positions to better align with the new mission flow.

[FIX] Fixed a geometry crash caused by a civilian aircraft's patrol zone.

[FIX] Fixed a Lua error where the random "S-32 Caribe" submarine script would fail if the unit didn't spawn.

[FIX] Randomization: Improved the randomization logic and "Teleport to Area" for enemy submarine patrols.

[UI] Briefing & Description: Overhauled the Scenario Description, Side Briefing (HTML) and Text Mission to reflect the new 21-hour timeline, the updated ROE, and the tactical context.

Special thanks to community members Knightpawn, Nikel, and Benefant for the critical logs and feedback.


I think it's time to create a worthy cover art for this mission after so much effort.