Page 2 of 2

Re: TRIDENT BOREAL

Posted: Fri Feb 20, 2026 7:17 pm
by Knightpawn
Correcaminos wrote: Fri Feb 20, 2026 10:31 am Perfect, easy to fix. I must have accidentally deleted it in the build versions. I'll name all the TF and SGC files. The sides is easy too. Anything else?
I will give it a go tonight. If I add Queen Elizabeth, how many F-35Bs and helos do you envision in your scenario?

Re: TRIDENT BOREAL

Posted: Fri Feb 20, 2026 8:45 pm
by Nikel
Nikel wrote: Fri Feb 20, 2026 1:05 pm
Messages like this appear on the screen when you load a save. More advanced the scenario, the more messages.

E5.png
E5.png (8.99 KiB) Viewed 55 times

Besides this.

When you load a save, the briefing looks like from another scenario?

Re: TRIDENT BOREAL

Posted: Fri Feb 20, 2026 11:38 pm
by Knightpawn
I am at 1130 Zulu and this feels very immersive. Bravo.

Reporting the following:

1. A lot of error messages at the outset. I understand they are from the script of the Jammer event that needs refinement

2.
Nikel wrote: Fri Feb 20, 2026 8:45 pm

Messages like this appear on the screen when you load a save. More advanced the scenario, the more messages.


E5.png

Besides this.

When you load a save, the briefing looks like from another scenario?
I second the above. Also note:

3. Orland Airbase:
The briefing speaks about 2 B-1B Lances with LRASM. Is it on purpose with different loadout? It takes 20hrs to rearm. Also it seems that the intention for the other 2 B-B1 is to be in maintenance, but this is not the case.
Same for two F-35A. Their name implies maintenance.

4. Queen Elisabeth missing. I added it myself for now.

5. I get the following pop up upon loading a save
Screenshot 2026-02-21 111904.png
Screenshot 2026-02-21 111904.png (119.89 KiB) Viewed 17 times
6. The message that is supposed to be delivered upon visual inspection of Havis-1 is not shown properly
Screenshot 2026-02-21 113744.png
Screenshot 2026-02-21 113744.png (387.68 KiB) Viewed 15 times

Re: TRIDENT BOREAL

Posted: Sat Feb 21, 2026 2:13 pm
by Correcaminos
VERSION NOTES: Operation Trident Boreal V2.5 (BETA)

Executive Summary: This update focuses on power balance, tactical immersion, and critical scoring engine refinements based on community feedback.

Unit Identification: Surface groups have been named specifically to facilitate searching and management within the OOB.

HMS Queen Elizabeth: The British carrier has been successfully re-integrated into its Strike Group.

Power Balance: Reduced NATO air assets to ensure a more balanced and realistic challenge against Russian capabilities.

Loadout Corrections: B-1B Lancer loadouts have been updated to specialized Anti-Surface (ASuW) configurations using LRASM missiles.

Civilian Traffic: Specific civilian airbases have been designated for the return of civilian aircraft, improving the management of the Civilian side.

Scenario Duration: Operations have been condensed to a 24-hour window to increase tension.

The "GIUK Gap" Event: New interception event: Russian submarines are attempting a breakout into the Atlantic. Players must utilize rear-guard carriers to intercept. Failure results in a specific HTML alert and a score penalty.

Yasen-M Threat: Submarine activity for the Yasen-M class has been increased.

Tactical Hint: Dispatching an air unit to the HAVIS-1 platform after the incident will provide clues to estimate its position based on time-speed-distance escape calculations.

Russian Doctrine: The Admiral Nakhimov SAG is now more aggressive and features its own organic AEW (Early Warning) missions.

Charles de Gaulle: Fixed the tactical description regarding its nuclear capabilities.

Increased Aggression: Added additional aircraft and missions for the Russian side, including SEAD (Suppression of Enemy Air Defenses), Maritime Patrols, and constant CAPs (Combat Air Patrols).

Global Scoring Engine: The scoring system has been overhauled and expanded. It now correctly accounts for the destruction of land-based units (SAMs, Radars) and surface vessels for both sides.

Area Management: Attempted to resolve "Invalid Area" errors by ensuring reference points do not overlap within the editor.

Side Lock: The scenario is currently optimized and locked for play from the NATO side only.

GPS Jamming: Temporarily disabled this event for further stability testing; the goal is to provide a smoother gameplay experience for now.

CRITICAL NOTICE FOR TESTERS
SAR Script Compatibility: It is strongly recommended NOT to play via the editor or swap sides during a session. The Search and Rescue (SAR) script triggers based on the active side; swapping sides will corrupt the logic and cause "ghost pilot" errors.

Recommendation: If you must use the editor to modify the scenario while playing, please disable the SAR event to avoid script conflicts.

"The images in the description have been temporarily added via external web hosting. If you encounter any issues viewing them, please wait a few seconds for them to load, or it might be a temporary issue with the host provider. We kindly ask for your patience, as this is not a priority at the moment."
Thank you all for your continued support, bug hunting, and patience as we polish this operation. ;)