catface.jpg 75 Posted October 13, 2013 Hey folks, I need help getting my private server working correctly. The last time I did this, I just used an easy server installer. This is my first manual setup. I used Reality server pack, which had been recently updated with most of the notes specifically mentioning 1.8.0.2. I installed Arma2, installed ARma2OA, installed the patches to 1.62 and then the latest beta patch (108074). I installed the dayZ client version 1.8.0.2. I installed MySQL. I then followed the instructions for manual installation here: https://github.com/thevisad/DayZ-Private-master/wiki/Manual-installation-(advanced) They're pretty straightforward, I was not confused by any portion. The server starts without issue and appears in the server browser. It prompts for password as configured, and seems fine. BattleEye updates successfully. The only thing is, when I try to connect to it from my playing machine, it just hangs at "waiting for host." Black screen. My username in the upper right. I've seen these symptoms reported by others, but can find no relevant fixes so far. Most references I've found say this is a client problem, but I've ensured matching versions all around as well as matching beta patch. I've also tried to connect from two different play machines. Both experience the same issue, and are able to connect to other servers without problem. Halp, pls? Share this post Link to post Share on other sites
TangledScience (DayZ) 3 Posted October 13, 2013 (edited) Double check Battleye, you said it updates in your post but the issue sounds very similar to the Arma server not being able to find battleye in the location specified in the server config / batch file, that or your mission file could be named or placed incorrectly. Edited October 13, 2013 by TangledScience Share this post Link to post Share on other sites
PK Richie 507 Posted October 13, 2013 Read your RPT log, It will tell you everything :)Post it here if you can't understand it. Share this post Link to post Share on other sites
catface.jpg 75 Posted October 13, 2013 Thank you guys! The .rpt file starts out with a lot of this: ======================================================================= C:\Program Files (x86)\Bohemia Interactive\ArmA 2\arma2oaserver.exe== "-nosplash" "-cpuCount=0" "-name=Reality" "-profiles=dayz_1.chernarus" "-cfg=dayz_1.chernarus\basic.cfg" "-config=dayz_1.chernarus\config_0b7b494a.cfg" "-mod=@dayz;expansion\beta;expansion\beta\expansion;Expansion\beta\expansion\addons;@reality_1.chernarus" "-world=chernarus"=====================================================================Exe timestamp: 2013/10/13 00:16:18Current time: 2013/10/12 22:14:45 Version 1.62.95251String STR_MOD_LAUNCHER_ACTION not foundItem str_usract_watch_toggle listed twiceItem str_usract_watch listed twiceItem STR_EQUIP_NAME_24 listed twiceItem STR_EQUIP_DESC_24 listed twiceItem STR_EQUIP_NAME_1 listed twiceItem STR_EQUIP_DESC_1 listed twice It repeats this pattern for various STR_ NAME and STR_DESC item numbers for about 150 lines. Then, it starts these: Updating base class ->Default, by ca\weapons\config.bin/CfgMagazines/CA_Magazine/Updating base class ->PistolCore, by ca\weapons\config.bin/cfgWeapons/Pistol/Updating base class ->Default, by ca\weapons\config.bin/cfgWeapons/ItemCore/Updating base class ->Citizen, by ca\characters2\config.bin/CfgVehicles/Citizen1/ It does this for about 1700 lines, various "base class" updates for items and objects and vehicles and whatnot. Then it starts these: Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/Offroad_SPG9_Gue/Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/HMMWV_Ambulance/Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/HMMWV_Avenger/Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/USMC_Soldier/Unrecognized CfgVehicles simulation in bin\config.bin/CfgVehicles/MTVR/ There are only about 20 lines like that, and then an equally small number of these: Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp/Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp_BaseWeakYellow/Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp_BaseMediumOrange/Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp_BaseMediumPale/Unrecognized CfgNonAIVehicles simulation thing in bin\config.bin/CfgNonAIVehicles/StreetLamp_BaseStrongPale/ Then, these: 22:15:24 Bad special value22:15:24 Bad special value22:15:24 Bad special value22:15:25 Bad special value22:15:27 Bad special value22:15:30 Bad special value22:15:36 Bad special value22:15:49 Bad special value22:16:09 Bad special value Then the log ends. The googles tell me this is probably BattleEye, so I will check things out from that angle tonight when I resume efforts on this. Any other light anyone else could shed in the meantime would be awesome. The only way I can get BattleEye to not print errors to the arma console is to launch the reality "restarter.exe" as administrator. I'm happy to do this as a matter of procedure. Anything else I should check for battleeye? I do have ports 29910 and 29911 UDP open and forwared appropriately, along with port 2302 TCP. My game is showing up in the public browser, which I take as a positive test that they're set correctly. Share this post Link to post Share on other sites
catface.jpg 75 Posted October 13, 2013 One thing I did want to ask about specifically, which did confuse me during the setup: The tutorials I found all said to download and install the DayZ CLIENT. The wiki guide I am following also refers to having the appropriate "client files."So, I installed dayZ client files on the server. This feels wrong, though. There is a Server download for 1.8.0.2, should I be using that instead? Share this post Link to post Share on other sites
catface.jpg 75 Posted October 13, 2013 I've been going back over the wiki a bit, and I think I'm just going to scrap this whole thing and start over. I missed a couple things, like the fact that 64 bit strawberry perl is not recommended. So, maybe I had build problems because I used 64 bit perl. Wish me luck this time around lol Share this post Link to post Share on other sites