Carrier landing issue as Essex not as #1 in group

[Foxtrot2571]

Carrier landing issue as Essex not as #1 in group

This issue was initially noticed when we attempted to have more than one USS Essex carrier in a single ship group. Aircraft can spawn and launch fine from any of the carriers, but the issue arose with landing. The arresting cables didn't function upon return to any of the carriers besides the number one carrier in the ship group. This is confirmed in the provided track file.

Track file test:
- Takeoff from #2 Essex carrier.
- short pattern and attempt to land on #2 Essex carrier. bolter.
- Moved over to #1 Essex carrier, successful landing.

Also to note, this issue does not occur with the Super Carrier. I had replicated the test and attempted the same process with the F/A-18 and F-14 with no similar issues I had with the Essex carrier and F4U Corsair. In all attempts, easy comms were used to test if established communications had any effect on carrier landing ops. No effect was observed. Only note is that Essex carrier comms do not function when carrier is not in the #1 slot of the ship group.

As our group (vCTF-58) plans to have Task Groups (up to 22 ships in one group, 4 of which are carriers) this will become more of an issue when we would like to be able to launch and recover from any of the carriers in the same group with the same heading. A temporary solution would be to separate the carriers in the own group in the same formation, but this becomes an issue for out mission makers. Tests were made in single player but issues were similarly noticed in multiplayer.

carrier issue.trk