BravoSierra

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.

ATC confuses who it is talking to, always referring to the same player no matter who called. Does not assign a different DME or altitude in the stack. 2nd and subsequent players must transmit 'abort inbound' in order to be able to contact the ATC. Again, because the ATC treats everyone as the same. Ground crew will not respond to some players (newly joined the game) when someone else is on Case III approach. Player has to disconnect and rejoin the server in order to get a launch or get rearmed. These are basic issues, and much more important than new functionality. Multiplayer carrier based pick up games are nearly impossible.

My team is frustrated with the FA18C module because on several occasions, AI migs have briefly flashed on SA and then disappeared, only to show up at the last minute or only after launching. AWACS doesn't report. Its as though we're getting jumped. This is new behavior per the guys on the team with years of FA18C experience.

Open the [your path]\Saved Games\DCS\Scripts\Helios\HelioExport16.lua file and make the following change. Find the line: local vvi = LoGetVerticalVelocity() and change it to: local vvi = LoGetVerticalVelocity() * -1