Particle (DayZ)

Indeed that appears to be the case. I'm up and running now, thank you.

I've been trying to update to 0.7.4 as per the email last week, but both of the links in the email have been dead every time I've tried to use them. I was curious if anyone had an idea of where a working download for it is. Alternatively, if 0.7.4 is unavailable now, does anyone know if the new DayZ mod revision can work with the older version of Hive (0.7.3)?

Is there a working manual download page anywhere? The "mirror" seems to be going offline every few seconds.

We're going back to automatic restarts every six hours. I think I've fixed the scheduled launch problem so that we don't end up with multiple instances now. While I say "every six hours" it's a bit of a misnomer. Launches will occur at midnight, 6 AM, noon, and 6 PM central time regardless of when the last start was. If the server crashes unexpectedly, it will re-launch after a 30 second cooldown period. Those relaunches and manual launches will not change the 12-6-12-6 launch schedule.

New RAM is in and recognized. Voice and game services will resume shortly.

Server will be offline for ~30 minutes for a RAM upgrade.

Oh, that's weird. Task scheduler doesn't appear to be terminating the old session like it's supposed to. Right now it's set up to stop the server and start it up again every six hours. I was told this is necessary to keep things from lagging up. I'll have to fix the two-instance thing.

I'll have to see if I can figure out why it's not showing up in DayZ Commander this weekend. --- Thank you all for the compliments, by the way. The server's specifications follow in case anyone is interested: AMD Opteron 6234 (12 Core, 2.4 GHz base, 3.0 GHz turbo) 64 GB Kingston DDR3 ECC/Reg HighPoint RocketRAID 2710 PCIe HW RAID controller 4 x 10K RPM 300 GB HDDs in RAID-5 AT&T Fiber OC3 100/100 Mbps --- I see the task scheduling ended up spawning two instances of the server this morning. heh Let me see if I can fix that...

I'm not particularly familiar with their play style as I haven't played much yet. I put up a server at their request, but you're more than welcome here if you wish. I'll ask them over Steam what their play style is like. --- I've figured out what is happening, just not why. I'm hosting my server on 2302 (standard port), but Six Launcher launches the client with the wrong port specified. It specifies the correct (external) IP but port 18750 for some reason. No wonder it doesn't work. --- Tertiary note: I've set up the server to reset every six hours (midnight, 6 AM, noon, 6 PM). I was told it's necessary for the Arma2 OA server to not start lagging. If this is in error, please let me know.

I don't understand how it is that people do not understand that BattlEye is not affiliated with DayZ. Rocket (and others) say it over and over and over and people still post stuff about how Rocket's BE system is flawed. It's not his ffs. These people need to go here if they need BE support.

Does it work if you join by other means such as using the in-game browser or direct connect? I've seen the same issue before but it appears to be server-specific. Some I can join with SL and others I can't but I can join the ones I can't if I join them using direct connect.

That much is really strange. It does show up in Six Launcher, so it must be listing with a master browser. I tested it myself last night and found the new patch didn't fix the join-from-six-launcher problem. I'm not sure about the in-game browser as I've always been doing direct connect by hostname where it adds the server to the in-game browser manually.

Patch applied. Anyone care to see if you can join from the server browser now?

I received a notice in my email of a new beta patch today. This issue seems to be one of the things it might address. The wording was a bit vague, so I can't be certain. I'll apply it tonight and see what happens.

No luck here with my server. In-Game Browser -> Wait for host Six Launcher -> Wait for host In-Game Direct IP -> OK / Works fine I'm running beta patch 95248 with Day Z v1.7.2.3. I don't see any NAT negotiation errors or anything, but it's like the master server is reporting the wrong address or something. Since direct IP joins work fine and people can play if they do that, the server itself must be working. It's also worth noting that the server does list on the master browser list but always has a 9999 ping. Once in-game, ping shows reasonable values. If a person does a direct IP server add in-game, it also shows a ping there. It's only when using the master browser list that things break down.