I keep getting this everytime I try and join a dayZ server on the DZSA launcher
Description
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10
- Category
- BattlEye
I click a server to join and after 1-2 min of loading it kicks me out and says "kicked off the game battleye (client not responding)"
I've tried uninstalling dayz and the launcher and reinstalling it, I tried also uninstalling the mods and reainstalling it, I've restarted my internet, I've tried joining dayZ server on the normal dayZ launcher with direct connect.
I'm just worried I won't be able to play dayZ
Event Timeline
Hello chucky20097.
Does this occur on the vanilla version of the game without any mods running when connecting to official servers? Also, do you have this problem with the standard dayz launcher?
Regards,
Geez
We had a massive spike in reports of this with 1.13. Battleye seems more sensitive to the time it takes clients to load in, and it's causing people with older or slower PC's to have issues they didn't have prior to 1.13.
In many cases we have worked around the issue by having the player move their DayZ installation from a HDD to an SSD (if possible).
Other times we have the player load the mods into the launcher, then launch the game without connecting to a server, then connect to the server after the game is running. This can be difficult if the player isn't familiar with manually managing mods in the client, however.
also I want to add that it sometimes says connection to host has been lost
So far modded servers and yes it does not work on the regular launcher too, I went to a point where I reset my pc and it still didn’t fix it
I also have the exact same problem. I've done all i can and nothing has worked. Has anyone figured a way to fix it?
I have the same problem, me and my friend can't play at all right now cause we get this error 95% of the time. Sad that there i still no working fix in any of the forums...
FINALLY I FOUND SOLUTION!! it turned out that the game sometimes does not work well with the IPV6 protocol. Changing the router settings to the IPV4 protocol solved the problem once and for all!