Status Report - 11 Oct 2016

Contents This Week

• Development Board Spotlight

• Dev Update/Hicks

• Dev Update/Peter

• Dev Update/Viktor

• Community Spotlight

Development Board Spotlight

Steam post image

Dev Update/Hicks

Greetings Survivors, I know a good deal of you are reading this hoping to see somewhere in big bold letters that 0.61 is hitting experimental/unstable branch *right now!*. Well, let me derail that train right away. We're not quite there yet. Fortunately in this Status Report I'll do my best to fill you guys in on what the dang hold up is, and our progress against getting it onto experimental/unstable branch since the last Status Report. In addition, Peter will be talking briefly about our designs for the DayZ Launcher, and Viktor will be talking about some of the animation teams work towards the implementation of the new animation system. As well, the Trello should have some new renders of the CR 550 and its magazines, as well as an updated image of the current look of the server browser. Steam post image Over the last two weeks the team has been doing almost daily all-hands multiplayer tests in an effort to isolate the remaining blocking issues getting us to experimental/unstable. Those issues specifically are fundamental to the base gameplay of DayZ. Namely server side performance, and player-to-player synchronization. I'm sure some of you are wondering why we're currently fighting new issues related to synchronization of players, as one of the milestone goals for .61 is just that - improving and reducing the chance for client/server desynchronization. The work Miroslav, and the gameplay programming team have been doing in this area has made massive changes to the communication process between client and server for DayZ - and it has most definitely changed how a lot of the behaviour is manifested client side. While the improvements in client/server synchronization have been outstanding (and lets hold our breath until the larger testing pool gets ahold of them to be safe) they have (not unexpectedly mind you) caused new issues. Thanks to the frequent all hands MP sessions we've had over the last few weeks, we have isolated repro steps and proper bug data on all of the ones we have encountered. As we get closer to .61 hitting experimental/unstable and look at the road beyond .61, towards massive engine and gameplay changes such as the new animation system, player controller, user actions, and so on we have to be very aware of the fact that huge changes like that are going to take time to get ready for Steam, and thus we have to make sure that the build that you'll all be playing while we work on that is as enjoyable and functional as we can make it. We're all very aware that the journey we've all taken together in Early Access has not been the easiest, and can be massively frustrating at times. However, speaking for myself I think we've opted for the harder road in the short term, but the road that leads to the best final product - and always keeps the focus on 1.0 being the best DayZ it can be, first and foremost. Enough rambling from me though, lets dig into exactly what our blocking issues are for .61 (and keep in mind, these are Must-Fix for Stable branch, not all of these are must fix for Experimental/Unstable)

• Player SFX significantly quieter than others: (Fix for this is in testing now)

• Network: Players can become severely out of sync with each