SylenThunder

The data I referenced, is based on the old game version which has lower hardware specs than the current or future versions. Unity is not less complicated than UE4. UE4 has nowhere near the capability of Unity when it comes to Voxels. Also note that A:SE and RocketLeague are not Voxel games. Completely different. Those games only care about the GPU performance. Also note that nearly every game ported to the switch has to have a major graphic overhaul to be able to function on the switch. Texture resolutions are cut in half, textures are cut out, and overall content is reduced.

This occurs when you are on Vulkan. I don't believe DX10 is supported any longer. You should try OpenGL, but if your card is that old, you're going to have some issues no matter what you do.

This is correct. The other thing I have seen moders do is simply re-skin existing NPC's. Usually it's a trader, but I have seen it done for the survivor/bandit code as well. Also note that the modding platform is not final yet for this title, and Workshop support is also planned.

After reaching a certain limit, a rail (output node) on the power supply was not able to provide the designated amount of power. In my particular case it was on an output that powered the SSD the OS was installed on. In your case, it could be something similar but on the link for your GPU power. Especially if it is doing it after a specific amount of time under load. By changing the renderer to OpenGL or Vulkan, you are reducing how much work your GPU is doing, and thus reducing the power draw on that rail.

Sounds like you probably have old data left over from a previous version. Especially if you are using such simple RWG seeds. I would follow the instructions in the banner to wipe all game data. Backup before hand so you can restore specific items. However if you have any saves based off of these maps, they are likely broken already and should be deleted anyway.

Could be a power rail limitation as well. We still haven't heard if they have fixed the drivers though. 7 Days uses the core components of your system more than any other game. It is very CPU-heavy and requires heavy use of RAM and your storage. Other games only rely on the GPU for the most part, and one single CPU core. As a result, 7 Days tends to find weak points in hardware and drivers more than just about any other program. I spent a few weeks troubleshooting an issue once where 7 Days would crash the system and not even Prime 95 plus Furmark could crash it. Turned out to be a bad rail on my nearly brand new PSU.

By posting in the correct section, and reading the Pinned instructions on how to report an issue and following them. I'll move your thread to the correct section, but you'll need to take care of the rest.

Yep, as I expected. You have a bunch of shader errors. Usually this is caused by an invalid driver, or corrupt DirectX install. Follow my advice at the bottom of my last post.

Usually this is because you have either chosen the incorrect renderer for your hardware, or do not have proper GPU drivers installed. However having it occur mid-playthrough is exceptionally odd. Usually though, it would be a GPU timeout, which also indicates a driver issue. Cannot really say for certain without a log though. Personally, I would start with ensuring all Windows updates are installed. Then using DDU to scrub all driver files and perform a clean installation of the latest driver package for your GPU.

IMHO, if anything was done, it should be a toggle. The default would be as it is now, but have an option to toggle off the repeat.

Again, Need useful information. How did you set up your server? Where is it hosted? What is your network configuration? What port forwarding did you use? Where is the link to your server and client log files that you uploaded to Pastebin?

Cannot help you if you don't provide any useful information. Do the needful.

That is abnormally low RAM usage. This seems a bit high for Vanilla, but depending on the world data and player activity it is not improbable. The Min spec is 8GB RAM. Recommended in 12-16GB. These have existed for years. If they never happened before, you either were not running a modern client version, or it was configured incorrectly. As noted in the thread you referenced, they can be ignored completely. This is simply filtering not being applied to the log output. In any case, you failed to provide any really useful details on your setup. No logs are presented either. I would imagine the issue is more with your configuration than anything else. Again, your previous "experience" does not match with the way the server has been running for almost a decade. So either you were using a mod that applied additional log filtering, or you had a really strange setup. At one point you needed to allocate almost 1GB RAM for each additional player joining the server. It is much better now than it has ever been, but I have serious doubt that you actually had those numbers without using 3rd-Party tools or modifying client behavior. And I'll be very clear on this. The dedicated server does run very stable. When it has the proper resources available to it, and you aren't exceeding known stable values. Post your setup and logs. If you have logs from your previous configuration, that would be interesting to see and compare with. Keep in mind that I am not some Fanboi towing the company line and spouting nonsense. I have been supporting and testing on a large variety of hardware configurations for over a decade just for this title alone. I have over 35 years of industry experience, and currently manage over 25 servers for a variety of different games. I say this because what usually happens next is you posting that I am full of crap, and don't know any better. That you for sure are having this abnormally golden experience previously. I will take most of your previous statements with a grain of salt because there is no data provided to any of it. Do the needful.

Officially so far. I am a bit surprised that the Official A22 Dev Diary thread hasn't been started yet. They usually come out shortly after the first build is released. Whatever their reasons, I do have hope that we will see the official thread soon. They have been discussing some of the content and changes already in the a21 diary, and on Twitter/X.

Yes, I have been noticing a good number of network issues today with both Steam and Epic services. Flushing DNS is usually a pretty good fix as you might pick up a new path to the servers.

Yeah, performance-per-dollar AMD is really winning out though. For $3-400 less than Nvidia you can get the same spec performance. I was just helping someone that was looking at a 3060 TI, and managed to get a 6800XT for only about $50 more. It runs almost equivalent to a 4070 without any overclocks.

With the focus on making the next console version cross-platform play compatible, I get the feeling that this won't happen. It will basically need to match the PC versions 1:1. I do hope that it does happen though, as this was basically the only way I played on my PS4.

It seems like they have this issue about every other generation. 5000-series GPU, major issues at launch with game compatibility and driver. 6000-series, no problems. now 7800XT and 7900XT's are almost unplayable on a large number of games.

That isn't an error. Just a warning that can be ignored. It would not cause a crash. I suspect that the data in your base chunk is corrupted, which would cause the crash. Could be due to a number of things like missing block data due to mods not loading properly, or even as simple as having put down too many frame shapes. The fix would be to reset the affected area so you can enter it again.

The dev's Twitter/X page, or the announcements section here. That is where you will see it posted first.

Ok, I know there have been some issues with textures, shadows, and other similar things on those 7800/7900's, but you shoudn't be having that kind of an issue. Step 1 : Exclude your game client and save folder from security software. If you say "I don't have any", you have Defender and it must be excluded. I cover this in detail in the Support FAQ thread that is Pinned. Step 2 : After you have fully excluded the client, now validate the files three times. Once almost never finds everything, and twice isn't much better. Step 3 : Reboot your computer. I would recommend doing a full hard shutdown and power drain if you haven't in a while. Step 4 : Back up your save files to another location. (File locations are in the Pinned FAQ thread.) Step 5 : Nuke everything. The Blue banner at the top of this page has instructions. Want to be certain that everything is fully reset. Step 6 : Try these video settings. I'm on an R9 3900X with 32GB RAM and a 6800XT. I average well over 100FPS at 1440p all the time. Step 7 : Try again on a fully fresh map/save. This will rule out any data corruption from previous worlds. If that works, then you can try restoring previous save data and see how it runs.

IIRC there are three POI's with a broken dew collector. Looting that has something like a 5% chance to have a filter in it when you loot it. Destroying it doesn't do you any good.

It is apparent that you don't pay any attention to active threads in this forum, or the main dev Twitter account.

TFP has no control over the current version in the store. They did not publish it, TellTale did. Only Sony and MS control it currently and will not allow TFP control under their rules. If you cared to do a bit of research in this topic you obviously care so much about, you might have discovered that.