Another week for the team pushing towards a stable release. We considered releasing a version to stable branch mid week during maintenance, however there were still two serious issues to fix. The first was related to the testing architecture not being suitable for the large number of servers we were supporting on experimental, and the second related to the invisible zombies and players.
Invisible players and zombies
Fixing the invisible players and zombies was a product of moving to the client/server architecture but retaining some legacy aspects of the architecture. To solve this we have been hard at work continuing to revise the way the game works. A workaround we have implemented is that when desynchronization occurs between client and server, now the server will enforce the players new location by ignoring the clients reported position and teleporting the player to it’s position.
What occurred was that sometimes the straight path to a location was blocked due to desync on the server, i.e. the path on the server was different from the path on the client. This could result in players getting stuck in walls on the client (or server) and issues occurring.
Fireplaces and Emissive Improvements
One key area for our survival focus has been cooking and the ability to make fireplaces. In order to do this we have created a new system for dealing with “emissive” textures that allows us to implement a mask for emissive, as seen in the picture above the result can be very stunning. This has been combined with heat haze to produce some excellent results. Players will be able to make normal fireplaces, as well as upgrade them to makeshift ovens such as below:
Our designers are now working with our art team to implement all these changes so that players are going to be able to hunt and cook in order to survive in the DayZ landscape.
New towns in Chernarus
Our map team has been very busy, here are some sneak previews of some new areas that are coming in the next update:
New Weapon Content
Our art team have been extremely busy while we work on fixing the bugs associated with our current build. Focus is currently on supporting the designers with their survival features, such as the craftable PVC bow, fireplaces, and cooking. However we have also continued the excellent work done with weapons models, here are a selection of pictures below showing progress.
We’re nearing completion of the AKM and the model was a true labor of love by @artguyharry. We’re working on staging the model now so its compatible with the attachment system and we really hope to bring variety to the possible configurations. By default the AKM will have wood furniture but we also noticed a great deal of customization in the AK civilian market and wanted to bring some of that more modern flare as well. A side-mounted PSO scope is being developed in tandem which players will be able to mount AK-pattern weapons.
Mouse acceleration and player control
We have been changing the way the player controls their character to improve playability. There was an issue with mouse control that affected many users of high DPI mice which we have now fixed. Changes to character turning should now also be consistent with how freelook works, which was taken from ArmA3. So we hope that this will improve the situation for players although we have more work planned on this.
Physics and Arrows
Continued work on our physics engine means that not only is throwing now nearly complete (it is now functional at a basic level), but it also means that ragdoll is very close to being a reality in experimental branch. This will open up many areas of development.
Work with the bow and arrow has come along very well. Bolts and arrows can now stick into their target, whether player or the ground, or an object. Additionally, animation changes means that we can now make the drawing and firing of a bow look better than ever before improving the versatility of our “gestures” based animation system.
Animals, collisions and zombie pathfinding
We now have an entire team, based in Bratislava, that are working on animals, collisions, and zombie pathfinding. This is a longer term task as it will require new thinking and new ways to fix the problem. We’re excited to see what the team can bring in the coming months.
Persistent Loot and objects
This was close to being implemented fully when we discovered some issues with the central server architecture that would becoming more serious for performance if we went live with it. These are being solved now and we expect to be trying some of those performance optimizations on the central server this Wednesday.
Where is the new build?
We are committed to not releasing builds onto stable to introduce new game breaking bugs. Now that we’ve fixed those bugs, we’re internally verifying and fixing any new bugs that have been introduced. We will do an unscheduled update the moment we are confident we have a suitable build to release
What is next for the future?
Once the current build is stabilized we want to finish up on our “survival” push for the month. This means hunting and cooking finished and process on our “survival combat” which involves the bow and arrow, crossbow, improvised weapons, and thrown items. In the more distant future we’re already planning for vehicles and barricading systems.
We look forward to finishing our work on the current build and having it out on stable!
This week saw us start our “survival” gameplay focus. This means most of our gameplay development focus is on refining the survival aspects of the game. We detailed some of the initial work for this last week.
Trying to get 0.37 to stable
Our main focus this week was to deploy a new version of the game to stable branch. We have two public “branches” of code, stable and experimental. A deployment to stable branch of the latest version of the game was scheduled for Wednesday, however we were not happy with some of the issues that remained.
Three major code changes have been occurring. We have been changing the way collision works to solve a number of bugs, such as shooting while prone colliding with the world and zombie collisions. Also our new physics system has been implemented, allowing us to have throwing, dragging, ragdoll, and even vehicles. In addition, a new guaranteed network message system has been developed to solve network issues, improve client/server performance, as well as reduce the “desync” issues experienced by many.
A number of bugs came out of these developments, two of which cause situations where players and zombies can become invisible to some clients. We want to solve this issue before we deploy to stable. You can try the current version out for yourself on experimental branch.
Progress continued with the development of several different kinds of fireplaces, and has moved onto creating assets for constructible ovens. These items will be persistent in the world, allowing the player to cook many things. The temperature system developed in the engine has been refined to have correct return from hot or cold to ambient temperature.
A new area of work commenced this week is combat directly supporting survival. This includes throwing items, bows and arrows. We now have a great new animation for throwing, and the system developed for this will allow us to support proper animations for bows (e.g. drawing bow back, awaiting player input to fire).
The next week
Both Survival Combat and Cooking are our gameplay focus for the next few weeks, with our primary goal to get 0.37+ deployed to stable as soon as possible.
We’re also looking ahead further now towards how to best position ourselves to release vehicles, barricading, and advanced physics. It’s exciting times for us all here and we can’t wait to show what’s coming in our next video blog!
0.37 will be deployed to Stable during scheduled maintenance on Wednesday, 5 March 2014 GMT. Changelog will be distributed at that time.
Bug Fixing progresses
This week most of the team has been focusing on key bugs, and some of the team have started our first new feature scrum.
New Team Members
We are inducting a large number of new people to the team, effectively doubling the whole project. Here are a few screenshots, and a short rundown on some of the key activity for the week.
Development of Cooking System Starts
This week we started on a cooking system. Heavily inspired by the outstanding cooking system in Project Zomboid, this will be part of a wider push in March to focus on Survival aspects of the game in general. You will turn your cooking device on (fireplace/stove) and then place the items in it.
The items will slowly heat up, and when at the required heat for the required period of time, they will become “cooked” and/or turn into something else (such as soup). Items can become overcooked, and items can also become cold via some process (this will be looked at later).
We’re very excited by the possibilities for this system.
In the past week animation team was mainly focused to bring all two handed melee animation in game. We have added gestures for two handed tree, evades and other missing animations. Our next goal is to polish those and finalize them all. At the same time we have created new reloads for Ruger MKII, added stab attack with hay fork and worked a bit on new zombie animations which we would like to introduce somewhere in march. There was couple of bugs fixed, some glitches and animation graph improvements.
Emissive material and masks
Our graphics programmer spent some time redoing the way emissive materials work, this will allow us to better support the new fireplace mechanics that are being worked on.
Guaranteed Network Messages
We now have a new system we are testing internally for sending guaranteed updates across the network. This is very important as we believe this will reduce the problems for those who are experiencing severe desync. We are still testing this internally, and it will be sent out to experimental for more testing next week.
Much more is ongoing, and we look forward to presenting our Roadmap for the rest of the year very soon!
The DayZ Alpha is available for early adopters from Steam for 23.99 Euros. Please be aware that our Early Access offer is a representation of our core pillars, and the framework we have created around them. It’s a work in progress and therefore contains a variety of bugs. We strongly advise you not to buy and play the game at this stage unless you clearly understand what Early Access means and are interested in participating in the ongoing development cycle. Please keep in mind that we do not expect to reach Beta status sooner than the end of 2014.
The initial weeks of the DayZ Alpha were really busy despite the holiday season. We’ve received incredible support from you, DayZ users, with over 875 thousand copies of the game sold in just three weeks and thousands of useful posts and reports that already led to some notable game improvements during the holiday period with much more to come in 2014. The level of support and confidence we have received from the DayZ community makes us even more dedicated to the game than we were in the past 16 months of DayZ standalone development.
We didn’t want to compromise on the brutal and unforgiving nature of the early days of the DayZ mod so we’re very surprised to see such interest as this clearly is not a game for everyone, especially considering that there are some radical changes under the hood in comparison to the mod. These changes may be more subtle than when comparing the relatively limited amount of content in the standalone game against the mod in its very mature state itself, but it should be much more valid in the long term for the overall game experience and of course we’re aware how much more work is ahead. We’re already seeing unbelievable player stories happening every day in the game even in its very limited Alpha and we’re focused to make huge progress in 2014 on many areas of the game. In the short term, we’re going to focus on the most critical problems you’re experiencing atm and at the same time we’re going to work on the road to the DayZ Beta. We’re going to re-evaluate the roadmap plans in the second half of January but here is a list of the existing top priorities on our to-do list to make DayZ really meet or hopefully exceed your expectations:
Server performance, stability and security
Animals & hunting
Cooking & gathering resources
Playable user customizable vehicles
Player created constructions in the environment
More complex interactions with the environment and crafting options
Streamlined user actions and interface
Control and animations expanded and improved for fluidity
Upgraded graphics and physics engine (including ragdoll, etc.)
Support of user mods and more flexibility for user hosted servers and game types
Happy New Year and thank you all for the incredible support so far, without the DayZ and Arma user communities, this game would never be possible!
DayZ Alpha has been available for early adopters since December 16th from Steam for 23.99 Euro. Please be aware that our Early Access offer is a representation of our core pillars, and the framework we have created around them. It is a work in progress and therefore contains a variety of bugs. We strongly advise you not to buy and play the game at this stage unless you clearly understand what Early Access means and are interested in participating in the ongoing development cycle.
The second week will be much calmer. Most of the team members are going to take a well-deserved vacation week with their families, so please be patient with us for the much slower pace in the coming two weeks. Thanks to all for the incredible support and interest in the game so far. 2014 is going to be an exciting year for DayZ. Merry Christmas.
Dean “Rocket” Hall during his Puja ceremony today, proceeded by a local lama. Flour is spread on each others faces, hopefully signifying the individual reaches old age. Rocket is completing this devblog from Everest Base Camp during his attempt on the summit of Mt Everest.
Devblog from Everest base camp!
I’ll start with a huge thank you to the DayZ development team who have continued development at a breakneck pace despite me being off living a lifelong dream to climb Mt Everest. Although the timing is poor for my sabatical, it is not something planned on a whim and involves non-refundable costs of up to $100k.
So here I am, at Everest Base Camp, 5400 meters, writing what I am sure is the highest ever devblog from the ground! This is largely able to occur because of Matt Lightfoot, the youngish looking chap who is our tireless Production Assistant. Both him and others have continued to send me progress updates and approvals, which I am accessing via a satellite connection.
Anyway, the important bit is the game. Ivan is now working a great deal directly on the project, and has been picking up the slack for some of the areas I needed to address which has been a huge help. Those from the community who wanted to get involved in writing are keen to get started, but the response is so massive that we are looking to put a structure in place to ensure community written books pass through some kind of editorial process. This community content, together with copyright expired books, will form the basis of hundreds or thousands of books that can be found and read in the world. There are no set timeframes for this, so please be patient.
Ondrej, our lead programmer, continues his work on moving DayZ into a server-client architecture, turing the entire architecture of DayZ into an MMO. Jirka is working on updating some of our steamworks integration, and fixing bugs associated with the massive inventory changes we implemented over the past month.
Bebul is working on our Radio implementation, allowing players to communicate using a basic radio, similar (but more simple) to the popular ACARS radio mod for ArmA2. Players pick up radios, and they can set a frequency and talk/receive text/voice from other players. The microphone or speaker can be turned on or off to allow players to use radios as a listening device. If the player has not crafted a headset onto the radio, then the output is public (either voice or text). The results are fantastic, and Bebul is now ensuring this all works properly in the all special cases during Multiplayer play.
Our team is working their way through the animation backlog, involving new zombie animations for the new skeleton, test melee moves for our new melee system, new animations for the new animals (such as the deer), and then onto player animations for the new skeleton, custom designed to feel more like a civilian rather than the trained soldier of ArmA2.
Mostly they are working on creating the interior data required for the AI zombies to pathfind correctly inside buildings. New road decals have been created by Mario for the roads so it looks like they have a damaged look to them, to give the world more of a feel like “the Road”. One of our big special new buildings is in game, and we will surprise you with some new screenshots of this in the next devblog!
Our team of artists recruited from the community have been hard at work. The new male character mesh is being prepared, in line with the new skeleton, as well as a new template for clothing skinning. The new M4A1 has been committed with proxies that allow our new attachment system to be utilized along with the crafting system. Also being worked on are a Gas Mask, Pilot Helmet, Mauser Rifle, pen/paper, mess tin, can opener - a huge amount of items are being developed while we wait for the programming tasks to be completed heading towards our first public release.
The excitement from the team is tremendous with all these fantastic new items, allowing huge crafting possibilities.
Seven towns have been remade by SenChi, overseen by Ivan, to alter the look and feel better. Bugs are continually being fixed and we have purchased new satellite data to improve the detail of the base map (looks much better in the distance with this new data).
I realize some people are upset at my departure from the project for two months to climb Mt Everest, but hopefully from this you can see the large team Bohemia have assembled behind the development that are continuing to innovate and develop DayZ Standalone in the direction of the game we all want. This is going to take as long as it needs to, we want to release our initial alpha under the architecture it needs to avoid hacking and security issues - this is the only remaining task stopping us from releasing the alpha. But while this task is being completed, we can continue with other activities.
The next devblog will feature some screenshots to demonstrate the progress, captured by Matt, but my satellite connection and tiny laptop cant cope with downloading the current build.
So, this is the devblog I write from Everest Base Camp, at 5400 meters! Tomorrow I am off to the Khumbu Icefall for training in fixed lines and ladders, big thanks to the community for their continued patience, and everyone at Bohemia who is pushing hard towards our DayZ standalone initial release!
Our development focus is 100% on core technology, the key architecture, and not on features (yet). A major stream developing assets also runs in parallel to the core development team.
Due to the success of the development so far, and the interest in the project in general - we decided we want to do things properly. This means we have been very bold with our architectural changes. We are moving to the server-client MMO architecture model. We are making weapons and items ‘entities”, meaning we can support customization and variables assigned against items. As discussed previously, this is a massive departure from the previous engine. In many ways, once this phase is completed - one could effectively say that DayZ is running on a new version of the engine. While the graphics may look the same (for now), under the hood so much is being completely rewritten.
Let me make this very clear, our foundation release (targeted for this year), is simply the beginning. We are committed to a period of development of at least 12 months beyond that. Our aim is to make this foundation strong, and use that time to improve the mechanics not through hacks, but through sound and quality development. Our initial build will test that this base architecture works.
I want to confirm the following:
Most settings will be forced server-side, such as gameplay and graphical settings (view distance, shadow distance, etc…). The exact nature of this and specific settings is very much subject to change, but this will be a significant departure from how it is currently with the mod.
Release will be on steam, using many of steams key features such as delta patching, VAC, server browsing technology. Patches to steam can be deployed by the click of a button in our build pipeline thanks to new technology developed by Steam, that is making our process extremely easy and exciting. We are very pleased that Steam is working with us so actively to make DayZ a great game and supporting us with quality features. I met many at the team at Valve at PAX, and really want to get them playing the game and getting their feedback to help in development. I’m incredibly thankful to people like Chet Faliszek (creator of L4D) who has been very supportive and helpful to me.
In using Steam for authentication, distribution, server browsing, etc… we are able to tap into their awesome resources in terms of scalability. The only hardware we then need to manage is the central database, which we already have some experience managing thanks to the DayZ mod. This means we can work towards avoiding the usual launch problems, by relying on the experience of Steam.
The controls have been completely rethought, using inspiration and design lessons from games such as Minecraft to make the player more engaged with their environment
Animations are being cleaned up to feel more responsive. This means trimming some transitions, so that you get quicker feedback from pressing the key to action (removing he “clunkiness” or “sluggishness”)
Player clothing is being implemented including: headwear, jackets, trousers, footwear, etc..
Weapons and items are now “entities”. This means they are more object oriented in structure, allowing weapon customization, degradation - the possibilities become endless. This is a major, huge, shift in engine architecture.
The Server controls character actions, a player’s client sends its requests and the server decides if this is possible. Our lead programmer in the company, Ondrej Spanel, is working on this currently. I believe this is one of the most radical changes ever implemented in the engine since Operation Flashpoint was released, and turns DayZ from an FPS into a true MMO.
A full-time map designer has also started work on ChernarusPlus now, redeveloping the world, placing new assets and buildings, fixing bugs, and creating new areas. This is in addition to the work done by Ivan and Maxell and will continue for the remainder of DayZ development.
The UI has been completely reworked, focusing on simplicity. We have studied games that we believe are leaders in this area, such as Minecraft, and are focusing on providing functionality without fancy complexity in this regard.
We have some outstanding former community members working on the project as paid members of the team. I hope to showcase their work and interview them on here for you, in the coming weeks and months. We are actively searching for more to bring them onto the team.
We are still working towards a target for an initial foundation before the end of the year. But we will slip this date if needed, we will not compromise the project for the short-term gain of meeting this date. The reasons for any slippage would be publicly discussed, and would most likely represent a failure personally on my part to plan correctly. We will be assessing the results of our major architectural changes at the end of next week, and reporting the results to everyone when we have assessed that.
Screenshots, videos, etc… will unfortunately have to wait. As they say, loose lips sink ships.
DayZ standalone will be based on a client-server architecture (more like an MMO), not the current ArmA2 architecture.
This blog post doesn’t contain any pictures, or videos, but I think it provides far more to be excited about. When I read many comments regarding the choice of engine, it can be very frustrating. Up there with the endless debates of what is or is not alpha, is the maddeningly uninformed arguments about what does or does not constitute a “new engine”. I see people say that DayZ is based on the ArmA2 engine, or Take on Engine, or even the ArmA3 engine. I have been joking with team members on the project, that if we were to focus on making shader updates and not change anything else, everyone would be proclaiming that it was a “new engine”.
This week saw our lead programmer outline a dramatic plan to change the face of DayZ and how it will hit the world at the end of this year. Simply put, the application will move into a traditional client-server relationship which the server makes most of the decisions. This is the common architecture behind virtually every MMO currently out there, and it will be DayZ’s architecture when it releases. How is this possible? Well, thanks to an extremely fortunate set of occurrences much thinking and some development had already occurred; the crack team of programmers behind Operation Flashpoint have been thinking about these things for many years. Combined, again, with the unique string of events putting me in the position to have the idea for DayZ, and everything to come together… one could be forgiven for thinking it sounds like fate!
Currently ArmA is running simulation calculations on all clients and on the server as well. Clients have the power to make changes to their world. When the world is as complex and changing as that which DayZ creates, it has created an environment where hacking and performance issues abound. This is not an issue with ArmA, this is an issue of the designer (me) making a design that far outreaches it’s foundations. It is a testament to the Real Virtuality engine that this is even possible. So, what we are doing right now is removing these operations completely from the clients and ensuring the server runs the world. DayZ does not require the complex array of player and AI interactions that ArmA does, so these are all gone. What we are left with is a very heavily optimized solution where the server “call’s the shots" so to speak.
For those with some understanding of such endeavours the significance of these changes will already be readily apparent. For those who do not, it is simple. we’re not just locking the application and data down any more, but we’re making the server the umpire. We’re ripping out everything not required and replacing it with an optimized solution that has players (the survivors) and AI (the zombies). Our zombies don’t need to conduct flanking maneuvers, they don’t need to reload their magazines. They are simple, and our architecture reflects that. Achieving this will be tough, as we are already crunching very hard. If this heavy optimization is as successful as it would rationally seem to be on paper, then we will be limited on player numbers not by performance, but map design. To ensure we are right, we will be running an architecture test at some point, soon.
(the title for this post is a quotation attributed to Alfred Korzybski, philosopher and scientist, and for those not able to understand the subtext - it is a light jab at those professing to know much about engines, and alpha’s, what exactly they all mean)
It has been a long time since we announced the standalone project, and much has happened. In many ways, DayZ is an “accidental project”, which brings about great opportunities for it but also with some real challenges. Most of the planning has to be done as it goes, with much of the project simply reacting to things that have happened. This is not a good way to start a development project.
Much of the effort has been spent establishing the project, getting the right people setup, a new build process, art pipeline working, contracts and agreements made, legal stuff sorted - all the stuff that is necessary to enable the project to work. During this time I completed a very heavy and protracted public relations tour - I could almost make a fulltime job simply out of doing interviews.
Now for a SCRUM style update:
What has happened
We have setup all the required pipelines to best push the project forward. The standalone engine we are using is a branch of Take on Helicopters, which itself is a branch of ArmA 2 Operation Arrowhead. We chose this because of its stability, ease of development, very achievable optimization, and the fact that our programmers are the architects of the engine - the very people who built it from the ground up over ten years.
Art has been very, very busy. Chernarus has been revamped, with bug-fixing and a great deal more buildings have been made enter-able with a very high standard of work involved.
For design I have spent much time listening, reading through the posts on the forums and the suggestion thread on Reddit. Some outstanding ideas have been gleamed from there.
What is happening now
Now the fun stuff begins, all the data from Bohemia projects is up for grabs - so I am going through and collecting the best assets from the projects and mashing the data together to get it loading into DayZ standalone. With this complete, the mod itself will be ported over and integrated. This then gives us a very solid basis for further development.
Our programmers have been reviewing the way forward on the critical issues, such as bugfixing, hacking, and security. These areas are proving straightforward areas for significant development as a standalone, and as a basis in the next few weeks we will have DayZ fully integrated, with all its required data, secured, and packaged. From here we can then test and begin the more exiting things.
Art is continuing with reviewing all the buildings, making them enter-able, and tidying up the interiors to make them look nicer. Once we have this done, they will look at making the environment much more authentic to the scenario (but first we aim for the functionality!). We are now commencing work on the redevelopment of the infected people (zombie) models themselves. This will be an exciting area of work for our artist who is dedicated to this task. Initially we will be producing male and female, I would like to look at the possibility of children infected - but there are technical (required new skeleton and baked animations), possible legal (rating issues), and even moral (shooting children) issues that need to be faced.
What is blocking us
Probably the biggest stumbling block, is me (rocket). I need to stop doing interviews and focus on making the game. Really, there is very little left to say - now it is up to me and the team to deliver this. Really, in many ways, this is our project to lose. We have great support from the community, developers, and the industry as a whole - it is up to us to deliver for that promise. I think we will, but the next month is going to be really telling for our project.
Beyond that, I simply need to push forward with the integration. Once that is done, I will post some content through on the tumblr so that people can see how the development is progressing.
That’s right, this is actually happening - DayZ will be developed as a standalone game, with me as project lead, by Bohemia Interactive. This is the fairy-tale outcome for a mod that many would have said impossible four months ago.
Development and updates of the mod will continue in parallel with the development of the game, so anyone who is playing the mod now will be able to continue to do so. The project will follow the Minecraft development model; fast iterations with the community alpha available for a heavily discounted price.
I realize people will have many, many questions - but we wanted to let everyone know the announcement now. Over the coming weeks, these questions will be answered. The game will have it’s own site, www.dayzgame.com and the mod will continue at it’s present link.
"Now this is not the end. It is not even the beginning of the end, but it is, perhaps, the end of the beginning.” - Winston Churchill