User Details
- User Since
- Dec 29 2017, 4:42 AM (358 w, 6 d)
Jan 26 2018
I consulted with the unit member who manages the changes we make to the mission file. Through his review of the code, he did find that this command is used and is critical to the mission function. From what we are able to determine, this command is used to remove hostile forces and wrecks from the entity list to keep a clean entity list and prevent anyone from deleting the hostile forces through Zeus (aka instantly killing all the bad guys without having to fight anyone).
Jan 24 2018
Sorry for the delayed response. We updated the server to the latest version of the mission file from the devs and found some interesting information.
Jan 3 2018
Adding a second log set from yesterday.
Jan 1 2018
To add more data to the issue, from discussion with the admin team, we have came to a conclusion that our instance of the issue is primarily tied to Zeus access. All of those with access to Zeus are the ones who crash when the trigger event occurs.
Dec 29 2017
The server at issue in my report is a base KP Liberation with some changes to the blacklists. I also tried the compatibility, XMP adjustments, changed the memory allocator, deactivated full screen optimization, and tried 32 bit. I also tried to play in full screen borderless, but no change there either.
This has been happening consistently on a server I am an admin on. What is unusual is that the issue sometimes never reproduces, but other times, it consistently reproduces. The issue also impacts everyone who is connected to the server and has faced this issue at the same time and then it often continually reproduces for those impacted. This began happening about a month ago and I have been searching for a fix along with other members of my milsim unit. What enhances the oddness is that we have weekly operations with high volumes of people and on our operations server (different than the server I am admin on) we do not encounter this error. That server has a high volume of mods in place, while the server the error occurs on has zero. Time frame is also variable with the issue sometimes happening immediately and at other times taking anywhere from 1 to several hours of play before occurring.