User Details
- User Since
- Mar 27 2024, 2:11 PM (31 w, 1 d)
Fri, Oct 18
I tried a method to correct the problem with a customer who was asked to have a DLC to connect to his Chernarus server. The problem is corrected by adding the following parameter to serverDZ.cfg:
steamProtocolMaxDataSize = 4096;
Perhaps it would be a good idea to increase the default value (1024 - I think) used by DayZ so that server owners don't have to do this. In addition, this will resolve the launcher warning that the list of mods is incomplete on servers with many mods installed.
Aug 13 2024
@XiKKA Hello. I've been able to work on a number of servers with this error. I've come to the conclusion that the latest update is not at fault and that the error itself is irrelevant, as it is systematically caused by a mod that crashes the server. However, it's difficult to identify the mod with this error alone: I'd advise you to ignore this error and look among your mods for what might be causing the crash. If it happens systematically during startup, it should be fairly easy to find. Otherwise, you'll need to be patient and persistent.
Aug 7 2024
Yes, it's not very clear inside the changelog. Can you say whether the "shardId" must be unique for each server hosted on a machine? Apparently, the same shardId can be used. But this is not clear without documentation.
Jul 20 2024
Jun 13 2024
Jun 8 2024
@Geez I don't think it will be necessary to look any further into the cause of these crashes. Crashes do not look the same, as reported by the developers and observed here, and can all be fixed (especially for crashes that occur during runtime) by server administrators with a complete checking the server mods. I debugged a customer's server yesterday that had a crash similar to what was shared here and it was from an event that spawned modded zombies. Very different from other crashes I've been able to fix that were caused by items spawns.
Jun 4 2024
Jun 3 2024
Jun 2 2024
Jun 1 2024
An example of a crash when the hive is initialised :
------------------------------------ WIN-UTOF1UC2OFH, 01.06 2024 17:23:13 Unhandled exception
Hello Steniboy. This problem has already been reported in another ticket : https://feedback.bistudio.com/T181638.
Follow this ticket if you wish to be notified of its correction.
Like @voudou reinstalling BattlEye didn't solve the problem for one of the users concerned. What can we provide developers to help them understand this issue?
I should also point out that we've had a few reports of this from players on our customers servers. I've passed on the method recommended by @Geez. I'm waiting to feedback from these players.
May 31 2024
May 30 2024
Can you try increasing the MTU on your PC Wired ? The MTU should not be 1300, the recommended value is 1500. This can be done with the command : netsh int ipv4 set subinterface "Ethernet 3" mtu=1500 store=persistent. An MTU of less than 1500 can cause a WaitAuthPlayerLogin error.
May 29 2024
So far, we know this happens:
On our side, we have identified a new customer affected by this problem. (And we're a small service... at the moment) When in doubt, I'll also provide you with the logs + MDMP so you have more material to understand the problem. According to the servers, this problem is fairly critical in its regularity.
Here is another crash and the associated .mdmp file:
------------------------------------ WIN-43417R2VOB5, 28.05 2024 22:48:15 Unhandled exception
May 28 2024
May 15 2024
Hello. It would have been great to be able to make the distinction to prevent this from happening. Unfortunately, the distinction that would be made would open the door to abuse through the use of third-party software to cause a voluntary exclusion so as not to be affected by the 15-second timer. It's technically possible, but you'd have to put too much faith in what's done on the client side.