faatal

If you don't play multiplayer, then you would not see the message. Being that it is a warning, you would never see the message unless you look at the console or log for them. Unity used to not care about you setting velocities on a kinematic RigidBody and then in 2022 they added a warning to tell you the velocity does not do anything because kinematic objects are not moved by velocities. Warnings don't break the game. I log plenty or these every day for all manner of testing. They are the same as a normal log message except they say "warning". Now, if there is a lot of spam of any type of message then it may cause a small performance hit, but it should not crash. I found two places in vehicle code where it happens and fixed them. One seems to be an actual bug where the vehicle would not have its velocity transferred when the server resumes ownership of the vehicle.

Your controller turning off when using keyboard and mouse is not under control of a game. That is what the Xbox OS does. Allan discovered that if you removed the controller batteries and plug it into the console, the controller will stay on. Smell would be nice to have again, but there is a giant pile of things that would be nice to do. The pile is always bigger than the amount of time we have, so we have to prioritize what we work on.

Sorry, but the data seems to be gone, so there is no getting it back. It stinks, but games have bugs. This was a rare bug that required just the right timing between multiple threads for it to happen. Even when we knew exactly what we were looking for, we only saw it happen once between several different people testing just crates loading and unloading for hours.

Curse those multiverses!

If it says b334, then that is the fix.

That is why we are switching to the Omega versioning system. It involves time travel, where you go back in time to fix bugs before they can be born. "They would reshape the Future by changing the Past. The plan required something that felt no pity. No pain. No fear. Something unstoppable. They created the Terminator." The Buginator will be unleashed soon, but since the past will change, we will no longer remember this conversation..........

The game has to allocate the world storage estimate up front due to how the console file systems work. The size is based on the Chunk Persistence setting. Lower the value to use less save space. You can also archive worlds which converts it to the basic files without the padding, so it is much smaller. It is very fast as these consoles have SSD storage.

That does not sound like the same issue with empty storage chests as the only thing changes with that bug is the loss of what was inside the chests. That sounds like chunks being reset. Chunks reset based on the Chunk Persistence setting unless there is a bed roll, land claim or players being in the area more often than the timer. Did you have any bedrolls or land claims near them? Did you place bed rolls in another area (there can be only one active)? What is persistence set to? Were both of you away from the area for an extended amount of time?

Should be fixed.

We have spent many hours looking at this and have yet to determine why it happens on Xbox. PC/Mac/Linux and PS5 seem fine. Consoles have profanity filter code as required by MS/Sony that adjusts the text. XBox does it very differently from PS5. I think it is a timing issue with tile read/write vs profanity threads, but have yet to see it fail for me. If the name is blank, then no filtering, so if the bug does not happen in that case, then we know it is the filter, else it is something with the read/write code.

Yes, we have cross play working in testing. Due to the additional time required for testing and fixes and getting the required permissions from MS and Sony, it was delayed until after the 1.0 release.

I have heard of no plans for new weapons or ammo or books, but it is possible. No plans for fishing, but someday I could see the game or a sequel having some water based creatures. Paid DLC has been talked about, but nothing specific that I know of yet.

Correct. The current roadmap for biome progression, bandits and story are normal free updates to the game. I saw someone on Steam shouting that it was all paid DLC. Clearly they could not read. Any feature we release should be seen in an experimental beforehand. I believe I said before that I was not doing it for 1.0. I have had way too many other things to deal with. Possibly for a 1.5 or 2.0 version.

b333 was experimental and since it tested fine, was switched to stable. As far as I recall, every stable update we have done in many years is preceded by experimental versions, which once we are done and the final one tests fine, it then turns into the new stable. Testing experimentals tells us that those exact builds, for all 3 platforms, each with client/dedi versions, tested well for a variety of people.

The brightness change had nothing to do with streamers. As you said, streamers could already turn up the brightness. It was changed because it was thought to be a more practical play experience. I actually like it dark and have thought we could have day and night brightness settings, but we shall see where the team opinions lands after more testing and feedback.

There was a change in the throw code to a line that compares if the item value was the same reference, which was changed to Equals. That compares all the values of an item, which did not match after lit, so it would cancel the throw as soon as you clicked. I changed it to a type compare to fix. That is old code and it may not even be needed anymore, but removing could cause some other bug. Fixing bugs can be dangerous as you often make new ones, which happened several times this week.

All these sounds are played as Unity Audio Sources. They have a curve for falloff with distance. Footsteps were just adjusted recently. This is footsteps, which has 0 volume at 20m.

There is no concept of a floor. It is just a lot of blocks. You have to scan blocks/colliders to know what is in the way. Then you have to figure out what things you hit and what they should do to the sound. You have to do that on every sound call, which is a lot.

Audio occlusion is not simple. We have old code from before my time at TFP that looks like they tried it and it was disabled. Maybe someday if we run out of other stuff to add, but it would probably be a performance hit.

The discount goes through Microsoft's and Sony's stores. I can't see them wanting to give discounts for anything bought from a competitor or having any reasonable way to know you bought it from someone else.

Spawning yes, the loot bag no, which was from them extending from the dire wolf and getting their health too. That is fixed.

I can't, because I don't know, because there are many decisions still to be made.

It was fixed in my testing. Each forge had a burning light and a crafting light. I merged them into one light and with a reduced radius, which improved performance of each forge. I also reduced smoke particles by 25%, which also improved performance. This rendered with less than half the FPS drop on my 3070 TI. You can also try lowering the graphics Particles setting which will scale down the amount of smoke particles.

We test changes, but with limited time, there is limited testing. This is why we tell people it is experimental and to expect a variety of issues. I am surprised the save games actually made it this far being still playable. It may seem like a lot of players playing experimentals, but actually a large majority of players do not play experimentals.

1 No plans, but it could change. 2 They could use them, but not happening for 1.0.