chronicsdoom 5 Posted November 16, 2012 ok so i been having this problem the last few days which is, everytime i log into the game i get killed instantly and then i have to start as a fresh spawn every time with no backpack or anything, the only thing i have changed is my isp would this matter ? Its really starting to bug me now as im in a guild but it doesnt happen to anyone else but me ??? could anyone shed any light on this at all would be most gratful,Many thanks,Shady Share this post Link to post Share on other sites
quezservers@gmail.com 1 Posted November 16, 2012 We had put up a short article about this bug on our website (QueZ). Here's a copy and paste of it to help you out.Yes it's a common problem not only found on our server but everywhere. Also happened to us admins. The problem is, when you launch your game and you're sitting in lobby of a server, always make sure your Battleye is fully innitialized and/or updated before pressing OK to get in the game. You will see a message of this appear at the bottom left corner of the screen in lobby. If you don't wait for this and press OK to enter the game fast and quick you may lose all your items, spawn somewhere else like you were dead with absolutely nothing, not even a backpack (sometimes on bug island where you can't go anywhere). Or you could just simply get kicked cause Bettleye is not rersponding while your in a car or something hehe sucks. If you spawn on the bug island with nothing and nowhere to go, simply log out and back in to spawn in an appropriate location.Always wait for a timeout to end before entering a server as well. If a server has been resently restarted, you will see an 88 seconds TIMEOUT at the top right corner of the lobby. LET IT COUNTDOWN to 0 or you may get that bug or get kicked in the middle of playing as well.We don't know why it does this, but we know it's not only our server... must be a general problem with DayZ... of course DayZ is still a BETA MOD and has multiple frustrating bugs and will continue to have bugs like this untill the standalone game comes out.Ever since I applied these tips for myself, I have not encountered this bug anymore.Hope this helps Share this post Link to post Share on other sites
brightlitefilms 37 Posted November 16, 2012 You're wrong (poster above me). It has nothing to do with the timeout thing as I join my own server often with the timeout thing still running (after a fresh restart) and all that happens is I get the loading bug and after one fresh ArmA 2 restart I able to join again.To the OP, it's pretty simple. Just use DayZ Commander to update your ArmA 2 version to the latest (I think it's 98836; just a guess). My friends have had this issue and that's all that they had to do to fix it.Regards,~Films :beans: Share this post Link to post Share on other sites
chronicsdoom 5 Posted November 16, 2012 tyvm QueZ i shall try this out, thank you for you time in replying :D Share this post Link to post Share on other sites
quezservers@gmail.com 1 Posted November 16, 2012 (edited) You're wrong (poster above me). It has nothing to do with the timeout thing as I join my own server often with the timeout thing still running (after a fresh restart) and all that happens is I get the loading bug and after one fresh ArmA 2 restart I able to join again.To the OP, it's pretty simple. Just use DayZ Commander to update your ArmA 2 version to the latest (I think it's 98836; just a guess). My friends have had this issue and that's all that they had to do to fix it.Regards,~Films :beans: Sorry mate maybe the timeout thing is right, I mean I know for a fact you get the loading bug yes. But dude we all use Dayzcommander and we are all updated to the max and some still get that bug (die for nothing and spawn with nothing) if they don't wait for battleye to update and/or innitialize. We tried several tests to proove this right. NO it wont happen every time you don't wait for it to update, but you have a 50/50 chance of it happening if you don't wait so YES the problem is with Battleye somehow... everytime we wait for it to Innitialize and or update we don't have that problem. If we don't wait then we have that problem. I will stick with that since we tested many times to proove it to our selves anyways.I am just trying to help here... use my suggestion or don't one thing is for sure, I wont get that bug cause I follow my steps here and that's all that counts ;)And you're welcome OP :D Edited November 16, 2012 by QueZ Share this post Link to post Share on other sites
