detonate

OK, for the benefit of others: I've resolved the issue we've been having that causes multiple DayZ instances to crash when there's already 1 running with players. Not sure exactly *why* but something in 1.7.5.1 now requires separate cfg directories per instance, where as prior we were just utilising 1 cfg dir with multiple cfg files within. Hope that helps someone.

Ports are fine, they show up in the serverbrowser as you'd expect. The issue occurs when people try to connect. Nope haven't copied the .exes, haven't needed to in the past. We just start them with different -cfg values at runtime. From a client POV, you get into the lobby, then sticks on 1KB received of "Receiving Mission File", then eventually times out. Only think I can think of is that it's not loading the right mission/map files properly. ie. all instances are trying to use the same mission file? But the config looks fine and hasn't changed ('cept for the required ver and hostname). However we did generate new mission files as per the update instructions. Edit2: OK I've done more testing (at an offpeak time without others trying to connect), and it seems when a client connects to another instance other than the currently working one, it does get past the 1KB "receiving mission file" and to the next screen, but that's when the server instance crashes. If you guys actually make copies for each instance and it works, maybe I'll try that. What exactly do you replicate?

We've got multiple instances of DayZ running on the same baremetal box, out of the same folder structure, with different cfg files and mapfiles. This has been fine up until 1.7.5.1. Since the update, all instances start up fine, and whichever one has players connect first carries on working. However all the other instances will crash when players join. It's not specific to one or several instances, it's just whichever instance gets players first is the "good" one. Tried a complete fresh reinstall just in case, and still the same dealio. I've not updated to beta 101747 but still no joy. Any ideas? Anyone else successfully running multiple instances with 1.7.5.1? Anyone else having the same issues? (I haven't found any threads when I've looked)

Can you confirm that that current version you linked to works on your servers? Last time we tried it it didn't, so we just reverted to the latest one from the server files and left it. edit: OK have given it a crack, we'll see.

If someone can point me to an accurate method of resolving this I can fix it on the NZ servers. When I first looked for a solution there was a lot of conjecture from players, but nothing solid. Haven't really looked for awhile though.

Game purchase only Kickstarter Community servers

This guy is an IT Technician by trade, show him some respect for Christ's sake! *cough*