TRIDENT BOREAL V3.0

Post new mods and scenarios here.

Moderator: MOD_Command

Nikel
Posts: 2627
Joined: Tue Mar 24, 2009 10:51 am

Re: TRIDENT BOREAL

Post by Nikel »

v2.7 tested in B1776 outside of the editor.




SPOILER ALERTS.




Major victory with 5175 points.


First time that could find and sink the Yasen-M russian sub, at the beginning in a ASW mission around Havis North-1.

The Nakhimov was also sunk the usual way, this is still too easy. I think they cannot defend themselves vs this barrage of LRASMs. Have you tried to switch sides and defend? They cannot, the missiles are detected too late and then an OODA loop. And gone.

The russian side is however much more active in attack in this version, specially the first hours. The air attacks destroyed most of the North Norway land installations and manage to sink one of the escort destroyers of the Ford CSG (I was not prepared for this), and some other minor ships.

As happened before, the Tu-22s then disappear of the scenario. Only persist the air fighter patrols in the Havis North area.


After the Yasen-M and the Nakhimov were sunk, there were still many hours ahead to try to stop the russian subs from crossing to the Atlantic. Only the blue subs remained in the North.

Diverted the Ford CSG, and the rest of the surface warships to hunt subs in the south, in their way they detected and sunk one of them (the Victor III class Obninks), but before the sub had time to sink the oiler and the Sachsen. In total 3 ships of the Ford CSG were sunk in this testing.

Later was also attacked the carrier Queen Elisabeth by the Tula, a delta IV class sub, the carrier survived the scenario but one of the torpedos impacted, destroying most of the air wing of the carrier :shock:

When there were still 5h left of the scenario, the sub message appeared on the screen, meaning that the scenario was in fact a defeat. I think that to avoid it, more ASW Poseidons are needed, but not in Norway, in Iceland.


Run the scenario to the end just destroying some radars with Tomahawks, in this version it is more difficult due to terrain, setting ticked that was not before, this is a realistic change.

TT.png
TT.png (31.04 KiB) Viewed 205 times



The scoring mechanism works ;) Points are assigned for radars, ships and subs. Not only ACs.

This is the scoring log along the scenario with the main events.

SL.png
SL.png (46.33 KiB) Viewed 205 times


The CSAR mechanism is mainly working :) You only receive messages of survivors from your own side. Points are assigned with messages on the screen, +25 for success and -75 for failure. You have to hover at low altitude with a helicopter, pickup does not work. This should be explained in the briefing as designer notes or someway.

CSAR.png
CSAR.png (12.48 KiB) Viewed 205 times

What is unrealistic is that only ACs generate them. When a ship is sunk, it will generate survivors but only for the crew of ACs in the ship. What happens with the officers and sailors :)

And when the QE was torpedoed many survivors messages appeared by each AC destroyed, however there were none of them on the map, so could not rescue them.

There are no losses generated for them as you see at the bottom, perhaps because only messages appeared, not the survivors themselves on the map.

I do not know if you want to mess more with this. Perhaps to simplify things only the ACs that are airborne should generate survivors to avoid these problems. No idea if this can be done.


LuaHistory file messages still appearing though.

...
Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!
Exception: [string "CachedChunk"]:10: attempt to call a nil value (global 'ScenEdit_SetUnitSensor')
Stack Trace: at NLua.Lua.ThrowExceptionFromError(Int32 oldTop)
at NLua.Lua.CallFunction(Object function, Object[] args, Type[] returnTypes)
at NLua.LuaFunction.Call(Object[] args)
at Adfs2QqMGUifo0Ac7CVE.qLd8ynxTUEn(Object , Object[] , Adfs2QqMGUifo0Ac7CVE )
at Command_Core.LuaUtility.DoString_Optimized(Lua lua, String chunk, String chunkName)
at Command_Core.Lua.LuaSandBox.RunScript(String str, Boolean RunInteractively, String script, String fullPath)

...
Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!
...
Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!
...
Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!


AS OF: 13-Feb-27 10:00:34

SIDE: NATO
===========================================================

LOSSES:
-------------------------------
1x A/C Hardened Aircraft Shelter (1x Large Aircraft)
2x Bunker (COMINT Station)
1x Bunker (ELINT Station)
1x Bunker (Large C3M)
1x Bunker (SIGINT Station)
1x DDG 125 Jack H. Lucas [Arleigh Burke Flight III]
1x E-2D Advanced Hawkeye
2x EA-18G Growler
1x F 219 Sachsen [Type F124]
1x F 310 Fridtjof Nansen
1x F-22A Raptor
7x F-35B Lightning II
1x Marjata [3rd]
2x Merlin ASaC.5 [Crowsnest]
2x Merlin HC.4
1x Merlin HM.2
3x MH-60R Seahawk
2x MH-60R Seahawk
1x MQ-8C Fire Scout UAV
6x NASAMS III
10x Naval Strike Missile (NSM) Truck
1x NH90 NFH
1x NH90 NFH [Caiman Marine]
3x Patriot M901
2x Patriot M901
1x Radar (AN/FPS-110)
1x Radar (AN/FPS-6A HF)
3x Radar (Coastal ACSR)
1x Radar (GLOBUS II [AN/FPS-129 Have Stare])
1x Radar (HADR SINDRE I)
2x Radar (RAT-31SL/N SINDRE II)
1x Radar (RAT-31SL/N)
1x T-AOE 6 Supply
3x Vehicle (AN/MPQ-64F1 Sentinel [NASAMS II])
1x Vehicle (AN/MPQ-65)
1x W 310 Jan Mayen [Pr.6615]


EXPENDITURES:
------------------
4x 20mm/100 Mk15 Phalanx Blk 1B Burst [300 rnds]
12x 20mm/85 M61A2 Vulcan Burst [100 rnds]
1x 57mm/70 Bofors Mk3 GP Burst [4 rnds]
68x AGM-158C LRASM
79x AIM-120D AMRAAM P3I.4
1x AIM-132A ASRAAM
5x AIM-9X-3 Sidewinder Blk II+
14x AMRAAM-ER
9x AN/SSQ-36 BT
90x AN/SSQ-53F DIFAR
59x AN/SSQ-62E DICASS
2x F21 Artemis
3x Generic Flare Salvo [3x Cartridges, Dual Spectral]
16x Meteor
12x MIM-104E Patriot PAC-2 GEM+
16x MIM-104F Patriot PAC-3 MSE
20x Mk214 Sea Gnat Chaff [Seduction]
12x Mk234 Nulka
2x Mk46 NEARTIP Mod 5A(S)
4x Mk48 Mod 7 ADCAP CBASS
6x Mk59 Mod 0 Floating Decoy
2x RGM-184A NSM Block 1
54x RIM-162A ESSM
11x RIM-174A ERAM SM-6 Blk I Dual I
8x RIM-174A ERAM SM-6 Blk IA Dual II
1x Saab Lightweight Torpedo
249x SSQ-926 ALFEA
134x SSQ-955 HIDAR DIFAR
79x SSQ-963D CAMBS VI
2x Stingray Mod 1
71x TSM 8050B Active RO
72x TSM 8062 DIFAR
24x UGM-109E Tomahawk Blk IV TACTOM



SIDE: RUSSIA
===========================================================

LOSSES:
-------------------------------
1x BPK Marshal Shaposhnikov Udaloy I [Pr.1155 Fregat]
5x Ka-27PL Helix A
3x Ka-31 Helix
1x MPK Gremyashchy [Pr.20385, Improved Steregushchiy]
2x MRK Smerch Nanuchka III [Pr.1234.2]
2x MRK Uragan [Pr.22800 Karakurt]
1x PLA-671RTMK Victor III [Shchuka]
1x PLA-885M Severodvinsk [Yasen-M]
1x PLARB-667BDRM Delta IV [Delfin]
1x Radar (P-70)
2x Radar (Spoon Rest C [P-12])
4x Radar (Thin Skin A HF [PRV-9])
1x RKR Admiral Nakhimov [Pr.1144.2 Orlan, Ex-Kalinin]
1x RKR Slava [Pr.1164 Atlant]
2x SKR Admiral Sergey Gorshkov [Pr.2235.0]
1x SSV Vishnya [Pr.864 Meridian]
4x Su-34M Fullback
5x Su-35K Flanker E
2x Su-57 Felon
2x Su-57 Felon
1x Tu-95RTs Bear D


EXPENDITURES:
------------------
5x 100mm/59 A-190 Frag
15x 130mm/54 A-192 Frag
7x 23mm Gsh-6-23 [50 rnds]
1x 30mm Gsh-30-1 Burst [30 rnds]
4x 30mm Twin Gatling Gsh-6-30K Burst [375 rnds]
4x 30mm Twin Gatling Gsh-6-30KD [375 rnds]
8x AA-11 Archer [R-74M]
5x AA-11 Archer [R-74M2]
5x AA-12 Adder C [R-77M]
50x AA-13 Arrow [R-37M, RVV-BD]
5x AK-130 130mm/54 Twin Frag Burst [2 rnds]
4x AK-630M 30mm/65 Gatling Burst [400 rnds]
4x AS-11 Kilter [Kh-58UShK, ARM, Semi-Ballistic]
1x AS-17 Krypton C [Kh-31P, ARM]
22x AS-4 Kitchen D [Kh-32]
8x Generic Acoustic Decoy
18x Generic Chaff Salvo [4x Cartridges]
6x Generic Chaff Salvo [5x Cartridges]
5x Generic Chaff Salvo [8x Cartridges]
74x PK-10 Flare [SO-50]
6x PK-16 Flare [TST-60U]
5x RGB-1 [NATO BM-1, Search, Passive Omni]
126x SA-21b Growler [40N6]
23x SA-28 [9M96D]
44x SA-N-21d Growler [9M96D]
4x SA-N-24 Grinch [9M342]
16x SS-N-12 Sandbox Mod 1 [P-500 Bazalt]
2x SS-N-19 Shipwreck [P-700 Granit]
4x SS-N-25 Switchblade [Kh-35 Uran] GLONASS
8x SS-N-26 Strobile [P-800 Onyx]
16x SS-N-27 Sizzler [3M54T Kalibr, Rocket Boosted Penetrator]
15x SS-N-27 Sizzler [3M54T Kalibr]
12x SS-N-30A Sagaris [3M14 Kalibr]
40x SS-N-33 [3M22 Zircon]
12x USET-80K



SIDE: CIVILIAN
===========================================================

LOSSES:
-------------------------------
1x Commercial Container Vessel - Post Panamax [9,500 TEU, 105,000t DWT]


EXPENDITURES:
------------------



SIDE: NATURE
===========================================================

LOSSES:
-------------------------------
1x Biologic Baleen Whale
2x Biologic Fish School


EXPENDITURES:
------------------



SIDE: Survivors
===========================================================

LOSSES:
-------------------------------


EXPENDITURES:
------------------
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL

Post by Correcaminos »

Great news and thank you very much for the v2.7 report! With this, I can confirm that the scoring system and the core engine are finally working as intended. The hardest part is behind us, hehe.
​Regarding your comments, here is what I am not changing and what I will implement for the next version:
​1. The Nakhimov and the LRASMs
You are absolutely right, right now they don't have enough reaction time. I am going to add Udaloy-class destroyers (I love this ship!) to the vanguard to act as a defensive screen and radar picket. By the way, since you know your stuff: do you have any specific suggestions on how to tweak their doctrine or WRA to make them more effective at intercepting stealthy missiles?
​2. The disappearing Tu-22M3s
Noted. I am going to reconfigure the logistics and orders to create attack missions in multiple waves. This way, the threat from Kola will be constant throughout the hours, and not just one initial strike.
​3. The CSAR system and ship survivors
I'm glad the core mechanic is working well. Regarding survivors from ships (sailors, officers...): I am not going to change it. It would be crazy for the game engine and the map to generate dozens of survivor units every time a large ship or the Queen Elizabeth sinks. As long as it generates downed pilots, that's enough to give it that strategic touch. I might just tweak the names of the generated units for better immersion, but the mechanics will stay as they are.
​4. ASW and the GIUK Gap
This is a simple issue to fix. My goal is to give all the tactical spotlight to the aircraft carriers, so I will add more models of the drone I mentioned before (the MQ-9B SeaGuardian STOL) to the carrier groups, along with their helicopters. Even so, I'll take your advice on Iceland to have a backup plan: I'll put 1 P-8 Poseidon operating from there and leave another one at the base in Readying status.
​5. The "Nature" side
Easy, I am going to remove the Nature side from the penalty scoring script. Greenpeace will be very grateful that we no longer lose points for sinking poor whales in the crossfire.
​I think the scenario is turning out quite well and highly polished thanks to your testing. The hardest part is already set up and working. I'll let you know as soon as the next version is up!
"Si vis pacem, para bellum."
Nikel
Posts: 2627
Joined: Tue Mar 24, 2009 10:51 am

Re: TRIDENT BOREAL

Post by Nikel »

Correcaminos wrote: Mon Feb 23, 2026 2:08 pm
​1. The Nakhimov and the LRASMs
You are absolutely right, right now they don't have enough reaction time. I am going to add Udaloy-class destroyers (I love this ship!) to the vanguard to act as a defensive screen and radar picket. By the way, since you know your stuff: do you have any specific suggestions on how to tweak their doctrine or WRA to make them more effective at intercepting stealthy missiles?

​3. The CSAR system and ship survivors
I'm glad the core mechanic is working well. Regarding survivors from ships (sailors, officers...): I am not going to change it. It would be crazy for the game engine and the map to generate dozens of survivor units every time a large ship or the Queen Elizabeth sinks. As long as it generates downed pilots, that's enough to give it that strategic touch. I might just tweak the names of the generated units for better immersion, but the mechanics will stay as they are.

​4. ASW and the GIUK Gap
This is a simple issue to fix. My goal is to give all the tactical spotlight to the aircraft carriers, so I will add more models of the drone I mentioned before (the MQ-9B SeaGuardian STOL) to the carrier groups, along with their helicopters. Even so, I'll take your advice on Iceland to have a backup plan: I'll put 1 P-8 Poseidon operating from there and leave another one at the base in Readying status.

1. I do not know my stuff, this is a question for Knightpawn and for blu3s :)

3. Crazy, for that reason I suggested that only ACs that are airborne generate survivors, if it can be done.

4. Note that there are 2 Poseidons in Evenes AB that cannot detect subs.
Knightpawn
Posts: 461
Joined: Mon Dec 02, 2024 12:28 pm

Re: TRIDENT BOREAL

Post by Knightpawn »

Nikel wrote: Mon Feb 23, 2026 3:01 pm
1. I do not know my stuff, this is a question for Knightpawn and for blu3s :) .
In all honesty the lesson I draw from this scenario is that contemporary US weaponry is too advanced for Russian surface platforms to counter. It is not only the ships. My F35 were able to kill the Russian CaP with their radars off with the AWACS doing the targeting for their Aim120D.

And the scenario is a good illustration of this technology gap.
Nikel
Posts: 2627
Joined: Tue Mar 24, 2009 10:51 am

Re: TRIDENT BOREAL

Post by Nikel »

The Nakhimov is armed with many long range SA-N-20a (Gargoyle).

If you try to manual engage with them one of the B-1B bombers, you have the red text "No directors are able to illuminate..."

However in the properties of the missile it is said "Illuminate at launch". What does it mean?

NDI.png
NDI.png (50.3 KiB) Viewed 153 times
GP.png
GP.png (51.39 KiB) Viewed 153 times
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL

Post by Correcaminos »

Knightpawn wrote: Mon Feb 23, 2026 4:07 pm
Nikel wrote: Mon Feb 23, 2026 3:01 pm
1. I do not know my stuff, this is a question for Knightpawn and for blu3s :) .
In all honesty the lesson I draw from this scenario is that contemporary US weaponry is too advanced for Russian surface platforms to counter. It is not only the ships. My F35 were able to kill the Russian CaP with their radars off with the AWACS doing the targeting for their Aim120D.

And the scenario is a good illustration of this technology gap.
Let's build the Russian "bastion" in the Bear Gap then. The Motherland's fleet from the Kola Peninsula Sea must set sail.
"Si vis pacem, para bellum."
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL

Post by Correcaminos »

Nikel wrote: Mon Feb 23, 2026 4:59 pm The Nakhimov is armed with many long range SA-N-20a (Gargoyle).

If you try to manual engage with them one of the B-1B bombers, you have the red text "No directors are able to illuminate..."

However in the properties of the missile it is said "Illuminate at launch". What does it mean?


NDI.pngGP.png
1. Radar Horizon: The B-1B is specifically designed for very low-altitude penetration. The radar waves of the 30N6-1 FCR do not curve with the Earth; if the bomber is flying "on the deck", it remains hidden below the radar horizon. Without a direct Line of Sight (LOS), the ship simply cannot illuminate it.

2. Firing Arcs (Blind spots): In reality, the massive funnels and masts on the ship's superstructure create blind spots. However, as you correctly pointed out from the database, in CMO the system is assigned full 360º coverage, so we can rule out this technical factor in the simulator.

3. Radar Status and Guidance Type: Is the 30N6-1 FCR actually transmitting? Unlike other weapons that fly to pre-set coordinates (fire-and-forget), the SA-N-20a missile requires continuous, direct illumination of the target from the exact moment of launch ("Illuminate at launch"). If the ship is under EMCON conditions (radars off), the launch sequence is blocked by the combat system.
"Si vis pacem, para bellum."
Nikel
Posts: 2627
Joined: Tue Mar 24, 2009 10:51 am

Re: TRIDENT BOREAL

Post by Nikel »

1. But the B1-B is a strategic bomber, they launch the missiles at 11000 m.

3. The Tombstone radars, 2 of them In the Nakhimov, both active, and still red message.
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL

Post by Correcaminos »

The B-1B isn't just a bomb truck; it's an absolute electronic warfare beast. It's loaded with jammers and is spitting a ton of electromagnetic "noise" at your ship. Yeah, your radars know the plane is up there, but they are so blinded by the interference that they can't get a clean enough lock to guide the SA-N-20a missile. You're going to have to let the bomber get closer until your radar's power manages to punch through that wall of noise (what the game calls burn-through).
"Si vis pacem, para bellum."
Nikel
Posts: 2627
Joined: Tue Mar 24, 2009 10:51 am

Re: TRIDENT BOREAL

Post by Nikel »

The problem is that it will not get near, LRASM is long range, 220 nm :)

And the missiles themselves have defensive and offensive ECM.

The russians need wonder weapons and sensors.
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL

Post by Correcaminos »

CHANGELOG V2.9
Scoring System: LUA engine rebalanced to 8500 points for victory.

ROE Penalties: Strict negative points for civilian collateral damage (-1000 for ships, -500 for aircraft).

Russian Bastion: ACTIVATED. Integration of next-generation surface units and submarines.

Russian Air Defenses & Operations: Tier 1 SAM reinforcements and full mission configuration for OECM, Recon, AEW, CAPs, and Tankers.

Balance of Power: Adjusted the total number of Russian aircraft to ensure a balanced and realistic challenge.

SAR Event: Fixed. Survival logic enabled only for air units; ships will no longer generate survivors or pilots.

NATO Deployment: Added P-8 Poseidon support in Iceland and new UAV detachments on the HMS Queen Elizabeth and Charles de Gaulle.

FINAL NOTE: If this Bastion doesn't stop NATO, in the next version I'll grant a reconnaissance satellite to each side... or simply activate the nuclear silos. :D :evil:
"Si vis pacem, para bellum."
Lakeend
Posts: 20
Joined: Thu Oct 31, 2024 9:35 am

Re: TRIDENT BOREAL

Post by Lakeend »

Correcaminos wrote: Mon Feb 23, 2026 10:26 pm CHANGELOG V2.9
Scoring System: LUA engine rebalanced to 8500 points for victory.

ROE Penalties: Strict negative points for civilian collateral damage (-1000 for ships, -500 for aircraft).

Russian Bastion: ACTIVATED. Integration of next-generation surface units and submarines.

Russian Air Defenses & Operations: Tier 1 SAM reinforcements and full mission configuration for OECM, Recon, AEW, CAPs, and Tankers.

Balance of Power: Adjusted the total number of Russian aircraft to ensure a balanced and realistic challenge.

SAR Event: Fixed. Survival logic enabled only for air units; ships will no longer generate survivors or pilots.

NATO Deployment: Added P-8 Poseidon support in Iceland and new UAV detachments on the HMS Queen Elizabeth and Charles de Gaulle.

FINAL NOTE: If this Bastion doesn't stop NATO, in the next version I'll grant a reconnaissance satellite to each side... or simply activate the nuclear silos. :D :evil:
I am getting lot of these dialog popups that pause the game and hide somewhere in the background:
Screenshot 2026-02-24 155129.png
Screenshot 2026-02-24 155129.png (13.62 KiB) Viewed 78 times
These are pretty annoying, had to alt+f4 my CMO first time because I didnt realize this was hiding behind all my windows and was preventing me unpausing the game.
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL

Post by Correcaminos »

That is an internal message from the AI mission planner. If you are playing as NATO and you are seeing Russian mission names like 'Alpha strike', it's because you have the option to see enemy messages enabled.
"Si vis pacem, para bellum."
Nikel
Posts: 2627
Joined: Tue Mar 24, 2009 10:51 am

Re: TRIDENT BOREAL

Post by Nikel »

v2.9 tested in B1776, outside of the editor.

There is something you changed in this version of the scenario that slows down the simulation. Have you noticed it? It improved a lot when there were left around10h of scenario.

Probably due to the civilian side, huge log file is created with countless lines like this:
12-Feb-27 23:45:00 - [CIVILIAN] Updating data for contact: A/C Hardened Aircraft Shelter (1x Medium Aircraft), based on new information by: FV Fishing Zone E #6. Updated info includes: BDA data.
Did you changed something in the civilian side? Those lines were not present in previous tests and the size of the log was normal.

Also the saves are huger.




SPOILER ALERTS.





Total disaster with -31625 points :shock:

I was completely defeated this time: Yasen-M not found, subs crossed to the Atlantic even with the Poseidons on Iceland that could cover the gap between Greenland and Iceland; and what is worse, the Ford CSG completely wiped out :(

Several errors committed, and I paid for them.


The initial bombers attack destroyed the land installations in N Norway like before. However this time also sunk most of the escorts of the Ford and the oiler. The carrier herself was severely mauled, only the Álvaro de Bazán survived the slaughter.

Both were retreated to the W, but at very slow speed, the carrier could not move faster to run away, and the runway was damaged enough to be useless. I had prepared a CAP and several group of fighters in Norway, but it was not enough for the Kinzhals and the rest of the weapons launched.

RD.png
RD.png (62.01 KiB) Viewed 68 times


The North was conceded to the russian side, except for the blue subs, that tried to find the Yasen-M along the scenario, but failed. It seems that if you do not find it at the beginning of the scenario with helos from the Marjata, you will never do it.


It was now the turn of my own bombers, and when the Nakhimov and most of the russian fleet was located, the B1-Bs were prepared. The error is to use the automatic engage button that will launch too many missiles to a single target or spend them in less important targets. The case is that I could not sink her at the first try. There are 2 other bombers damaged that will become available later in the scenario, so I had to wait.

The Tomahawks multi-mission can also attack the Nakhimov and the russian surface ships, but the red side can defend vs them, contrary to the LRASMs.


Some hours passed, some russian subs were detected trying to cross and were destroyed.

The damaged bombers finally became available and this time used the LSASMs better, sinking most of the russian surface fleet. As they are not able to defend properly, you do not need to spend too many in each ship.

After this success, I thought I could recover in the scenario if the Yasen-M was found.

But I was wrong, never was found in several hours. The Virginia class sub Oklahoma was sunk, the first time, perhaps was the Yasen-M, I do not even know it.


And something happened that did not happen before, the russian bombers reappeared at the end of the scenario. I was not prepared for this, could have deployed a CAP of Rafales and F-35s from the French and British carriers, but did not think about it. The red bombers destroyed and sunk the carrier Ford with all the air wing, and the Álvaro de Bazán.

Seeking revenge, too late launched the Rafales and F-35s to shoot down the bombers, but they were too far away and could not arrive in time even after refueling. So the revenge was done by some fighters still available from Norway, the Tu-22M were destroyed.

And the final blow was the sub crossing event.


Errors committed:

- Too small CAP covering the Ford at the beginning of the scenario.

- LRASMs from B1-B bombers, must be used manually, few of them per ships are enough, even though you can retarget them after launched.

- Patience with your own subs, flank speed is not a good idea to arrive to a point trying to get to targets

- The risks only end when the scenario ends :)


This is an excellent scenario, even with the Ford mauled I could have won, but ended in total disaster. Thanks Correcaminos :)





Some problems and suggestions, beside the slowing down of the simulation and lua errors listed below:

- This time, the survivors was an annoyance, centered in the rest of the scenario I did not pay much attention, remove it completely? It is still causing errors.

SGS.png
SGS.png (63.63 KiB) Viewed 67 times


- CAMM weapon cannot be fired, datalink missed (Visby corvettes). You can add it (see thread below), or use other ships. This db error was not fixed apparently.

https://forums.matrixgames.com/viewtopi ... 8#p5196458


- I think no points were lost when the Oklahoma was sunk.

- When the bombers were destroyed in the final and futile revenge, they were not escorted.

- I commented this before, the ACs names are mixed in the AC operations and in the scoring log. In the scoring log is better the type of AC not the callsign, how is this done?

Name.png
Name.png (38.55 KiB) Viewed 64 times


- Add points for avoiding the russian sub crossing event at the end. I never managed to avoid it, perhaps you have already added the points :)

- It is a good idea the losing of -10000 points per carrier sunk instead of ending the scenario (I was going to suggest this), the pain is even greater :lol:

- The scoring is still wrong comparing ACs and ships, too much for the ACs. Example -500 points for the Álvaro de Bazán and -400 for a single Super Hornet.

- The fighters diverted to other bases in Norway will become unavailable, perhaps is intended?











Scoring log with the main events.

SL2.9.png
SL2.9.png (49.31 KiB) Viewed 70 times



The errors in the Luahistory file still appear.

Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!
Exception: [string "CachedChunk"]:10: attempt to call a nil value (global 'ScenEdit_SetUnitSensor')
Stack Trace: at NLua.Lua.ThrowExceptionFromError(Int32 oldTop)
at NLua.Lua.CallFunction(Object function, Object[] args, Type[] returnTypes)
at NLua.LuaFunction.Call(Object[] args)
at Adfs2QqMGUifo0Ac7CVE.qLd8ynxTUEn(Object , Object[] , Adfs2QqMGUifo0Ac7CVE )
at Command_Core.LuaUtility.DoString_Optimized(Lua lua, String chunk, String chunkName)
at Command_Core.Lua.LuaSandBox.RunScript(String str, Boolean RunInteractively, String script, String fullPath)

...
Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!
...
Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!



AS OF: 13-Feb-27 10:00:06

SIDE: NATO
===========================================================

LOSSES:
-------------------------------
4x A/C Hardened Aircraft Shelter (1x Large Aircraft)
6x A/C Hardened Aircraft Shelter (1x Medium Aircraft)
1x AW.101 Merlin Mk.512 SAR Queen
2x Bell 412SP
3x CMV-22B Osprey
1x CVN 78 Gerald R. Ford
2x DDG 125 Jack H. Lucas [Arleigh Burke Flight III]
5x E-2D Advanced Hawkeye
6x EA-18G Growler
1x F 101 Alvaro De Bazan
1x F 219 Sachsen [Type F124]
3x F 310 Fridtjof Nansen
14x F/A-18E Super Hornet Blk III
14x F-35C Lightning II
2x KC-46A Pegasus [KC-767B]
1x Marjata [3rd]
13x MH-60R Seahawk
2x MH-60R Seahawk
6x MQ-25A Stingray UAV
1x MQ-4C Triton UAV
1x MQ-8C Fire Scout UAV
3x MQ-8C Fire Scout UAV
2x NASAMS III
9x Naval Strike Missile (NSM) Truck
1x NH90 NFH
2x NH90 NFH [Caiman Marine]
1x P-8A Poseidon
1x P-8A Poseidon
2x Patriot M901
1x Radar (AN/FPS-110)
1x Radar (AN/FPS-6A HF)
3x Radar (Coastal ACSR)
1x Radar (GLOBUS II [AN/FPS-129 Have Stare])
2x Radar (HADR SINDRE I)
2x Radar (RAT-31SL/N SINDRE II)
1x Radar (RAT-31SL/N)
1x SSN 802 Oklahoma [Virginia Class, Flight V]
1x T-AOE 6 Supply
1x Vehicle (AN/MPQ-64F1 Sentinel [NASAMS II])
1x Vehicle (AN/MPQ-65)
1x W 310 Jan Mayen [Pr.6615]


EXPENDITURES:
------------------
4x 127mm/54 HE-CVT [HiFrag]
8x 20mm/100 Mk15 Phalanx Blk 1B Burst [300 rnds]
4x 27mm MLG-27 Burst [20 rnds]
21x 57mm/70 Bofors Mk3 GP Burst [4 rnds]
16x 76mm/62 Super Rapido HE Burst [2 rnds]
86x AGM-158C LRASM
7x AIM-120B AMRAAM
90x AIM-120D AMRAAM P3I.4
12x AIM-132A ASRAAM
7x AIM-9X-3 Sidewinder Blk II+
20x AMRAAM-ER
9x AN/SSQ-36 BT
111x AN/SSQ-53F DIFAR
9x AN/SSQ-62D DICASS
98x AN/SSQ-62E DICASS
70x AN/SSQ-77B VLAD
18x Bullfighter Chaff/Flare Seduction
4x F21 Artemis
1x Generic Chaff Salvo [5x Cartridges]
2x Generic Flare Salvo [3x Cartridges, Dual Spectral]
42x Meteor
24x MIM-104E Patriot PAC-2 GEM+
18x MIM-104F Patriot PAC-3 MSE
44x Mk214 Sea Gnat Chaff [Seduction]
26x Mk234 Nulka
2x Mk48 Mod 7 ADCAP CBASS
8x Mk59 Mod 0 Floating Decoy
21x RIM-116C RAM Blk II
79x RIM-162A ESSM
6x RIM-162B ESSM
16x RIM-162D ESSM
16x RIM-174A ERAM SM-6 Blk I Dual I
16x RIM-174A ERAM SM-6 Blk IA Dual II
49x RIM-66M-2 SM-2MR Blk IIIA
1x RIM-66M-5 SM-2MR Blk IIIB
2x Spearfish Mod 1
219x SSQ-926 ALFEA
163x SSQ-955 HIDAR DIFAR
75x SSQ-963D CAMBS VI
4x Stingray Mod 1
67x TSM 8050B Active RO
90x TSM 8062 DIFAR
36x UGM-109E Tomahawk Blk IV TACTOM
52x UGM-109J Tomahawk Blk Va MST



SIDE: RUSSIA
===========================================================

LOSSES:
-------------------------------
3x BPK Marshal Shaposhnikov Udaloy I [Pr.1155 Fregat]
5x Ka-27PL Helix A
3x Ka-31 Helix
1x MPK Gremyashchy [Pr.20385, Improved Steregushchiy]
2x MRK Buyan Mod [Pr.21631 Buyan-M]
3x MRK Shkval [Pr.22800 Karakurt]
2x MRK Smerch Nanuchka III [Pr.1234.2]
2x MRK Uragan [Pr.22800 Karakurt]
1x PLARB-667BDRM Delta IV [Delfin]
1x PLARK-949AM Oscar III [Antey]
1x Radar (P-70)
1x Radar (Spoon Rest C [P-12])
3x Radar (Thin Skin A HF [PRV-9])
1x RKR Admiral Nakhimov [Pr.1144.2 Orlan, Ex-Kalinin]
1x RKR Slava [Pr.1164 Atlant]
2x SKR Admiral Sergey Gorshkov [Pr.2235.0]
1x SSV Vishnya [Pr.864 Meridian]
10x Su-34M Fullback
2x Su-35S Flanker M
1x Tu-142A Bear F Mod 1
8x Tu-22M-3M Backfire C
2x Tu-95RTs Bear D


EXPENDITURES:
------------------
22x 100mm/59 A-190 Frag
8x 130mm/54 A-192 Frag
3x 23mm Gsh-6-23 [50 rnds]
21x 30mm Gsh-30-1 Burst [30 rnds]
3x 30mm Twin Gatling Gsh-6-30K Burst [375 rnds]
10x 30mm Twin Gatling Gsh-6-30KD [375 rnds]
4x AA-10 Alamo A [R-27R, MR TSARH]
3x AA-11 Archer [R-73]
8x AA-11 Archer [R-74M]
3x AA-11 Archer [R-74M2]
23x AA-12 Adder B [R-77-1, RVV-SD]
18x AA-12 Adder C [R-77M]
100x AA-13 Arrow [R-37M, RVV-BD]
36x AK-100 100mm/70 Frag
5x AK-130 130mm/54 Twin Frag Burst [2 rnds]
21x AK-630M 30mm/65 Gatling Burst [400 rnds]
3x AK-630M 30mm/65 Twin Gatling Burst [800 rnds]
8x AS-11 Kilter [Kh-58UShK, ARM, Semi-Ballistic]
10x AS-17 Krypton C [Kh-31P, ARM]
43x AS-4 Kitchen D [Kh-32]
6x Generic Acoustic Decoy
7x Generic Chaff Salvo [4x Cartridges]
11x Generic Chaff Salvo [5x Cartridges]
24x Generic Chaff Salvo [8x Cartridges]
129x PK-10 Flare [SO-50]
4x PK-16 Flare [TST-60U]
40x RGB-1 [NATO BM-1, Search, Passive Omni]
4x SA-15b Gauntlet [9M331]
119x SA-21b Growler [40N6]
16x SA-27 Grizzly [9M317M]
31x SA-28 [9M96D]
24x SA-N-20a Gargoyle [48N6]
76x SA-N-21d Growler [9M96D]
13x SA-N-24 Grinch [9M342]
43x SA-N-9 Gauntlet [9M330-2 Kinzhal]
13x SS-N-12 Sandbox Mod 1 [P-500 Bazalt]
2x SS-N-19 Shipwreck [P-700 Granit]
2x SS-N-25 Switchblade [Kh-35 Uran] GLONASS
71x SS-N-26 Strobile [P-800 Onyx]
35x SS-N-27 Sizzler [3M54T Kalibr]
16x SS-N-30A Sagaris [3M14 Kalibr]
40x SS-N-33 [3M22 Zircon]
1x USET-80K



SIDE: CIVILIAN
===========================================================

LOSSES:
-------------------------------
1x Commercial Container Vessel - Feedermax [3,000 TEU, 30,000t DWT]
1x Commercial Container Vessel - Small Feeder [750 TEU, 9,500t DWT]
1x Commercial Fishing Boat [23m]
1x Commercial Tanker - General Purpose [20,000t DWT]
1x Commercial Tanker - Medium Range [40,000t DWT]


EXPENDITURES:
------------------



SIDE: NATURE
===========================================================

LOSSES:
-------------------------------


EXPENDITURES:
------------------



SIDE: Survivors
===========================================================

LOSSES:
-------------------------------


EXPENDITURES:
------------------
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL

Post by Correcaminos »

Fantastic news, Nikel! We now have a real Russian fury operational. I think this scenario is going to be a 5-star difficulty level (at least for me). I'd like to reply to your fantastic debriefing, but I'm tied up with the debugging. For now, the civilian side is already set to blind, since the fishermen, seeing so many explosions and missiles, were reporting everything to the log (I didn't change anything, I just added more action, and it's normal that it happens). I'm also studying VSCode and Blu3es's fantastic GitHub repository. I've debugged the SAR event; this time it should work well (the GPSJamming guy better watch out when he has time).

Image


I'll check the rest of the things, I really appreciate your involvement. :)
"Si vis pacem, para bellum."
Nikel
Posts: 2627
Joined: Tue Mar 24, 2009 10:51 am

Re: TRIDENT BOREAL

Post by Nikel »

As it is right now is a pain to test the scenario Correcaminos, it is very slow.

At least in my laptop.

Setting the civilian side to blind will fix it?
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL

Post by Correcaminos »

Image


Now the CIVILIANS side can no longer use their eyes to see missiles passing by or detect explosions; they are "blind" and should not generate messages in the log. There are many more missiles in play, and they were overloading the log.
"Si vis pacem, para bellum."
Nikel
Posts: 2627
Joined: Tue Mar 24, 2009 10:51 am

Re: TRIDENT BOREAL

Post by Nikel »

Perfect :)
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL V3.0

Post by Correcaminos »

SCENARIO CHANGELOG: KOLA 2027 (V3.0)

OPFOR (RUSSIA): Escort balance optimized. Su-35S Flanker-M assets have been added to provide realistic fighter cover for Tu-22M Backfire waves, ensuring the AI can manage effective strike packages.

USS OKLAHOMA: Negative scoring revised. Loss of this critical asset now incurs a -3000 point penalty. A comprehensive revision of all other assets for both NATO and RUSSIA sides has been completed to ensure scoring consistency.

SCORING LOG: Implemented u.classname variable. The message log will now display official unit models (e.g., "F/A-18E Super Hornet") instead of tactical callsigns, providing a cleaner interface.

SAR OPERATIONS: SAR event logic corrected and validated via VSCORE console and the fantastic Blu3s' GitHub database. Rescue procedures now require the recovery unit to perform a hover maneuver with sustained time over the survivor's position ( Added an explanation of the rescue maneuver has been added to the message generated by a survivor)

CIVILIAN SIDE: Non-combatant status set to BLIND. This prevents civilian units from flooding the message log with automated alerts triggered by missiles or explosions.

NATO ORDER OF BATTLE (OOB): Swedish Visby-class corvettes have been removed from the scenario due to a persistent Database (DB3K) error regarding missing datalinks for the CAMM weapon system. To maintain and enhance Task Force capabilities, they have been replaced by 2x Finnish Pohjanmaa-class corvettes (representing NATO's newest member) and 1x German Sachsen-class frigate (F124). This update significantly increases the group's anti-air and surface warfare power

STRATEGIC PENALTIES: Aircraft carrier loss penalty set to -10,000 points, reflecting the national strategic impact of such a loss.

LOGISTICAL DIRECTIVE: Tactical aircraft diverting to civilian or non-militarized airfields will be unable to rearm (WAD - Works As Designed). Commanders must manage fuel and recovery bases with extreme caution.
"Si vis pacem, para bellum."
User avatar
Correcaminos
Posts: 159
Joined: Sun Jun 01, 2025 7:25 am

Re: TRIDENT BOREAL

Post by Correcaminos »

Nikel wrote: Tue Feb 24, 2026 2:43 pm
The errors in the Luahistory file still appear.

Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!
Exception: [string "CachedChunk"]:10: attempt to call a nil value (global 'ScenEdit_SetUnitSensor')
Stack Trace: at NLua.Lua.ThrowExceptionFromError(Int32 oldTop)
at NLua.Lua.CallFunction(Object function, Object[] args, Type[] returnTypes)
at NLua.LuaFunction.Call(Object[] args)
at Adfs2QqMGUifo0Ac7CVE.qLd8ynxTUEn(Object , Object[] , Adfs2QqMGUifo0Ac7CVE )
at Command_Core.LuaUtility.DoString_Optimized(Lua lua, String chunk, String chunkName)
at Command_Core.Lua.LuaSandBox.RunScript(String str, Boolean RunInteractively, String script, String fullPath)

...
Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!
...
Function:ScenEdit_SpecialMessage (0) Error:Unable to identify Side-A!

I've been looking into this, Nikel, and I can't find the ScenEdit_SetUnitSensor command anywhere. It's not in any of the scenario's LUA files. I still don't understand why you're seeing "Residual Memory"? I don't see it in my game.


I'm thinking about how to overcome the difficulty and complexity; right now it's a really challenging scenario, I don't know if I myself would be able to finish it successfully; it's an extremely modern scenario.

I welcome any feedback. The effort to bring all the units together on stage has been enormous, and also a lot of fun.
"Si vis pacem, para bellum."
Post Reply

Return to “Mods and Scenarios”