saintofthesystem

Talking about these issues a month later, when the teddy bear effect has worn off, is pointless. Those fucking things actually could have contributed. It's obviously wasn't top priority for a hotfix, and the silence means: either deal with it or pull your servers. http://forums.dayzgame.com/index.php?/topic/217766-server-resource-usage-and-crashes-pre-and-post-052/#entry2188280 http://feedback.dayzgame.com/view.php?id=20237

Any form of lock up or crash issue will happen on both high and low population, public or private. Like i've said & shown, undeniable 'lock-ups' aside, a crash error will be witnessed at some point during uptime, and easily be mistaken by players as a somewhat-normal yet oddly-timed reset, especially if logs/data aren't able to be served up. Anyway... The OP showing the worst section of performance was during/after the reverting of the 24-hour time cycle back to standard issue start, without me doing anything, & with no news on what happened with that - Point is, the issues persist and doesn't care what your GSP or settings are. My concern is, while December DevBlogs said server stability & performance was a primary focus for this month, nothing else was said about it other than adding the glanced-over 'Known Issues' note of "server crashes" on 0.52's changelog. Quick turn around there. So while this patch saw more of the same, core system & feature updates apparently fell by the wayside, and still it got shit tons of premature praise. Hell, almost nobody cares about the re-re-breaking of 'eating batteries when you lick them' anymore because that stuff has become expected - but anything to do with persistence, server performance, or time cycles (or any biggie) should be cared about & communicated in detail, especially when it gets worse. But it won't. The alpha cult hood quickly covers the heads of anyone with slight expectations of progressive standards. It would've been praise-worthy to show progress if there was any, instead of sacrifice for more distractive content.

Do you have some kind of data to show your servers are not crashing and then restarting periodically? Crashes and/or resets can cause a timing discrepancy between BEC and reported server uptime, but it could be settings too. By the way, do you have persistence on?

I'm pretty sure all servers are seeing this, although to normal player base it is only noticeable/discernable from a 'reset' when servers crash and don't reset properly, leaving it in a locked up or 'nothing can be interacted with' state. Players not connected at that time will see 'wait for host' until it is properly reset. The server could have as few as 15 players and this can still happen. Most crashes follow with a proper restart, so if people aren't paying attention, they'll think it just restarted early or something. Feedback tracker: http://feedback.dayzgame.com/view.php?id=20237

Now we're getting somewhere, thanks. You don't need a reason, that's fine. I'll repost this here, since they want to delete what I consider legitimate reporting and questioning - instead of addressing it, I guess they can re-delete it here. Then we'll have traction. I want to hear from other people renting servers, or playing on them, that's actually paying attention to - and cares about - the memory leaks and crash cycles. [From Devblog, Week of 01 Dec 14] Today is similar, I'll look at that shortly. This was yesterday:

At first I got tired of gamingdeluxe's bullshit. Now I'm going to say Multiplay is worse. That's just because I'm that needy part of the consumer base, and think I deserve a reply that acknowledges when a server is down almost 24 hours, and want to know what the fuck is going on. It's too much to ask, I tell you. Don't dance with them.

Oh, Bullfuck. Click it.

Just saying that either it's working, not working, or has bugs - all understatements. This feature holy pisses me off, simply because there has been and still is hardly no dev information coming forth about it. GSP's say anything to pacify and close support queries. DevTeam - GSP communication? Take a guess. Nothing is uniform to date. I'll add my wiggle again though. What the fuck is going on or shaping up, what is persistence system data looking like internally, and what/when will the community receive updates on it? ----------------------------------------------------------------------------------------------------------------------------------------------------- Maybe I should've just said: Yeah man, my stuff randomly disappears too. As in not one or a few things, but everything that was ever placed anywhere by anybody - A.K.A. crashes But sometimes, persistence doesn't even really 'crash/reset'... sometimes it takes a step or 2 backwards. Example? Tents that were deployed will be packed up, sitting there, a couple hours later after a restart. Some items placed in one location will teleport back to a previous location. Various other oddities that will just be ignored. Don't say it's player interaction/theft, yada yada, just STFU. ----------------------------------------------------------------------------------------------------------------------------------------------------- Making feedback tickets doesn't get you anywhere. At this point it's like a 'GSP says it's the devs' & 'devs say its the GSP' type of stalemate. Everybody knows it's in development, hell so is every other feature. But persistence needs to get some spotlight shined on it so somebody will shit out some details. Not only tents and current items, but also vehicles and future features all depend on persistence in some fashion. Too many people think persistence is just about how you get loot. Newsflash bitches, it's tied to everything 'immersive' or continuous about this game in the coming months. We apparently see what's been worked on during the last few months of 'dev-blogging'... but I haven't seen shit about persistence or status about an impactful gameworld being priority. They could say it's placeholder, say it's in the new tech, say peanut butter jelly time with a wiffle ball bat comming soonTM. Just put something of substance after that first something. Bohemia isn't Blizzard. 90% of the people that are going to buy the Standalone, have probably already bought it, so information on core features isn't the devil. Unless the team traded the devil they knew for the one they didn't. Oh wait...

We wish megaphones would be implemented after global sound gets ironed out. Let's pretend that we indeed do have a megaphone, and I see you in-game first, and give you my 'word' : *Skrreech* "Fuckhead, yeah you, Fuckhead" <pause to determine if you wanna be my lover and could get with my friends> *Skrreech* "He's resisting arrest" <bullets come from multiple directions to make the arrest> <at this point, that area is a crime scene and anyone following suit is interfering with it even though I'm too far away to hear them, bygod they hear me> #toetag Just kidding. Or am I? Did I take my medication?

It seems like persistence has been crashing out on some private shards, probably public too, where no item stays persistent until server setting is disabled and then re-enabled. Then eventually stops working again, usually the same day depending on activity. Would be nice to see updates on how persistence is shaping up internally, and hopefully a couple fixes/improvements soon.

There was a persistence wipe on .50 patch.

Why would you need to do anything? If you read .50 status reports, it says the server time of year can be set, as on experimental they first tested December and then September for tweaking/data. Apparently all stable branch is now set to August/September. I just want to know how or when this can be done by server admins. Comprende?

Can we currently set up the time of year/month on hosted servers? If so, how?

Yes you think that, but then you think its the server stealing from you, because nobody would steal with this mentality and leave those results. Nobody would take random crap and leave an ammo box, grenade, or whatever else. Nobody would take a fireplace and other 4-8 slot items, but leave an FNX pistol or an optic. Why not just dump everything and take the tent for kicks? Oh yeah, then you think nobody stole it because you're the one doing the resets/relogs to test it and different tents get bit in different ways, randomly.

Not much notice of what to expect in the next few patches for tents/storage/peristence, but what's really going on? This is a referal video on one issue: http://youtu.be/fKIuqfj3Z3c Yet that video still does not explain loosing, say pants with items inside, if that is the only thing stored in a tent. Some of my single items as well as items inside containers which are inside my tent will randomly disappear. This could begin happening after one persistent server restart, or it could be fine for a couple days, but eventually things start going poof. Of course some things still 'reappear' after manipulating the contents after relogging or upon return, but eventually not all will. Stacking items a certain way has not helped after many restarts for me. Any update on these and related issues would be appreciated in the future.