Skydive (DayZ)

Have any other server owners / admins noticed players being falsely kicked for "Seagull" in the createvehicle logs since updating to 1.7.3?

FYI DayZ Team: The site front page is still indicating the 1.7.2.6 as current download version.

Read his post more closely.

The downloads may not be ready yet. I keep refreshing the main DL server and one of the mirrors and the file size continues to increase.

I've run DayZ servers several different ways. For a standalone box, I've run it on a i7 920 overclocked to 4GHz with 8GB mem and using just a WD Velociraptor drive. It ran very well on that setup. Currently I have been running DayZ server in both VMware and Xen cloud environments I have built from a lot of Dell R900 boxes and storage is run off of a fibre channel SAN and also a iSCSI SAN. In the VM environments, I give the server instances 8 cores to work with. In VMware that is 2 virtual sockets, each with 4 cores and in the Xen environments it's 8 CPUs. On both platforms they get 8GB of RAM which so far has been more than enough, but I leave it at that to allow overhead in case it is needed.

Is there any plans for the standalone to use DX11??

Where are the updates? I can't find any updated client or server links.

Hey everyone, I'm trying to find some definitive information on where working/repairable helicopters spawn. On my server, some players repaired the one that spawned on Skalisty Island and flew it away. A couple days later myself and a few others found it, refueled it and flew it around. Unfortunately it ended up crashed and we have not been able to locate it again. I have read various posts on where and how often the helicopter will spawn. Can anyone confirm if it ONLY spawns on Skalisty and if it is crashed, does it actually take a week before it will respawn?? Thanks!

Hey all - Can any server operators lend a hand in setting up a Namalsk server? I run a Chernarus hive server and a Chernarus private hive server and now I want to set up a Namalsk server, but the instructions on the Namalsk site are a little bit lacking in details. Would anyone with experience setting up / running a Namalsk server be willing to provide some assistance? Thanks, Skydive

As mentioned before, this sometimes happens when the server is restarted and does not properly communicate with the hive server usually because NAT negotiation fails. Another server restart will usually fix this. After doing a lot of trial and error testing with the tents, my formula for getting the tents to "stick" when I place them is to first pitch the tent, (DO NOT SAVE THE TENT EMPTY!) place at lest 4 items in the tent and then save the tent. As long as I have used this method, I have not lost a tent or the loot inside it.

Date/Time: 9/19/2012 12:30am EDT [GMT -4] What happened: Crashed helicopter when server experiencing desync from hive. [Crash occurred over a week ago] Came back to crash site to see if helicopter spawned there since crashed vehicles are currently spawning where they were crashed. Managed to restart the server several times to find location of the helicopter crash and witness what has been happening to the helicopter. When it spawns, it is 3 to 4 meters in the air, drops out of the air to the ground and then explodes leaving no trace it was ever there. Please view the youtube recording I made to demonstrate this scenario. http://youtu.be/iqtECLao45g Where you were: Near the red warehouse in Lopatino. *Current installed version: 1.7.2.6 / Hive 0.7.4 Beta build 96895. *Server(s) you were on: US47 *Timeline of events before/after error: Crashed helicopter when server experiencing desync from hive. [Crash occurred over a week ago] Came back to crash site to see if helicopter spawned there since crashed vehicles are currently spawning where they were crashed. Managed to restart the server several times to find location of the helicopter crash and witness what has been happening to the helicopter. When it spawns, it is 3 to 4 meters in the air, drops out of the air to the ground and then explodes leaving no trace it was ever there. Please view the youtube recording I made to demonstrate this scenario. http://youtu.be/iqtECLao45g

Here is the response: Me: "One last question for you. Should these problems be fixed for earlier beta builds of ARMA 2 OA as well? I have had others ask this on the dayzmod forums." BE: "It has nothing to do with the game version, so yes."

I am running on the 97771 beta build and the problem has been fixed with this build. I cannot speak for earlier versions. EDIT: I just sent another email to BattlEye to ask for clarification on this. I'll update once I have a response.

I was just communicating with BattlEye on this issue and a couple others and worked with someone at BE to resolve this. Everything should be working correctly now and no longer receiving error messages about the BE Master either.

You might try looking in your createvehicle.log file and get the name of the vehicle from there, add it to your publicvariableval.txt file so that the players will get kicked if they try to spawn that particular vehicle.

Unfortunately, this is true with all the vehicles right now. Until the DayZ devs release a fix, there really isn't anything that can be done.

LOL! I want to see the vid of the bus flying away if you have it.

I only put "scrubed" in there to take out the UID. It probably doesn't even matter. You logs definitely indicate that the helicopter is blowing up on server restarts.

Their web site is currently down.

If you're not seeing that first line when you do a server restart, it may be missing from your mission file. Only thing I can suggest for that is to open a ticket so your mission file can be checked.

Did you try putting the bus under it? Unfortunately, you have to get it in just the right spot or you blow both of them up as I'm sure you saw in my video.

In the case of the helicopter, they explode and leave no crash site behind. Nothing to save.

Here is how you can tell if you are getting a helicopter spawn on the server and if it is spawning correctly or blowing up each time the server is restarted. Check your .RPT file for this when it is started up. (helps to delete everything out of it while it's shut down so it's a clean slate and easy to locate this information) If your mission file is set up correctly and the hive server is instructing your server to spawn a helicopter, you will see this: 8:35:46 "HIVE: Starting" 8:35:49 "HIVE: Request sent" 8:35:49 "HIVE: Commence Object Streaming..." 8:35:50 "OBJ: "1318455"UH1H_DZ" You may also see this near the end of the startup: 8:35:54 UH1Wreck_DZ: MainTurret - unknown animation source MainTurret 8:35:54 UH1Wreck_DZ: MainGun - unknown animation source mainGun 8:35:54 UH1Wreck_DZ: Gatling - unknown animation source Gatling This is okay. It is just the spawn of a helicopter crash site. If you see this next set of lines in your .RPT log file, it means your helicopter is bugged and exploding on each server restart. 8:27:57 "HIVE: UPDATING OBJ: [1aec4100# 1055265: uh1h.p3d,"damage"] / UID: "scrubed"" 8:27:57 "HIVE: UPDATING OBJ: [1aec4100# 1055265: uh1h.p3d,"damage"] / UID: "scrubed"" 8:27:57 "HIVE: UPDATING OBJ: [1aec4100# 1055265: uh1h.p3d,"damage"] / UID: "scrubed"" 8:27:57 "HIVE: UPDATING OBJ: [1aec4100# 1055265: uh1h.p3d,"damage"] / UID: "scrubed"" 8:27:57 "HIVE: UPDATING OBJ: [1aec4100# 1055265: uh1h.p3d,"damage"] / UID: "scrubed"" 8:27:57 "HIVE: UPDATING OBJ: [1aec4100# 1055265: uh1h.p3d,"damage"] / UID: "scrubed"" 8:27:57 "HIVE: UPDATING OBJ: [1aec4100# 1055265: uh1h.p3d,"damage"] / UID: "scrubed"" 8:27:57 "HIVE: UPDATING OBJ: [1aec4100# 1055265: uh1h.p3d,"damage"] / UID: "scrubed"" 8:27:57 "HIVE: UPDATING OBJ: [1aec4100# 1055265: uh1h.p3d,"damage"] / UID: "scrubed"" Currently, ALL of the vehicle spawns are bugged. They never reset after being crashed / destroyed. After a server restart, they will spawn at the point they were wrecked / destroyed.

If you are changing IP addresses, you will need to get the new one whitelisted. Otherwise, simply set up the new server the same way you did the old. (copy your config files, etc.) The new server will access the same data off the hive as if it was never down.

Take a look at this thread I created. Had the exact same problem and solved it. http://dayzmod.com/forum/index.php?/topic/92934-helicopter-spawn-bug/#entry873687