Jump to content

Multiplayer SuperCarrier ATC issues - confuses the players with each other


BravoSierra

Recommended Posts

Case I and III multiplayer ATC confuses the players, calling them all the same call sign and assigning them all the same position in the stack.  In Case III only, other players must transmit 'Abort Inbound' before being able to call ATC, and then the replies are all to the incorrect player.  

When a player is in case III approach, some newly joined players cannot get the crew to respond to them to get a launch or get rearmed. Must leave the server and rejoin. 

Please priorities multiplayer carrier ops - it is impossible to coordinate a team with such confusion. 

  • Like 2
  • Thanks 3
Link to comment
Share on other sites

  • 2 months later...

bump ... our flight group can confirm ...

Case III in Multiplayer and with more than one Pilot in a flight are absolutly confusing ....
One only Client in a flight works ... sometimes ...

Its very anoying ...

please try Case III with two Clients in one flight in example Enfield-1-1 and Enfield-1-2

brg
 

  • Like 1

too much ...

 

 

Link to comment
Share on other sites

can also confirm, Case I practice the other day and even after all of us calling the boat, only the number one bird got any kind of talk down from the LSO and even still after landing we all got "missed an important step" even though we know for a fact that we did not. at some point ago ( one or two updates ago) if in formation and the number one bird called in you would hear "holding hands with.." for example, "Mothers, 230 holding hands with 315 (aircraft two), 235(aircraft three)" and then thats all we would have to do. Carrier ops is a BIG BIG BIG part of our missions and the even more so on the MP Campaign we fly (Want To Fly). please fix!

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

CASE III has it the worst. Player A calls inbound, but CATCC sends the respons (comms menu tree) to Player B, using Player B's modex and state. After established CATCC/Tower get Player A and Player B properly separated, but Player B gets "no proper communications) because he/she literally isn't allowed to call inbound.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...