Share This

Status Report 7 February 2017 | DayZ | Official website

We have a new Status Report for you. Brian is talking about known issues and fixes what are we working now and Victor is sharing some news from animation department. We want to show you an interesting thread from our official Forum and you can find awesome song in Community Spotlight.

Contents This Week

Dev Update/Hicks

Dev Update/Viktor

Handpicked: DayZ Forums News

Community Spotlight

Dev Update/Hicks

Greetings Survivors,

This Status Report we’re going to cover what the .61 Live Team are focusing on for Stable branch issues, I’ll touch briefly on .62 – and then I’d like to give a little perspective on the work currently under way for the bulk of the team (Beta milestone).

Rest assured, the development team is well aware of a good deal of critical issues that have popped up on various builds coming through Exp/Unstable and onto Stable branch. Some of them we’re working to address in .61 updates, and some will more than likely have to wait for Beta milestone (as we’re on the edge of addressing some issues in technology and systems that won’t be around in Beta).

The team has been able to make good strides on addressing server crash issues, but we’re also tracking a good number of additional issues that have come in through the Official Feedback Tracker:

Issues with the Central Economy group spawning items and clustering in some areas after extensive persistence uptime

Client side FPS drops from several causes

Issues tied to animation transitions at time of death

Client side network freezing in some cases

Remaining issues with vehicles from Exp/Unstable

“Ghost Infected”

Server Performance Issues

We’re all aware that these issues are critical to everyone playing on 0.61 Stable, and we appreciate everyone’s patience and participation in utilizing the Official Forums and Feedback Tracker to better allow us to track these issues down. Hang in there and be patient, as mentioned before .61 hit Stable – a majority of the team has switched to working on Beta, and some of the issues might not make sense to spend time resolving as we’re working on the .62 and Beta milestones now – but we’ve not given up on addressing them for .61. If you find any new issues, or have new data – please continue to utilize the Official Feedback Tracker, it might not seem like it helps but trust me – it *does*.

For .62 development, we don’t have too much for you in this Status Report – however Adam (Sumrak) is working on putting together some tasty information on the .62 team’s progress on their end for the next Status Report. Currently the .62 team is working on profiling the Chernarus with the new trees, and making adjustments to the forests based upon the data they gather from the profiling tools. There are some additional improvements on the visual fidelity side they are looking into – but I won’t ruin any of that as Adam is looking forward to what he can tell you all in the next Status Report.

It (almost) goes without saying – but the Beta milestone isn’t just a matter of plugging a few new things into DayZ. The Animation System ties into effectively everything you guys do in DayZ, and the New Player as well. Tie into this the goal of total removal of SQF support (The scripting language that DayZ utilizes for most every gameplay mechanic) and the teams undertaking starts to closely resemble a skeletal and critical organ transplant. A great deal of work has gone into recreating all of these SQF scripts and mechanics into the new Enforce scripting language over the last year or so, but even so – the risk and work that is required to coordinate across the team, ensure things are functioning as expected, and discovering exactly what impact the total removal of SQF has against the game is a significant amount of work. We’re all excited (and a bit winded) at all of this, and understand that it may be frustrating not getting the fixes you all want for .61 Stable as fast as you’d like – but rest assured, the work that we’re doing on the Beta milestone will be worth the struggle of legacy bugs on .61.

Lastly, In regards to the Official Feedback Tracker – the BI Webteam has recently added support for logging in utilizing credentials from Facebook/Google accounts for those who might not want to make an additional login just to report issues. We hope this lowers the barrier for some of you that might have data on bugs you’re experiencing, but have held back on reporting them.