[INVESTIGATING] MP Carrier launch crew don't reset after landing on the deck

[Valkyrien]

The crew on the decks of the carriers stay in their "recovery" positions with their usual for those positions idle animations after touching down, this doesn't reset until someone spawns on the carrier, ATC also seems bugged for the landing plane as all options in the ATC menu for the carrier are removed save F11/F12.

 

This completely prevents subsequent launches on some servers with carriers but no carrier spawn slots (tested on hoggit TNN).

 

This also sometimes manifests as the crew resetting to their launch mode idles but the aircraft that landed being unable to interact with them in any way shape or form.

[squid509]

you need to use the coms menu and talk to the ground crew and "request launch" that will reset the cats so you can hook up

you need to do this even if some one spawns in MP and resets the animations

[BIGNEWY]

Hi as mentioned above use the deck crew radio command it should help

 

thank you

Edited September 10, 2020 by BIGNEWY

[Bankler]

Hi as mentioned above use the deck crew radio commend it should help

 

thank you

 

That's not really it. From my experience, the first few launches seem to work fine. But when being more than a just a few guys in MP, practicing traps, continously landing and launching, the ground crew will eventually stop responding for some people, with AFAIK 100% repro rate.

 

When this happens, if you tune in the AI Tower, they call out "Hold position, hold position!", and there is no way to make them respond ("request launch" does nothing).

 

This should not be marked as [NO BUG]. Because it is indeed bugged. Just requires you to play MP.

Edited September 9, 2020 by Bankler

[Bankler]

This is the current experience: https://m.twitch.tv/videos/735278006

 

(Sorry for the below average landing performance. Lots of beginners flying this time. Try not to focus on that. Posting the video to illustrate how bad the deck crew work in MP).

 

I can provide a track if that's helpful. The one from this event is 188 MB though.

 

If you need a short(er) track, and you don't have the resources to perform MP tests yourself, let me know, and I'll see if I can schedule some guys to help out. This really needs to work.

[BIGNEWY]

I will review it, thanks

[Bankler]

I will review it, thanks

 

BigNewy: My pleasure. Just let me know if I can be of any help. I'm on Discord as well.

[BIGNEWY]

Can you confirm if the clients were using the in game radio calls for recovery? or were they bypassing it and using human comms?

 

This maybe due to the carrier not being sure what state recovery or launch it is in.

 

once recoveries are in progress it is best to keep aircraft away from the JBD until they are ready to launch again. The AI may have got confused. I will mention it to the team, I see the problem starts around the 41 minute mark.

 

thanks

Edited September 10, 2020 by BIGNEWY

[Bankler]

Can you confirm if the clients were using the in game radio calls for recovery? or were they bypassing it and using human comms?

 

This maybe due to the carrier not being sure what state recovery or launch it is in.

 

once recoveries are in progress it is best to keep aircraft away from the JBD until they are ready to launch again. The AI may have got confused. I will mention it to the team, I see the problem starts around the 41 minute mark.

 

thanks

 

Thanks for looking into it already! I can confirm that we generally do not use the AI radio comms for recovery (we have humans doing marshal, tower and paddles, so it wouldn't make sense). I cannot 100% confirm though, that noone did it. Maybe someone pressed it, but I don't think so.

 

Regarding keeping aircraft off the JBDs during recoveries, that's an interresting thought to mention for your devs when tracking down the bug. But it's of course not viable for us as players. During CQ, aircraft constantly recover while they shoot aircraft from CAT #1 and #2.

 

Thanks again for the attention!

 

By the way, if it turns out that it's hard to solve these problems in a graceful way in the next few weeks, maybe you could consider implementing a "hard reset" radio option, that resets the deck crew state machine completely? (Just thinking out loud here, not sure if it makes sense from a technical viewpoint, depending how it's all implemented)

Edited September 10, 2020 by Bankler