This has indeed been a sore spot for many users attempting to join our lightly modded servers. Several times a week we field support tickets from users completely baffled by why they are unable to connect and are receiving the "Connection has been lost" error message. 99% of the time having the user move DayZ to an SSD will resolve the timeout they are experiencing. This is not an option for all players, unfortunately.

Not only is the timeout on the shorter end for a lot of hardware, but the kick message is vague and unhelpful on the users end.

Hi @Geez,

The kick message is "Warning 0x00040004. You were kicked off the game. Connection with host has been lost.".

This has been an issue since the 1.13 patch, it's just becoming noticeably worse as load times increase.

Some examples:

To test it, it should be as simple as installing DayZ on a older hard drive and joining a server with several larger mods (ie Expansion).

Thanks

In T163527#2284684, @Lewk wrote:

Hi @Geez,

The kick message is "Warning 0x00040004. You were kicked off the game. Connection with host has been lost.".

This has been an issue since the 1.13 patch, it's just becoming noticeably worse as load times increase.

Some examples:

To test it, it should be as simple as installing DayZ on a older hard drive and joining a server with several larger mods (ie Expansion).

Thanks

Why does this error message makes you believe this might be related to the BattlEye client? As this might be unrelated to BattlEye.
Regards,
Geez

With use of unoptimized mods, on a lower tier hardware (HDD, low read/write speeds) the game tends to take much longer when loading in.
The connection process on each server takes different amount of time based on factors like; mission size (adding custom buildings via CreateObjectEx), count of entities nearby to load in during initial connect.

Battleye has a timeout threshold during client connect. When the client fails to respond(while in the connecting stage), the user is kicked. Typically between these two states;

AuthPlayerLoginState
WaitAuthPlayerLoginState

Either a) we get to set a higher timeout value on BE, or change timeout value server side.
MissionServer::OnClientPrepareEvent(....out int preloadTimeout)
preloadTimeout doesn't seem to function properly, the timeout duration is the same. As far as i am aware, there aren't other parameters (serverDZ.cfg or globals.xml) that allow to edit such values.