fixed missionCommand.addCommand borked in *dedicated server* since update to 2.9.6.57650 (July 11)

[cfrag]

The July 11 update to 2.9.6.57650 has apparently broken the missionCommands function for 'Other' menu when then mission is run on DEDICATED server. This seems to affect only some aircraft, not all, and the way it affects these can also be different.

Below please find screenshots. Left is the self-hosted server (correct menu structure, identical to single-player), right is the broken menu structure when hosted on a dedicated server

Upper line: AH-64, lower line Kiowa

It seems that here on the Apache (top row), the menus lose their title, clicking on them does not invoke the correct method. On the Kiowa (bottom row) two lines disappear altogether. 

The mission that produces this behavior is here, and it can be reproduced at will using "Nal Kiowa" and "Nal Apache":

https://www.digitalcombatsimulator.com/en/files/3337088/

( @Flappie is this a known issue?)

Thank you so much for looking into this. 

 

[Flappie]

Hi @cfrag. I ran your mission on my dedi and tried said Nal slots, but the F10 menu does not even show. Do I need to do something special?

[cfrag]

Just now, Flappie said:

Do I need to do something special?

No, it appears you are getting the full brunt of the issue. If you run it local server, the F10 menus will show.

[Flappie]

Same issue when I run a local server through the Multiplayer menu.

And same issue when I run the mission from the ME. Are you sure I'm not missing something? I spawn in the hot "Nal 1" Kiowa, then I press \ and I don't see the F10 menu.

[cfrag]

That is strange indeed, as the screenshots come from my DCS install, standard, steam, no mods, local hosted via ME, and dedicated hosted via Fox3.

I‘ll check tomorrow, as I’m no longer at my computer.

Edited July 12, 2024 by cfrag

[Flappie]

Don't scratch your head too much. I think I missed something, I'll try again.

EDIT: It's OK, I see the F10 menu now (wrong version). I'll test and report.

Edited July 12, 2024 by Flappie

[Flappie]

Issue reproduced and reported.

[cfrag]

8 hours ago, Flappie said:

 

Issue reproduced and reported.

 

Thank you!

[GiraffeBoy]

+1

This issue is 100% replicated when running mission on dedicated server. Occurs only on certain aircraft and not others.

When mission is played in single player, comms menus display all options correctly in all aircraft. Only occurs in multiplayer.

[Kappa-131st]

On 7/12/2024 at 11:34 PM, Flappie said:

Issue reproduced and reported.

Any news about this issue?

[Migow]

On 7/12/2024 at 11:34 PM, Flappie said:

Issue reproduced and reported.

Please ED we need  the bug to be fixed thank you

[Flappie]

I've just bumped the internal report.

[Flappie]

Hi gents.

The Expansion mission does not work anymore on my end: I cannot spawn any aircraft. If you have another mission that still is affected, please send it to me.

I have a question from the devs: do you guys use SLMOD? And what if you don't? Do you still get the issue?

[cfrag]

24 minutes ago, Flappie said:

And what if you don't? Do you still get the issue?

Apologies if I sound silly (I'm not native English): Can I paraphrase your question as: do people in (dedicated) server that do not have SLMOD running see the issue of disappearing menus? I'll check anyways

26 minutes ago, Flappie said:

I cannot spawn any aircraft.

Can you be slightly more specific for me? What do you mean by that -- you cannot order support flights while you still have funds, or does the "Admiral AI" does not create flights any more?

 

[cfrag]

Yes, issue still there, NO SLMOD running on dedicated server, using Apache

null

[Flappie]

28 minutes ago, cfrag said:

(I'm not native English)

Neither am I. My sentence was not very clear, I admit, but you got it right.

Thank you for testing this.

The issue I got with the Expansion mission is not clear:  I select a slot, my name appears next to it, I wait for my aircraft to spawn, and after 10 seconds or so, I'm told my aircraft was lost.

I'm doing a test mission in the hope that I can reproduce the bug easily (at least, I can spawn in my missions).

[Flappie]

I can't reproduce the bug with my test mission. I used a Release dedicated server. What am I missing?

addCommand.miz

[cfrag]

9 minutes ago, Flappie said:

I select a slot, my name appears next to it, I wait for my aircraft to spawn, and after 10 seconds or so, I'm told my aircraft was lost.

Expansion only allows spawning from airfields that are owned by blue. Try a fesh start (delete the data folder) and select a slot from Nalchik (a flight starting with "Nal"). That should work.

Edited November 11, 2024 by cfrag

[Flappie]

33 minutes ago, cfrag said:

Expansion only allows spawning from airfields that are owned by blue. Try a fesh start (delete the data folder) and select a slot from Nalchik (a flight starting with "Nal"). That should work.

That's what I used to do (the Nal Apache 1, to be more precise) but it does not work anymore in an ED internal version. No such issue in Release, and I'm still able to reproduce the bug in Release by the way.

I'll try again, but if you have another mission using addCommand, I'll take it.

Edited November 11, 2024 by Flappie

[Flappie]

Here's a new test mission to try and reproduce the issue in Release: no joy (I used addCommand, addCommandForCoalition, and addCommandForGroup).

addCommand2.miz

[Flappie]

@cfrag It's OK, a fellow tester helped me with my spawning issue in your Expansion mission. I had to neutralize the stopGap feature.

We're now trying to understand why some slots are unaffected while others are.

[Flappie]

It could be a scripting error related to whether an helicopter is logistics capable or not, since only the Apache and Kiowa seem to be affected.

[Flappie]

Hey @cfrag. Can you please confirm this issue was fixed with the Christmas update?

[cfrag]

Thank you for following up on this, @Flappie.

I just checked (just some spot-checking), an now the menus do seem to be correctly present in dedicated server.

Cheers,

-ch

 

[Flappie]

Thanks for your feedback.