IronCross

HAHAHAAH Bloodbath

Solid work

I can't play stable--too much desync going on. Nothing will happen if/when my patience runs out. I won't run DayZ anymore. Probably take a month off, or six. Lots of people already have. LOTS.

It's an official DAYZ forum, what did you expect?

That's one hell of a double-spaced, massive response.. But you never answered my question.

I find you entertaining and you require no brain usage.

Hahahaha. Then you'd definitely shoot yourself if you happened to encounter your twin.

Bandits and heros. You sound like rp f***. Christ, go play a pen/paper RPG.

So tell me folks... when does your patience run out? Mine is wearing thin, especially with the fucking experimental servers down for 24 hours.

The cordoned areas.. what? Did you pull that out of your ass? Terrible. Calling Elektro survivable is ridiculous. Also your semi-RP style is just fucking annoying, haha. Did you have stalker as your religion on your dogtags? There's plenty of good info for a brand new player, but some of this is a little misguided.

--from Rocket's twitter, I'm sure it was posted but if you're bitching read this. Anyone who wonders why the patch has not been moved to stable only needs to play on the experimental and you can see the reasons there. If you are disappointed the update is not on stable, simply go play on experimental and you can see these changes. You also quickly see issues as to why it is not out on stable. Believe me: we want this patch out much more than the community. Because continuing like this is a majorheadache for development as branching and merging becomes an absolute nightmare. This is occurring at the same time as us finishing our planning/roadmap process and starting up our new feature scrums. However, this desire doesn't change the fact that for the patch to be pushed onto stable we must not introduce new serious, game-breaking bugs. Currently we are tracking two new major issues that we see as being blockers: Invisible Characters/Zombies We believe this is caused by them becoming stuck in geometry on client(s) and therefore rejecting new updates. In order to fix this our QA has been going back through different build revisions and checking to see if this occurs so we could isolate the exact point in development it started occurring. That was an extremely labor intensive process and through this we managed to narrow it down to an exact revision that caused the issue. Now that we have found out exactly when that occurred, we start to look into why that happened. Once we fully understand the problem we can design a solution. The problem is that these are not simple issues or bugs, they are complex bugs that can result from a variety of factors. They can be caused by multiple issues, or simply just a symptom of a much wider problem. They are also often very hard to reproduce, and are exceptionally difficult to produce estimates for on fixing. Network pauses roughly every 30 seconds This recently appeared on experimental, and has been noticed by many. What happens is regularly the server stops sending updates for a second or so, which is caused by the server hard-locking for some reason. It lasts only a second before the server starts sending updates again. It looks like desync or rubber-banding for the client. The current most popular theory for this is that the Experimental Server Architecture itself is causing the issue. I.e. the Experimental "Hive" central database simply cannot handle the load, and therefore when a players is killed or dies, the updates are delayed and the server is forced to stop and wait for the central server to respond. I'm vastly oversimplifying the issue but I am sure you get the point. We're again testing this in detail with our 30 fulltime, onsite, QA staff. It's a huge job and it's been a major effort. Edit: Network Pauses... bug has been confirmed as being related simply to the Experimental database not handling the load. The experimental database is not configured for load balancing and is run on simple hardware so it simply cannot respond to servers fast enough. This leaves us with one blocking issue, the first issue. We have a full reproduction and we know the commit that caused it. It's related to network messaging changes. Simply reverting it will probably not work, because the change is complex.

This is pretty dumb. Bicycles are a fuck ton more common than horses. And easier to maintain (your bike doesnt eat)

Go make your own game, OP. Or play Battlefield. All kinds of "snipers" in there.

In an apocalypse, those who have will be set upon by those who do not. That is why 'preppers' exist. Especially in America, where we have grown so accustomed to a life of ease and basic standard of life being high. A small fraction of America would make it through a real hardship of even Great Depression level. So, this game has that dynamic down.

Lots of childish griping in here... I still have a lot of issues and it's damn near unplayable. Not gonna bitch, because I've gotten 200 hrs of quality gameplay from it. End of day, its a damn game. Alpha at that.

Rocket, I get it man. People speak without knowledge and muddy the waters. What I will try to do in this post is provide my symptoms, as well as the steps I've taken to attempt to resolve the issue. I have been playing since late December with little to no issues. I have a decent PC, I am an experienced user and my Internet connection has been stable for the last two years. When I first started playing DayZ with a group, one of our members was having this problem. He would connect, play for awhile, and notice he couldnt see anyone or interact with the game world. He noticed when he was in proximity of any other player he would see desync maxed out (100000). He eventually stopped playing. Fast forward to the FPS issue that has been hotfixed. Around the same time the FPS drop showed up, I've had the same problem, but it has NOT been coincidental with the FPS problem. Oftentimes I will go for ten minutes straight unable to pick up or drop items, or open doors. If I am in a group, they can see me, but I cannot see them or they run in place. These issues exist regardless of what equipment I'm carrying. I've run speed tests, and even run google's mlab tool to check for bandwidth issues. Disabled firewall and run in DMZ for a short time. Issue still reproduces itself. At the end of this month I'll be moving to a different ISP, because I do believe Time Warner here in the States is absolutely guilty of BW throttling. My tentative conclusion is that possibly,due to DayZ's high level of bandwidth required, it drew the ire of my ISP who then decided to throttle it. That is the only thing as a user I can possibly effect at my knowledge level. Good luck, and don't let have an aneurysm from this thread.

The FNX is brand new, brah.

Experimental will give you a different character. And every time you log in you risk losing all your gear.

Ten minutes of play and I've faced three server restarts, resulting in an "authentication timeout" I also suspect I was killed after logging out, due to thirty second timer. Now I have the 2xx seconds before respawn. Not a fun start!

Griefing aint gonna fix it. Have some patience and some faith in the dude. You aint building something better :)

Currently in NWAF, will check coords as able.