SylenThunder

According to @faatal from earlier in the a18 or a19 developer diary, bedroll only blocks POI and biome spawns, and LCB only blocks POI spawns. Also I like Vedui, but some of his videos are a bit misleading and tend more towards theatrics. (Which honestly isn't any different from 95% of the other video game streamers.)

I checked it on mine thinking this might be the case, and it's reporting it just fine. I also have an Asus, though it's a ROG Strix X570-E.

Some clarification on this. You want the 6GB variant of the 1060. The 3GB variant is trash that should never have been released.

Possible, yes. Enjoyable, not as much. You're going to struggle to get 30FPS. Especially if the rest of your hardware is as old as that GPU. The minimum required hardware states 2GB vram. If you go back to some older versions before a16, you can have a little bit better experience.

Just to note... 20 years ago, this was the case. In current times, not so much. Critical security and performance issues are put into BIOS patches, and they are updated now almost as commonly as regular drivers as a result. Here's a list of some of the changes that have occurred since the build you're using. Improved system performance and stability Improved DRAM compatibility Update AMD AM4 AGESA Support Smart Access Memory for Ryzen 3000 Series Processors Fix the L3 cache performance in AIDA64 Fix USB connectivity issue So basically by not updating, you are missing several versions of patches to code on the motherboard that affect performance, stability, and efficiency. And it's not like it's even a risky measure anymore with being able to update it in Windows via software provided from the manufacturer, and even via using a built-in tool in the BIOS that will go as far as locating the latest build, downloading it, and installing it for you. Not to mention having the BIOS Flashback feature that will allow you to quite easily recover if anything does manage to go pear shaped.

Okay, a couple of things. 1. EAC is not blocked on Linux. The only issues in that regard I could think of is if you're using Wine. Since 7 Days has a native Linux client, that shouldn't be an issue. 2. If you have EAC turned off, you will be unable to join any server that has it enabled. More information on exactly what you've got going on there would be useful in troubleshooting.

I work nights, so I'm basically on Australia hours. Your RAM timing should be 15-15-15-35 for your 2400MHz RAM. However because it was never actually set in BIOS, it's running on Motherboard manufacturer default "safe" timings. As a result, it is sitting at 2166MHz and pulling down the performance of your CPU. This misrepresentation is also known to cause issues that will appear very similar to RAM sticks going bad. Also note that since you aren't using a 3rd party AV solution, Defender is enabled. You must exclude the client from that. It's almost worse than Norton for killing games. Almost. Your system BIOS is obsolete. It's like it's the default version from the original board printing. Get the latest here, or use Armoury Crate to update. You have version 1004, and should be on 2006. While you're at it, ensure that you have the latest drivers in Armoury Crate as well. The last Windows update replaced core chipset and LAN/Wifi drivers with extremely obsolete versions. Your GPU driver is outdated as well. Get the latest version from here. Choose to go without GeForce Experience, and choose Custom Install so you can tick the box to perform a clean installation. Other than that, I don't see anything that really stands out. Your most crippling problems are the BIOS that expired two years ago, and the incorrect RAM configuration.

Your RAM is not configured properly. That alone is going to cripple your system's performance. I'll look into more of the report once I've had breakfast and some coffee.

Looks like a GPU driver failure. Make certain you have installed the most recent driver from the manufacturer. (AMD in your case) Especially if Windows had a big update recently. (which it did) Also, don't forget to exclude the client from security software.

A Speccy report taken at the time of the issue may help out as well. Instructions on how to link a published report are in the Pinned topic on how to report an issue.

Follow the information in the Pinned Support FAQ thread on excluding the mod, and the game client, from security software.

It's been an issue since Distant POI was introduced in a16.0. It's also been really hard to get people having the issue to submit proper bug reports containing useful information to try to replicate it. I've only been able to get the issue to occur by either using obsolete hardware (and even then I had to over-stress it), or by using mods or other things that would invalidate most of the testing.

I responded to this on Steam already.

You can't fully shut it off. Exclude the client.

Ok, you didn't actually state the command. Here is what is should look like. Assuming the server folder is D:\7Days Server steamcmd +login anonymous +force_install_dir "D:\7Days Server" +app_update 294420 -validate +quit

When you took all of these steps, did you also exclude the client from Windows Defender?

1. What is the command you are using with SteamCMD? 2. Why did you rename the server executable? 3. Pro-Tip, don't use the default config or batch for your server. Make new copies with custom names. Then updates don't wipe data.

Yeah 20 FPS for an active server is low. Ideally that should be 35-40. (Higher than 40 is just wasting CPU for no reason, and below 30 indicates a bottleneck issue.)

Mostly the things I listed already. Security software, RAM issue, HDD issue, permissions issue. Stuff like that. Could just be some other software getting in the way too. Like how Citrix Workstation will randomly kill the client because of how it handles GPU data. Or how nearly every experimental has an issue with the overlay from MSI Afterburner. These things are harder to track down, but usually can be discovered eventually.

Pretty sure I provided an alternative in that case. justpaste.it will host larger files. It's all in the Pinned thread. First issue. You have so many mods that could be conflicting, I'm not even going to try sorting them out. One set in particular looks to be an overhaul mod, and it is typically not safe to merge those with other mods that make core changes. Second issue. That CPU really can't manage that many mods with that number of players. Even with SSD's in RAID it's not going to keep up. The hardware platform simply can't support the amount of data that needs to be processed. Third issue. Double-stacking server managers will typically cause problems. Not only with overlapping commands, but also with duplicating processes. And again, this is going to put even more strain on the already struggling CPU. Fourth issue. Towards the end of the log you have a critical network failure. Data is not being sent to the client, or cannot get out of the client. Any shutdown command not being sent directly via the client is not going to be heard. Causes for the end failure that leads to the issue are numerous. More data would be required.

Well after you get in trouble for using your software to steal data from the NSA, it's hard to come back from it. (Which may not have actually happened the way they initially thought. That's a funny one.) In any case, disabling security software fully is typically not possible without completely un-installing it from the system. This is by design due to too many of the viruses we used to write simply disabling the software so they didn't get detected. Also in regards to the several server restarts. There was a known issue where logging out of a server, and logging into a server without exiting the client could cause a memory leak. It was advised to fully exit the client when switching servers, or re-logging in a disconnect situation. I know work was being done to fix this issue, but cannot recall off the top of my head right now if it was actually resolved in one of the recent updates. Something I do find interesting in your logs is the inconsistent amount of RAM allocated. One log is averaging 10GB, and another is only averaging 5-6GB. The tail end of the logs lead me to believe that it is still an access violation issue though.

I remember when they added UMA and tried to have the random outfits in a14. It lasted all of about 5 minutes. Any more than 10 zombies spawning brought even my high-end system to a crippling halt. That wasn't a lot of fun. The system was quickly removed, but UMA was still in, and is one of the reasons we don't have a ton of wild zeds roaming around in the client atm. I am looking forward to the new systems coming in a20 and beyond though.

My current record for repair is a wee bit over 850,000 infections. If they didn't absolutely have to have bank data that couldn't be pulled out by just copying the files, I wouldn't have even attempted it. Took a couple of days, but I did manage to purge all the infections. Main source of infection, husband visiting porn sites on a separate profile in the PC. I left him a little note in his user profile.

This appears to be an access violation. Which can be caused by a number of things. Ensure that the client is properly excluded from security software. Ensure that you don't have any RAM issues by running memtest. Ensure that your hard disk is error free. Ensure that you do indeed have the latest drivers. (Windows updates will install outdated/broken drivers for LAN, Chipset, and GPU on a regular basis. Always ensure that you refresh all critical system drivers after a Windows update.) Ensure that the Pagefile is set to "System Managed". Doesn't matter how much RAM you have, manually locking this will cause issues. It also will not save your SSD. That is a myth.

Ok, ran 7 Days, and while screenshotting I noticed something. OP talks about "Ultra" settings. Here's the deal though. This game is still in development, and putting every setting on Ultra, is kind of a dumb thing to do. In particular, reflections and Shadows have not had a ton of optimization. (In the case of reflections, I would argue that it most likely hasn't had any notable optimization ever at all.) So with that in mind, I'm including my in-game settings. I know I'm a bit limited by the 1060 in terms of graphics power, but this configuration allows me to get above 100FPS regularly so I can lock it into 60, and ensure that the FPS numbers don't float around much at all. In this test I started out in our underground base in the wilderness. Came up top and roamed around the forest/mountain by our base. Then ran a couple clicks to the nearest road, planted a gyro, and flew a good kilometer over the forest to the nearest town. Did some flying about, then dropped into the center and picked up the gyro. Then I walked around town on foot for a bit, encountered some zombies, and then stopped to take the two above screenshots. I was in-game for a total of about 20 minutes, which is more than plenty enough to get the card nice and warmed up. As I am writing this just about two minutes later, the card is already down to 38C. (Ambient room temp is 75.0F, or 23.89C) EDIT: The most recent Wolfenstein title I have is The New Order, so that wouldn't really be a valid comparison. Will have to see if I can borrow it from someone.