HomeGamesUpdatesPricingMethodology
Steam News13 April 20188y ago

Status Report - 13 April 2018

Latest Development news from Eugen, small teasers of the upcoming changes to radios and other VoIP devices, as well as the final particle effects for gunshots, and also a nice summary of our trip to PAX East!

Full notes

Full DayZ update

Read the full published notes in a cleaner layout. The original post stays linked below.

What changed

1 fix0 additions0 changes0 removals
  • Performance
fixedDev Update/EugenDear DayZ players. All of us here are both playing and tweaking the version for the first Stress Test. You might be asking why it's not out yet, and how on earth we are enjoying it and not sharing that with you? :). The current state of the build, although fun and quite consistent, is still a bit unstable. And what I mean by unstable? In the worst gunfights with large numbers of players and looting, we can still see at least up to 10 different crashes averaging in up time of less than an hour . We fixed about 500 bugs so far for this Stress Test alone, and there is about 50 left. About 10 of those are crashes that have been plaguing our most recent internal playtests. The good news is that we were finally able to debug the reasons behind these, and are working on fixes as you read this. Steam post image Quick look at the issues that need fixing for 0.63 Experimental as of this afternoon (not including features that still need to be implemented). Click to Enlarge Once these fixes are confirmed, and if nothing else pops up (usually does, but fingers crossed!), we will evaluate the state of the build again and start with Stress Testing. We are as anxious as you to get this ball rolling :). Now for the work invested into things that are not launching with either Stress Tests or with the first Experimental build: there are about 1000 bugs fixed so far for Experimental and we are doing some heavy work on UI visuals and functionality to go beyond the basics needed to develop on the new engine. Jumping has got into the game with its first iteration and will be followed by climbing later as we polish animations and possible edge cases where players get stuck. On the notion of having other means of movement rather than walking and running, we are still working on 0.63 vehicles, and also the first helicopter iterations for internal testing . These are still heavy work in progress as vehicles, base building, and several other features are still waiting for a commit (= implementation to the main game code) of technology that we have mentioned a couple of times: enabling hierarchy between entities in the game . We will move on to that commit once we confirm that there are no larger issues during Stress Tests. Just to give you some scope (since I started using numbers) over the years, we have tracked around 30 000 issues and resolved about 25 000 of them, where resolving means that some have become irrelevant on their own either due to change of tech or design (Expired, Won't fix, Duplicate, As Designed and other resolution types in the chart below except for Done or Fixed). Part of the remaining unresolved issues is also related to post 1.0 content and features:

Latest Development news from Eugen, small teasers of the upcoming changes to radios and other VoIP devices, as well as the final particle effects for gunshots, and also a nice summary of our trip to PAX East! It's not Tuesday, but it's still Status Report time, so let's read!

Contents This Week

  • Dev Update/Eugen

  • Dev Update/Jan

  • Dev Update/Boris

  • Community Spotlight

Dev Update/Eugen

Dear DayZ players. All of us here are both playing and tweaking the version for the first Stress Test. You might be asking why it's not out yet, and how on earth we are enjoying it and not sharing that with you? :). The current state of the build, although fun and quite consistent, is still a bit unstable. And what I mean by unstable? In the worst gunfights with large numbers of players and looting, we can still see at least up to 10 different crashes averaging in up time of less than an hour. We fixed about 500 bugs so far for this Stress Test alone, and there is about 50 left. About 10 of those are crashes that have been plaguing our most recent internal playtests. The good news is that we were finally able to debug the reasons behind these, and are working on fixes as you read this. Steam post image Quick look at the issues that need fixing for 0.63 Experimental as of this afternoon (not including features that still need to be implemented). Click to Enlarge Once these fixes are confirmed, and if nothing else pops up (usually does, but fingers crossed!), we will evaluate the state of the build again and start with Stress Testing. We are as anxious as you to get this ball rolling :). Now for the work invested into things that are not launching with either Stress Tests or with the first Experimental build: there are about 1000 bugs fixed so far for Experimental and we are doing some heavy work on UI visuals and functionality to go beyond the basics needed to develop on the new engine. Jumping has got into the game with its first iteration and will be followed by climbing later as we polish animations and possible edge cases where players get stuck. On the notion of having other means of movement rather than walking and running, we are still working on 0.63 vehicles, and also the first helicopter iterations for internal testing. These are still heavy work in progress as vehicles, base building, and several other features are still waiting for a commit (= implementation to the main game code) of technology that we have mentioned a couple of times: enabling hierarchy between entities in the game. We will move on to that commit once we confirm that there are no larger issues during Stress Tests. Just to give you some scope (since I started using numbers) over the years, we have tracked around 30 000 issues and resolved about 25 000 of them, where resolving means that some have become irrelevant on their own either due to change of tech or design (Expired, Won't fix, Duplicate, As Designed and other resolution types in the chart below except for Done or Fixed). Part of the remaining unresolved issues is also related to post 1.0 content and features:

A quick look at the issues that need fixing for 0.63 Experimental as of this afternoon (not including features that still need to be implemented). I'm excited about what's to come with the

Source

Steam News / 13 April 2018

Open original post

Changelog.gg summarizes and formats this update. How we read updates.