Teams (not) working together, and incomplete OOB
-
Version
4.35.0 (x64)Build
22548Detailed Description
With the changes to how teams work in 4.35, it’s now possible to create a tactical engagement with allied nations operating from each other’s bases (e.g. in KTO, NATO, US or ROK aircraft can all operate from a single ROK airbase), which is a pretty neat feature. Unfortunately though, there are currently still a few issues with that.A) The available squadrons are not clearly reflected in the OOB
When US squadrons are added to a ROK airbase, for example, they aren’t visible in either the US or ROK OOB.
There is one workaround, by activating both the team that owns the airbase, and the team that has the squadron, as seen in the image below. The manual sort of mentions this indirectly on page 10-169, probably more by accident than by design I think, but it’s by no means clear that this is the only way to see the full OOB in BMS.B) Can’t add squadron to team nation’s base
When a squadron does not exist yet, it is impossible to directly add a squadron to an allied member’s base. If you try this, it will add the squadron to the base owner’s team instead. The only way to add one to an allied base is to add a flight, select a “new squadron” and select the allied team member’s base.C) Lack of combined packages
Unless I’m missing something, like the OOB work-around, there is currently no way to have multiple teams in packages yet, and a package is still one-team only. Would be nice if we could mix those up and have a single package with NATO Eurofighters, US F-22s and ROK KF-16s, for example.D) Ineffective AWACS / support assets
Probably the biggest issue of all, is that the AWACS seems to be less effective for allied nations than it is for their own team. Since 4.35, our default is to fly as NATO F-16s, and to reduce clutter in our flight list, we usually frag AWACS support by US E-3s. Quite often, when we ask for a picture, we get a “Picture Clear”, despite us having multiple hostile groups on the FCR. In some instances, we’ve even ID’ed or been engaged by the hostiles already. Our experience so far is that AWACS becomes more reliable as we get closer to the enemy groups, but that usually means we have to be nearly on top of them already to get proper information.During two same-side tests (one where we played as NATO F-16s with NATO AWACS, another as US F-16 and US AWACS), we did get proper picture calls at ranges beyond 40NM.
Example files
N/ACrash logs
N/AReproducibility Procedure
N/A or explained aboveExpected Behavior
A) I think the OOB should reflect all the squadrons on a particular airbase, even if the squadrons belongs to another team than the base owner’s.B) Either have a squadron maintain the team currently selected in the top left of the TE Editor, or add an option in the Add Squadron pop up to select the desired nation for the squadron that is being added.
C and D) Increased operability between allied teams.
Kind regards,
Eagle-Eye