Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About [email protected]

  • Rank
    Scavenger
  1. Not sure, it seems to be fixed for me as of yesterday. You might wan to go to the Battleye site and send them an email like I did. He should be able to give you the beta BE client that logs the data so he can track down what your issue is.
  2. See if it works now. Bastian Suter pushed a new Battleye for the server side after I gave him the log files from the beta Battleye client he created for me. My issue seems to be fixed now.
  3. There should be a fix coming on the server side BE for the "client not responding" issue tonight or tomorrow according to Bastian Suter.
  4. Finally got the test BE client from Bastian Suter. Grabbed some some logs while connecting and getting kicked for client not responding and sent them into him. He said he sees the issue and will work on a fix.
  5. On all servers or just a specific one? The reason I ask is that there is a known issue with the scripts.txt file employed on some game servers. I started getting the "Battleye: Client Not Responding" a little over a week ago on my home server and tried everything under the sun to resolve it, it turns out that it is something to do with Battleye and the scripts.txt on the server side that is causing it. I'm waiting on a test BE client from Bastian Suter (Battleye creator) that should hopefully be delivered here in a few hours according to his last email. Not sure if the test BE client is simply going to log the data he needs to figure it out or if it is going to resolve the problem.
  6. Darn, already set to LLC. This isn't apparently my problem.
  7. Going to try changing to LLC based when I get home. I seriously hope that is my problem as well.
  8. Just an FYI. My home server does it to me every single time as well as long as the server side scripts.txt file is in place. I'm in direct communication with Bastian Suter from Battleye, he is producing a test BE Client for me to try (I'm guessing it'll gather information for him) to try to help fix this issue. http://dayzmod.com/forum/index.php?/topic/46792-battleye-client-not-responding/
  9. You aren't crazy, its a REAL problem with that server (and a few others I've stumbled on). What ISP does your buddy have? UPDATE: Just got another email from Bastian Suter, he's going to create a test version of Battleye and send it to me soon in order to help locate the issue.
  10. That solves nothing for me on that server. I've done EVERYTHING and I'm in contact with Bastian Suter from Battleye who seems to think it is a problem with scripts.txt and Battleye. If the server admin renames the scripts.txt file and reboots the server I can connect and play just fine for hours on end. If the scripts.txt file is in place I can get to the lobby and sit there for 15 seconds and then I'll get kicked for "Battleye: Client Not Responding". The problem has something to do with scripts.txt and Battleye and (perhaps) my ISP (I play just fine on about 95 percent of other servers btw.. but the server I'm trying to play on is my clan's home server so I want to play there). Before someone starts offering the simple fixes that I've seen peppered all over the Internet, I've done them, 20 times each... I've reinstalled Battleye (and the manual dll copy method), reinstalled the game, reinstalled my OS, changed routers (One is a Netgear the other is Apple), update firmware on the routers, had the server admin try playing my character (succeeded), I tried playing the server admins character (failed), installed the game on one of my old machines (still failed with "Client Not Responding"). So yeah, it IS definitely some combo of Battleye 1.165+, scripts.txt (even the new one my server admin obtained yesterday) and (maybe) my ISP.
  11. I have a similar issue (mine happens like 10 or 15 seconds after connecting to the lobby) although mine happens on my home server (and a few others I've tried): US 257 Seattle (http://www.gametracker.com/server_info/74.121.191.74:2302/) I have tried everything you have and even tried different routers (switched from a Netgear WNDR3700 with OpenWRT to my Apple Time Capsule) and have the same result for that server (in addition to what he'd mentioned I've tried every uninstall/install method for Battleye I could find on the Internet). I can get on about 90 percent of servers but I hit one now and then that just refuses to play nice just like US 257. I sent a message to Battleye support to try to help me turn up logging or something but I'm not holding my breath. Any helpful tips from anyone that has overcome this issue?
  12. Hit the respawn button, it worked for me and many others.
  13. My apologies for ever doubting you. Problem solved.
  14. That sounds like a guaranteed way to lose my existing gear. Where did you read this?
  15. Good, now you won't have one when you really need it. I hope the zombies gnaw your leg off. :rolleyes:
×