Enforcing deck crew via mission settings doesn't work

[Ahmed]

Enforcing the deck crew setting through the ME Mission Options setting doesn't work. After looking into the mission setting, the setting is being saved in forcedOptions under:

Quote

        ["Supercarrier"] = 
        {
            ["deck_crew"] = false,
        }, -- end of ["Supercarrier"]

when it likely should be saved (because it works if manually edited this way) under:

Quote

        ["plugins"] =
        {
            ["Supercarrier"] = 
            {
                ["deck_crew"] = false,
            }, -- end of ["Supercarrier"]
        }, -- end of ["plugins"]

 

[Jself]

we couldn't  enforce deck crew in options either

[CaliJoshua]

We had the same problem.  Please hotfix this for those of us that do no use the AI/use human controllers and LSO. 

[guitarxe]

Having the same problem. Need this one fixed ASAP! Whatever other bugs can be worked out in time, but not being able to disable the broken deck crew means not being able to use the carrier at all! Our squadron isn't able to fly missions any more because of this mess.

[gunterlund]

can confirm this. If unchecked in mission and its set to on in your controls, the deck crew will still be there. If you turn if off in mission makers controls and unchecks in mission, no deck crew. Fix this!!!!!!! The deck crew system is so porked, I came into my MP mission into the carrier and all the AI aircraft were stuck making the carrier useless. 

[lee1hy]

cant belive it was released in this condition
everything borken in Multiplayer respwan  This is like an e3 demo tech

[NineLine]

1 hour ago, lee1hy said:

cant belive it was released in this condition
everything borken in Multiplayer respwan  This is like an e3 demo tech

If you have nothing helpful to add the the report please do not post, this is not helpful. 

[gunterlund]

its tough when the expectation is we beta test

[ia_pro1691]

Our squadron just attempted our first mission with the new deck crew. It was a disaster. Two client slots began receiving taxi instructions before they were even finished starting up the jet. Once they started moving, the directors gave them guidance for about 20 seconds and then both received a "hold" signal. At that point, nothing else happened. Both tried to inch forward a bit to see if it would get things going as suggested in Spudknocker's video, but nothing. We despawned, reset the server and had everyone change their personal settings to disable deck crew. The mission file was set to not enforce deck crew as required. When we spawned back in, still deck crew present. I edited the mission file to enforce the deck crew being off and that worked to revert it back to how it has been before the update. There were zero statics or AI on the deck. 8 client hornets and 1 client tomcat.