ironmaidenmn 0 Posted September 15, 2012 (edited) Heya, Ive been having the same error that this guy has been having.I also read this article and followed the instructions, nothing worked yet.help please?EDIT: I also tried doing this, but it also did not work.7:05pmhttp://support.dayzm...ayarticle&id=20http://dayzmod.com/f...stan-12-update/http://dayzmod.com/forum/index.php?/topic/90290-problems-getting-on-to-dayz-takistan-servers/ Edited September 15, 2012 by ironmaidenmn Share this post Link to post Share on other sites
stokvis 24 Posted September 15, 2012 Hi, here is the guy. Accidently saw your post hahaha, ;)I have played for 2 whole minutes now. Until the admin shut the server down because he heared me firing at zombies (not the server that I tried joining the whole day).I think it is in one or another way server related. Some work, some don't I think, still figuring it out. Share this post Link to post Share on other sites
stokvis 24 Posted September 16, 2012 This is what I found on other topics about this issue:SOLVED!Its a serverside problem with the -maxmem 2048 command. Serveradmins: remove it and all will be fine!alter a week of trying everything. i solved it (for me and my server)! seems that some people have problems with the bigger package size. remove the -maxmem 2048 command from server start parameters and set it in the arma2.cfg back to 1400 and your server will be run fine. way less battleye client not responding kicks and the signature check timed out is completly gone.if u are not the admin of the server try to contact him. link him this threat. if they have questions contact me.have fun with Dayz again!a Share this post Link to post Share on other sites
Michaelvoodoo25 3120 Posted September 16, 2012 Up the Irons!! Share this post Link to post Share on other sites
stokvis 24 Posted September 16, 2012 I downgraded to 1.1 and I can play now. Not on the server that I want but f*ck that. I want to play. Now. Share this post Link to post Share on other sites
stokvis 24 Posted September 17, 2012 Ok apparently what they told me it's a Battleeye issue. Share this post Link to post Share on other sites