drgullen

If you push and hold the ` key, they don't appear?

No, nothing else needs to be done, but what is odd is that on my default server files, that active parameter was already set to 1, I didn't have to enable it. You might try verifying your server files just to be sure you have all the correct versions of the build.

I don't have a vehicles.xml on my server, so I'm assuming you mean you deleted vehicles.bin in the storage_1 folder, is that right? If you delete only some but not all of those bin files, you are essentially creating the equivalent of a server crash, because having only partial bin files in there equates to a corrupted persistence folder, meaning the server ignores it and loads in a fresh world from the XML configurations. How did you increase the number of hatchbacks? Which file did you edit to do that? If you edited the right one and changed the values correctly, you shouldn't have to delete anything to have them show up.

They are not ready to drive yet -- the devs will activate them when they are. Why they are spawning the parts for them, I don't know.

I was able to cure the one cold I've had so far by getting dry and staying put. It was boring AF, but it worked. I removed my wet clothes, replaced them with dry ones, got in a house, shut the doors and meditated for half an hour or so. You start to notice the coughing and sneezing intervals getting longer and eventually, the sicky face disappears and the coughing/sneezing ceases. I didn't have any meds on me -- not convinced they do anything yet -- I just sat down on the floor, went AFK, made some coffee IRL, checked email, etc. and eventually, it worked. I was kinda hoping someone would come in and blow my brains out, but alas that's DayZ for you, you can never find what you want when you want it. LOL

Not true, you can automate the process with batch files. I'm finalizing one now that should keep my server's persistence to within an hour. The batch file keeps checking for the existence of the server exe and, when not finding it, copies over the last valid backup persistence folder and starts it up again. My backups will be taken every hour, so worst-case scenario would be the server crashing in the 59th minute of the hour, which would mean we'd have to roll back 59 minutes to the previous backup. It's still better than losing everything though. My server isn't "up" yet per say -- it is here on my laptop while I continue tinkering and setting up. I plan to put it live soon. I don't think persistence is ever going to be completely fixed because not only can the DayZ Server go down, but the Windows Server machine itself could for whatever reason. If the persistence files were being written when the hardware itself failed or the server OS blue screened as examples, you'd still need a backup of some sort to restore to when the machine comes up again. 100% persistence guaranteed is never going to be a thing regardless of what the DayZ devs fix/change.

Put mag in hand, hold left-click to unload the ammo which will either go into your inventory or onto the ground if your inventory is full. To load the mag, with the mag in your hand, open your inventory and drag the ammo onto the "Combine" section of the picture of the mag and then when your inventory closes, once again, hold left-click and the mag will load the ammo. You can also put ammo on one of your hotbar keys if you want and then you load by pressing and holding that hotbar number.

Press and hold left-click to place it.

Have I tested what? Fully assembled vehicles? If that's what you mean, yes, as I say, for many weeks now, I've been testing them. I've driven them all over the map, log off, shut down the server and then next day, they're still there, so no persistence issues with them. I've not had the "flying car" bug either. I've simulated some server crashes by using the /F switch on taskkill and I notice every time that happens, persistence file "dynamic_000.bin" always goes to 0K. So, if you have a server crash, you absolutely need to copy over some backup storage_1 folder you have before restarting the server, otherwise you are definitely going to lose some stuff. Assuming you have a recent enough backup, all the cars should still be wherever they were at the time that backup was taken. It sucks to have to roll back at all, but it's better than losing everything.

Interesting. I guess I've just lucked out so far and not had the issue. The one difference I'm planning for my server is that cars will spawn already assembled. I've watched too many streams and videos where it just takes forever to assemble the car and I think most people can't be bothered, so on my server, all you'll need to loot are the water, gas and oil to get it running. So, in my case, I edited the cfgspawnabletypes.xml file and changed the definiton of the car to this: <type name="OffroadHatchback"> <attachments chance="1.00"> <item name="HatchbackWheel" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HatchbackWheel" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HatchbackWheel" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HatchbackWheel" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HatchbackWheel" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="CarRadiator" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="CarBattery" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HeadlightH7" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HeadlightH7" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HatchbackDoors_Driver" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HatchbackDoors_CoDriver" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HatchbackHood" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="HatchbackTrunk" chance="1.00" /> </attachments> <attachments chance="1.00"> <item name="SparkPlug" chance="1.00" /> </attachments> </type> I'm guessing here, but perhaps spawning the car complete eliminates the bug, because as I say, I've been playing around with this for many weeks now on various builds (pre- and post-release) and my cars have never spawned in the ground. It's probably a multi-faceted bug where x, y and z all have to be true for the car to bug out. If during my testing, I can make it happen, I'll post my findings here.

Yeah, true enough. I'm looking at where you announced your Killin Zedz server -- is yours still not modded at all? I was just thinking perhaps the car issue is related to modding somehow since mine is not modded and my cars are fine (so far anyway).

I'm wondering if this is related to the modding. I am setting up a server right now -- I have no mods on it as yet and I've had zero issues with cars. They spawn correctly, I can touch them as in add/remove parts like wheels, spark plug, etc. and they don't fly away and they seem to drive as you'd expect them to - well, they're a bit lame traction-wise if they're supposed to be 4x4s but that's another matter. Are you able to temporarily remove your mods and then also temporarily wipe the persistence files and then see if they spawn and behave correctly? I guess another question to ask would be is there anyone who has a non-modded server out there where cars are spawning underground?

This is the first I've heard of this -- they are fine on the server I'm setting up. There is a bug that's been reported where they tend to want to fly on occasion, but never heard of them partially buried or exploding. My guess is some or all of your persistence files are corrupted. As a test, shut down the server, cut and paste the storage_1 folder somewhere else (meaning you'll have a fresh server with no saved loot or characters on the next server start) and then start up the server and see how they look and behave now. If that works, my guess was probably right and you should just delete that storage_1 folder wherever you put it. You could potentially save the characters though if you copy back the players.db file from the old storage_1 folder into the new storage_1 folder that was created on this latest server start. If you've been editing some of the server XML files, you might have messed something up unknowingly. Another thing to try -- verify your files for the DayZ Server listed under Library > Tools in Steam. This will download and replace any server files that have been altered from the official versions. If none of this helps, you should fill out a bug tracker so the devs can look at it.

Same here, the website must be malfunctioning right now.

Well, if this is true, the engine is lacking to some extent, because if I remove their force to 9/20 and set the date to be in June, it still snows rather than rains. It may be that they've simply replaced rain with snow for now, but I was expecting it to be smart enough to know what precipitation type should fall from the sky depending on what season it is. I guess that isn't in yet.

Those parameters worked in .63, but as of 1.0, I think the wind is simply randomized. I have set the weather.SetWindMaximumSpeed value to 5 for example, which should produce only a light breeze, but the trees in game still swayed at times as if being hit by heavy gusts. If you look at the weather section in the vanilla init.c file in 1.0, wind isn't listed anymore. Perhaps extracting and editing the weather.c file as Sy8282 suggested might work, but I think this parameter when listed in the init.c is ignored now.

Mouse over the Library menu in Steam and then select Tools and select the update for DayZ Server -- then the versions will match and it should work.

Have you tried this using GhillieSuit_Mossy as opposed to GhillieAtt_Mossy? Ghillie_Att is just the attachment to the gun part, is it not? Wouldn't Ghillie_Suit spawn the whole thing in one pile? I have no idea to be fair, just taking a stab at it as you suggested.

For whatever reason, the client (your game) froze, but the server still registers your character as being "in the world" at that moment, so yeah, while you were frozen, the guy killed your character most likely. If nobody else had been there, you'd have been more or less in the same spot as you were when your game froze when you logged back in.

Drag the ammo to a hotbar position then, with the gun in your hand, press and hold that hotbar number and up to 5 rounds will load into the chamber, depending on how many were already in there.

Has anyone played around with these yet in the init.c? //INIT WEATHER BEFORE ECONOMY INIT------------------------ Weather weather = g_Game.GetWeather(); weather.MissionWeather(false); // false = use weather controller from Weather.c weather.GetOvercast().Set( Math.RandomFloatInclusive(0.4, 0.6), 1, 0); weather.GetRain().Set( 0, 0, 1); weather.GetFog().Set( Math.RandomFloatInclusive(0.05, 0.1), 1, 0); Not that I want a pile of rain again like we had during the Beta period, but I don't seem to be able to make it rain for more than a few minutes. In Beta, these values were much different and included the option to adjust the wind, which apparently you can't do at all now. Also, there is a reference to a "weather controller" in the form of Weather.c but I have no such file in my server files or in the game itself. If anyone can provide a description of these values -- what they mean and do -- it would be appreciated.

As the devs said, use "taskkill /IM DayZServer_x64.exe -- as long as you don't add the /F switch to force it, the server seems to shutdown gracefully every time (that's been my experience anyway).

Yeah, the thing I noticed with the 1.0 init.c is that the weather is created before the hive whereas in .63, it was the other way around. The other interesting thing I noticed was that the weather is apparently saved in the events.bin file in the persistence folder -- no matter what I changed the weather variables to, DayZ kept loading the previous weather I had. Anyway, like you, I also tried replacing the weather with what was in the .63 init and now I can set it as I like. I haven't had any luck with the wind, however. I can set the max wind speed parameter to something very low to simulate calm winds, yet the game randomly start swaying the trees hard as if it's blowing pretty good anyway, so I think that part of it doesn't work, but with the .63 variables in place, I can set it to any combination of overcast, rain and fog that I want.

It's working for me -- I think you have to delete (or at least cut and paste it somewhere else as a test) the spawnpoints.bin file in the persistence folder (the storage_1 folder or storage_X if you have multiple folders). I think with that file present, it defaults to using the spawn points within that file rather than reading what's in the XML file -- I'm not 100% sure about that, but I know if you start with no persistence folder present, it definitely uses the spawn points in cfgplayerspawnpoints.xml.

Oh yeah, I see it under that name -- spawns at least 2 of them in Military locations. Thanks.