Patch Notes: The little guys are showing up + new info

Note & credit: Action screenshots were provided by players on the game’s Discord - today featuring Munchlol, XEN, Alan, Matic, Pilot and Foxman. Great thanks to them!

Not really a full update today, but the latest patches that dropped had still to get their patch notes - please find them below with a few comments!

What's new: Static crewmen, LRCAP & FDO New functions, more details about Flight Deck Damage

The following new fixes & functions were implemented this week:

06/05/2026

• Fixed major bug with japanese seaplanes in the Wake Up Call at Tulagi scenario.

• Fixed crash when planes requested to land just after a plane took off from a given carrier.

• Added an error reporting system that will automatically package game data, with user validation.

• Regarding carrier flight deck damage mechanics introduced a few days ago, please note the following:

  • A destroyed aft flight deck section will make all landings impossible.

  • A destroyed mid flight deck section will make strike spotting impossible, but CAPs will still be able to takeoff.

  • A destroyed fwd flight deck section will make all takeoffs impossible.

08/05/2026

• Added static crew on some turrets. You may need to enable the option, in the "graphics" tab.

  

  

• Fixed crashes when ships are removed from divisions because of damages or manual fleet edition.

• Fighter Direction Officer (FDO):

  • Fixed manual interceptions order for large CAPS.

  • LRCAPs can now be directed from their target fleet (please select the right fleet on the FDO screen).

  • Fixed several bugs when ordering the closest patrol to intercept a boogey.

• Slightly improved collision avoidance when a fighter attacks a bomber.

Steam post image

The Next Scenario: Kantai Kessen

The new scenario is being worked on and should be available within a couple weeks, once we're done with the new functions and units it requires.

In this hypothetical take, Midway never takes place - at least, not as we know it. The HYPO "AF" deception fails to trick the Japanese and Washington, and as such ComInch subsequently fails to allocate forces to the Midway area in time.

However, now that HQ and the Redman brothers have been proven wrong, Nimitz has a free hand to remodel the American counterstrike. All the while, although Midway was intended to be a cakewalk for the Japanese, the initial invasion failed, and the transports have retreated. The Combined Fleet is now moving into position to intercept reinforcements coming from Pearl Harbor- but those reinforcements are taking their sweet time.

Nimitz has deliberately waited for the USS Saratoga and the arrival of new airframes before launching his gambit. Now, TF-17 (Yorktown & Saratoga) and TF-16 (Enterprise & Hornet) are executing a massive pincer movement centered on Midway. Meanwhile, a relief force of fast transports is running the gauntlet to resupply the island - and possibly act as bait.

Nimitz rejected the assistance of TF-1’s battleships, ensuring the US forces remain nimble and carrier-centered. The Japanese, conversely, are forced to rotate their ships in and out to refuel, as the bulk of the Combined Fleet has been idling off Midway for a week or so. The Kido Butai has also expended a non-negligible number of aircraft killing sand dunes and gooney birds, trying to avenge the sacrifices of the Japanese Army troops and Marines, but to little avail. Although the outpost is neutralized, it remains firmly in American hands, and continues to provide vital intelligence on the surrounding waters.

This scenario will put US carriers against formidable foes - including the fearsome Japanese battleline. The air groups will also be pretty peculiar, with VT-8 upgraded to a full Avenger group, and Saratoga carrying more fighters than usual. New units are also introduced to the game and will hopefully be integrated by the time it releases. It could be spectacular, and will serve as a good proof of concept for larger, multi-day battles.

In other news

Wolfpack has blessed us with a new video. Along with the Historical Gamer & Rimmy, he has been among our greatest supporters in the sim-wargaming community, and I'd like to thank him particularly using this opportunity. You can go and watch him play our latest scenario, Wake Up Call at Tulagi, that was just released last week.

As some of you have noticed, Wolfpack's Dauntlesses have been a bit "naughty." They opted to attack the retreating second-line destroyers of the Tulagi invasion force instead of the bigger prize, that is Carrier Division 5. For those interested in the "why," here is a breakdown of what happened:

It appears Wolfpack fell victim to a perfect storm of conditions that caused the AI to behave this way:

• First: The strike force completely destroyed all the slower ships in the Tulagi invasion force. This unburdened the escorts, allowing them to proceed at full speed toward their exit point.

• AdjustedSecondBecause of their increased speed, the destroyers occupied a position just beyond the strike force’s Initial Point (IP).

• Third: Since the Japanese carriers weren't within visual range when the IP was reached, the strike force attacked the first targets on sight.

In most cases, this wouldn't occur because the escort force wouldn't have reached that position in time, but it obviously sort of qualifies as an issue, still. We plan to implement more advanced target selection logic in the future to allow players to set priority targets for strikes.

Until then, consider this as an unlucky fluke, though one with historical precedent. Tanikaze at Midway, misidentified as a light cruiser, had to go through something like that, being bombed by 60+ bombers (SBDs & B-17s in three waves) for lack of a better target. Some might also say that it is not too different from what happened to Neosho and Sims at Coral Sea, although in both cases the navy pilots naturally checked the surroundings rather thoroughly. As IRL, in the future, we'll have the bombers first conduct an extensive search towards their final waypoint before they decide to go for the consolation prize.

Discord & Modding – Quick Reminder

Reminder about the modding discord here, where Matlock3462 will entertain you with his experiments (see screen above):

CLICK HERE TO ACCESS THE BUORD DISCORD

And as you know Task Force Admiral also has its own server. For any in-depth, direct support for technical issues, please do pay our tech support section a visit.

CLICK HERE TO ACCESS THE OFFICIAL TFA DISCORD

That's all for today folks! Enjoy your time and take good care!

The TFA Team