7 Days To Die Dev Tracker

I have a bug ticket for it. Some of the fat zombies do it to. I don't know why anyone would want such a feature, so yes, it is a bug, probably from some of the colliders changing.

Load order, current VRAM use and then where the OS decided to put textures would make it somewhat random what is in VRAM vs system RAM.

----

Hopefully the disappearing backpack bug is now fixed. That was not easy to track down.

There was about a 5% chance, depending on when random chunk saves happen, that a newly dropped item would be lost when you teleported away, because its chunk might not save.

A19 has a variety of rendering changes. Many textures got larger and more objects with textures were added, so there are probably more textures running out of system RAM for you. The next release will have 100+ textures that Justin shrunk down, so it might be better.

Console messages are not as bad as you make them sound. For years the game has logged plenty of console messages as you play. It takes dozens/hundreds in a short time period to start lagging unless you have some weird issue with it writing to the file.

Now the code that is logging the message might be running slow, but that is not from the message itself.

If they don't take any damage then it is probably a bug, but I would not want them taking much damage even if we fix it, because people would make low resources corridors full of campfires to kill zombies. Yes we should fix it, but it would be way down the list of things we need to worry about.

b169 did not load block entities up front, so less VRAM use, but added lot of loading lag, so that change was reverted in b173. One of our artists lowered texture sizes on many textures last Friday, so texture memory use will be somewhat less in the next release.
It is probably a memory issue on that GPU. How much VRAM does it have? Wiki says 2 GB or 4 GB. If yours is 2 GB, then that not much and you would need to put all texture quality settings to the lower choices.

I checked the randomness of loot containers a few weeks ago. Was working fine. 75% of 1 means you have a 75% chance to get 1 and a 25% chance to get 0. That also applies to any partial amount. 5 items on 50% loot means 2.5 items, so a 50% chance to get 2 or 3.

There was this change: "Change "Boss Volume" to "Quest Exclude" on sleeper volumes", which repurposed the boss volume flag we never used to allow designers to exclude volumes from a quests requirements. Like a garage outside a house could have sleepers in it but not be required to fulfill a clear quest.

If only it were that simple. Water runs fast for me normally. I've been around and under water during testing a lot in the last several months. It has never acted like it did during the stream.

Bugs that rarely happen on your own computer are often very hard fix.

Like I found a way that backpacks can be lost and can reproduce it fairly well now, but I needed to add code to move the backpack constantly to make it happen regularly. The reason the bug was so hard to find is it requires the backpack to move between chunks as the chunks unload and chunks save. That stuff is complicated with 2 different threads and after debugging all day, I still am not sure what is going on other than the chunk the backpack is in does not always save. Hopefully get that one fixed Monday.

Due to changes to sleeper volumes it is recommended to start over.

If you do not, you may experience a POI flagged as clear before you cleared all volumes.

b170-b173 Changelog:

Added

Localization updated for destroyed concrete material


Setup xml, localization, and icons for Gas Pump Remake


Updated localization for Wild West Coffin helper


Setup xml and localization for Bleachers Set


Destroyed concrete material


"gfx graph tex mem" and "gfx graph tex stream" console commands


"gfx st reduction" console command


"gf