Contents This Week
- Development Board Spotlight
- Dev Update/Hicks
- Dev Update/Peter
- Dev Update/Mirek
- Dev Update/Viktor
- Community Spotlight
Dev Update/Hicks
Greetings Survivors,
First off let me apologize for the status report being pushed a day, I was unfortunately ill over the last few days - and wanted to ensure that the data in the Status Report reflected the most up to date state of our 0.61 branch, and where we were with it.
Yes, we are still working on destroying the last few remaining issues preventing us from pushing 0.61 to experimental. As is usual, I'm going to walk you all through what those issues are in this Status Report so you're aware of what they are, and what it is that is keeping 0.61 from hitting the experimental servers. Once we go over those, I'm going to spend some time discussing points made over on our forums in regards to status reports, and feature set backlog so as to address some discussion I've read on the community side regarding those. In addition to that, Peter will spend some time sharing his excitement for future changes to the animation system, player controller, user actions, and so forth, Miroslav will discuss some of his teams current tasks, and Viktor will elaborate on some of the work the animation team is focused on for builds past 0.61.
As of this morning, we're looking at approximately 11 open must fix issues, are regression testing 5 other issues that have been flagged as resolved by the developers assigned to the issue(s).
Taking a look at what exactly that means:
Current Must Fix Open Issues:
- Client crash after exiting title
- Player SFX sounds near silent
- Players can become severely out of sync
- Some firearms not firing on first mouse click
- Player position stuttering under 100+ ms network conditions
- Some lighting conditions not casting proper shadows
- Known 0.60 item duplication methods
- Magazine capacity issues
- New methods for players swimming in ground
- UI Zeroing not present
- Glock muzzle flash / SFX not present for other players
Obviously some of these issues are far more critical than others, and some are new. Over the last few weeks we've been fairly aggressive with some of our bug bash sessions, and while it is most definitely frustrating for all of us - I'm very pleased with the fact we've been able to track down some of these critical issues. For example, the players out of sync issue (#3 on the above list) took a good deal of time to find a proper repro on, but the behavior it caused makes for a total break down of network messaging between two players. Causing some animations, and sounds caused by other players to not show up properly for several minutes. (Think gunshots, or player position) which will only lead to incredibly frustrating gameplay and is something I absolutely do not want to see on the Steam branches. Tackling known methods for duplication, animation glitching, and so on are also absolutely critical to get resolved - and left unchecked will do damage to both the economy, and player experience in the time between new builds being pushed to Steam.
In addition to those, the issues we're currently regression testing include issues with player temperatures / modifiers, player sounds, and several serious client crashes. The player temperature issue is something I've spent a good deal of time focusing on, and discussing with Peter's design team on. As I feel that both resolving the issue present on 0.60 stable for hyperthermia, and pushing towards providing players on 0.61 an actual environmental risk (more towards hypothermia being a risk when wet and or dealing with severe cold and improper protection against those elements) is absolutely important.
While those above issues are regression tested, and fixed by the appropriate developers, Peter and I have also gone over behaviours of per player dynamic spawning, and what the technology of the Central Economy will allow us - and have pushed for changes in that area to switch to a more area based trigger rather than per player, to reduce player ability to try and meta game the system.
Recently I've been pushing myself to have more of a presence on our official forums, and engage actively in discussion on the project, gameplay, mechanics and so on with the users over there. As well as sharing experiences and details of the ongoing 0.61 internal testing. I hope at the very least more of you will read the posts over there, if not actually register and participate.
Speaking of the forums, I want to revisit some key points I've made over the last few months in the "A Few Thoughts On" posts. Specifically, in regards to Status Reports, and Pending Feature/Content updates.
As many of you may recall, or have noticed - we made changes to how we communicate "new things" in the Status Reports. From the old method of talking about whats to come in DayZ as soon as we've settled on a design, or may have a model ready, to specifically focusing on what is upcoming in the very next build to be pushed to Steam.
I know some of you haven't necessarily enjoyed this change, but I honestly feel it is a much safer approach to managing hype, and not giving people false hope on how soon they might see something in game. Now, I do feel there is however some compromise on our part that can be made - which is why I'd like to compile a 1.0 feature set we can keep on our forums that will give people an idea of exactly what to expect of the final version (within a margin for error of course), and I hope this will help reduce some of the confusion. I'll need to sit down with Eugen, and the leads responsible for each department before publishing this, but I hope it will serve to answer some of the questions I've seen out there.
Which brings me to my next point.
Just because Status Reports are not touching on a major technology change, or new pending feature set does not mean it is not being worked on. As I mentioned above, we focus the Status Reports on progress towards the next major build to be pushed to Steam - and does not cover changes that are slated for builds to be pushed to Steam past that. A perfect example would be the new animation system, player controller, and user actions. The developers responsible for this have been working their fingers to the bone day in and day out, and we *will* be talking about it and showing off examples once we reach the point in which we are focusing on those updates for the next major build update for Steam.
In addition to that, we have a *significant* content and feature backlog that is dependant on these systems - and as Peter will discuss below, we are at a point in which it does not make much sense to create systems, or address non game breaking issues in the old SQF script and hierarchy. I, and the rest of the team are all very aware of how frustrating this might be for many of you. We're all right there with you, but the work we are doing and have been doing this year represents *massive* changes and the introduction of the major key points for DayZ's new Enfusion engine.
We're not going anywhere. The developers who work on DayZ are some of the most passionate, dedicated, and hard working folks I've ever had the pleasure of working with. We love this game, we love the stories you all create in the world of Chernarus, and I believe I speak for all of us when I say we have the most absolute faith that all of our hard work is going to make DayZ a game that is truly worthy of the dedication and love you have all shown it throughout the trials and hardships of public development.
We might not always agree - all of you that make up the DayZ community, and I - but I don't think I could ask for more amazing, and dedicated fans for the project - and I wouldn't trade you all for the world. Truly, thank you for being there with us through the ups and downs. I can not wait for the adventures we will all have together.
0.61 Milestone Goals:
- Server Login Queue
- Ready for experimental branch testing - no current issues preventing this at this time.
- Merge of New Audio Technology from Arma 3 Eden Update.
- Technology successfully merged into DayZ branch. Ready for further testing on experimental branch.
- Update of Weapon Sounds for New Audio Technology.
- All current firearms configured - Audio team is now focused on addressing must fix issues for 0.61
- Dynamic Spawning of Infected.
- Testing complete on initial implementation, Programming team is now making the requested changes described above to area triggers in order to provide the Design team with the requested functionality.
- Predators (Wolves)
- Internal Testing is very optimistic, several fixes to behavior have been merged over - and programmers are focused on addressing several server crash issues potentially tied to the predator AI.
- Dynamic Shadows
- Last few issues related to proper shadow projection are being focused on now, once these are resolved we should be ready on this specific feature.
- Network Synchronization Improvements
- The gameplay programming team is currently focused on addressing the previously mentioned issues with 100+ MS connections having jittery gameplay in some situations, as well as tracking the recently discovered repro steps for causing player to player sync to fail. Once these issues are resolved, we should be good to go.
- New Server Browser
- Functionally this is ready, however while the must fix issues are addressed, several small UI changes have been made to make the new server browser easy to use and understand.
- Brian Hicks / Creative Director
For the full Status Report, please use the following link: http://dayz.com/blog/status-report-28-sept-2016