Unexplained problem with UI in multiplayer dogfight mission

[Barnacles]

Dear Developers!

I'm an admin of one of the servers (Combat Box) over the past months we've been having a lot of unexplained crashes and glitches / bugs happen. I'm collating some info to send to you, but in the meanwhile, we had this happen for several players today.

When people join the server, they can't see the airfield spawns to click on.

For example on this map, on joining the server I saw this.

 

image.png

There should be several bases in the West part of the map.

 

I waited a few minutes, and then one (out of the four there should have been) appeared

 

But when I clicked on it, none of the planes appeared (initially)

instead there was a small black box.

After a while (1 minute approx), I was able to select aircraft

And I was able to spawn

 

After another 3 minutes a second airbase appreared (la Vielle in this image.)a seco

I was wondering if you could investigate, is there a problem with our mission we made?

EDIT on the Dserver consol, it has this error

!!! ERROR:
Incorrect delete attemption or receive data (0)

!!! ERROR:
Incorrect delete attemption or receive data (0)

!!! ERROR:
Incorrect delete attemption or receive data (0)

(Attached here)

big-normandy-campaign-day-024.zip

Track files as well

dogfight.2025-07-21_10-22-53_00.zip

Edited July 21 by Barnacles

[Biggles*266]

Yup same issue now.

[Alonzo]

Here are some errors shown on the dserver console window. This is immediately after a server restart (it's a fresh server) and the mission file itself contains Allied airfields. Players are complaining they can't see Allied fields, and we get this odd message: "Incorrect delete attemption or receive data (0)"

 

[Regingrave-]

Hi there, I'll take a look.
What mission logic does affect the buggy airfields in your mission? Any activation-deactivation commands, maybe?

[Regingrave-]

On the second glance, that could be a network issue (seems like a heavy lag preventing current state of an airfield to be updated in the GUI).
I'll consult with the programmers.

[Barnacles]

27 minutes ago, Regingrave- said:

Hi there, I'll take a look.
What mission logic does affect the buggy airfields in your mission? Any activation-deactivation commands, maybe?

We do have some missions that deactivate or activate things in the gui, but in this case I think we turned the logic off. @Alonzo can confirm

27 minutes ago, Regingrave- said:

Hi there, I'll take a look.
What mission logic does affect the buggy airfields in your mission? Any activation-deactivation commands, maybe?

But we will double check their status and remove that logic, if that's a possibility. 

For what it's worth, the mission we currently have running is currently experiencing this issue, right now.

 

Only the RAF and USAAF fields are affected (there should be 4 but some clients are not seeing any)

Edited July 24 by Barnacles

[Regingrave-]

What is Close_airfield_82 command for MCU:Behavior supposed to do? Using Float 9 seems wrong (should float -1 be used?).

[Barnacles]

12 hours ago, Regingrave- said:

What is Close_airfield_82 command for MCU:Behavior supposed to do? Using Float 9 seems wrong (should float -1 be used?).

Ok, we'll check it out, thanks very much!