solved Multiplayer Slots Locked after Client Despawn or Death

[GeoS72]

I encountered a strange error last night while playing a closed mission with my squadron.

The problem:
Multiplayer slot is locked or denied to a client after the unit is dead or the client despawns. This happened in the Sinai map. See attached DCS log but I didn't find any errors that would cause this type of problem. This problem affected any client who crashed/despawned.

I checked the airfield assets. All aircraft set to unlimited. No dynamic slots were used. I also compared the mission settings to another multiplayer map. The settings are identical.

Has anyone else experienced this problem? I didn't see any threads that would compare to this problem.

dcs-2024-09-05 Pharoahs Fate.log

[GeoS72]

This problem still persists. I attempted to create a "dummy" MIZ file and then copy most of the relevant lines of code from the suspect file into the dummy file.

The problem carried over to the dummy file. Any suggestions?

[GeoS72]

Moderators,

Have you seen this problem?

[GeoS72]

Bumping this old thread. I re-examined this mission again and part of the problem is fixed. I did not encounter slots being locked out for fixed-wing aircraft in this multiplayer MIZ file. This problem only affects the helicopters.

I'd like to repeat that no scripts or 3rd party modules were used or required in this MP mission.

@Flappie, would you be able to help or offer advice? Has anyone else experienced this issue?

I also noted the DCS log ballooned to 72 MB with tens of thousands of lines of the same error. See the link to download these massive files.

DCS Log-Pharaohs Fate-Issues-1
DCS Log-Pharaohs Fate-Issues-2

This is an example of the 2 prevalent errors in the DCS Log file:
2025-01-17 23:58:49.680 ERROR   ED_SOUND (Main): source_start(-1, 0000000000000000, 0000009268afedb0): invalid source
2025-01-17 23:58:49.680 ERROR   ED_SOUND (Main): source_is_playing(-1): invalid source

[Flappie]

I tried your mission for about an hour but could not reproduce you slot availability issue (I used the "Gecko-1" Apache slot). Maybe it was caused by a server-side script (slot blocker for instance).

My client log does not have these sound error messages of yours.

From time to time, your log says it's trying to launch SRS, but I don't thin it has a link with your sound error messages.

dcs.log

[GeoS72]

Flappie,

Thank you for the feedback and sharing your DCS log. I'm still digging into the problem. This is the only MIZ file that gives me problems and has a very large log file full of sound errors. I'm still looking for the "smoking gun".

[GeoS72]

OK, I believe I fixed the error with clients being denied slot access if that slot was released or a crash.

The trigger system in this MIZ file may be the root cause. Here's a synopsis:
Trigger Category: 1 [One Time]

Condition 1: All of Group in Zone. Zone is defined as Everywhere, takes up a large portion of the map. Group is a 1-ship, named "AH-64 Slot 1".
Condition 2: Time More than 400 sec.

Action: Flag On: "AH-64 Slot 1"

My solution with 2 triggers:
Trigger Category: 3 [Switched Condition]

Condition 1: All of Group Out of Zone. Zone is defined as Everywhere, takes up a large portion of the map. Group is a 1-ship, named "AH-64 Slot 1".
Action: Flag Off: "AH-64 Slot 1"

Trigger Category: 3 [Switched Condition]

Condition 1: All of Group in Zone. Zone is defined as Everywhere, takes up a large portion of the map. Group is a 1-ship, named "AH-64 Slot 1".
Action: Flag On: "AH-64 Slot 1"

 

The problem with the sound entries in the DCS log appears to be a separate issue. That will be a separate topic.

 

Thank you, @Flappie for offering your help and insight!