In this update3
Full notes
Full Project Zomboid update
Read the full published notes in a cleaner layout. The original post stays linked below.
What changed
- Gameplay
- Maps
- Compatibility
- Performance
It’s been a really big week for us, as we merged the second-to-last element of Build 42 into the main codebase across the rest of the team – which is the long awaited tech upgrade which brings a whole host of improvements to the engine.
It’s currently being tested and the feedback has been super positive so far. This said, it’s also brought over lots of small bugs, visual glitches, and issues with new depth map clipping items incorrectly. Nothing over-dramatic, but enough stuff to keep testers and coders alike fully occupied.
This is where a lot of our brains have been at recently, so we thought we’d give you an update on the engine as it now stands while testers run around kicking its tires – alongside some videos they have made along the way.
Likewise, we also have some examples of some of its new capabilities that we will be able to explore in future – perhaps during the Unstable beta, perhaps beyond.
So, a run-down of what this tech upgrade brings into the game:
OPTIMIZATION
We’ve made huge optimizations to the rendering of the map that should have a huge impact for most lower-midrange and upwards systems. We are now easily able to get a solid framerate even on 4K, or on furthest zoom. The difference in performance is honestly surprising, and extremely satisfying.
For full disclosure, however, we’ve discovered that a few of the absolutely lowest end systems capable of running our game are still adversely affected. This is because the solution for such large FPS optimization comes at the expense of GPU memory usage for the caching textures used. Cards with extremely low dedicated GPU memory may run into problems.
We’re investigating and trying to optimize this further to make sure as many systems as possible can benefit, and worst case scenario these optimizations will be disabled on systems where they would do more harm than good.
However, it’s still entirely possible that we’ll be able to resolve this completely and provide a large boost to even the most potato systems. More likely, we’ll provide some kind of automatic detection to provide as large a portion of the optimizations as possible for a GPU’s available memory. This will be our next task post visual-bug clear out.
Generally we estimate that a huge majority of our playerbase will benefit greatly from the optimizations. Since most of the optimization frustrations we hear come from players who feel their machine should be able to run PZ at a solid framerate, we feel this work will ease the vast majority of performance sadness we see in the community.
VIEW CONE
Another improvement born out of necessity is an improved and smoother viewing cone. Due to the optimizations, it was no longer feasible to alter the lighting of tiles frequently enough to allow for the smooth light changes required for our tile based viewing cone.
As such we needed to implement a completely separate and newly-coded viewing cone that didn’t rely on tile lighting – which truth be told we were never a huge fan of anyway.
Now we have a much more accurate, smooth and fancy viewing cone – and now we have extra hands on it internally feedback is being collated so that we can provide plenty of requested options to allow you to tweak it this way and that. (Making it more or less visible probably being the primary one.)
LIGHT PROPAGATION
The new lighting system is
Source
Changelog.gg summarizes and formats this update. How we read updates.
