SylenThunder

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.

Yeah, my 1060 is set to default at 0 fan speed until it starts to heat up, then the fans kick in. Sadly, even then the default MSI options were extremely lacking. I mean, I understand that they used the massive fans for their 1080 OC series on the 1060, and that is a little overkill. Still the fans weren't designed to really start spinning up until after it was hitting 80C. This is the custom control layout I'm using currently. Truly it never gets to 70C though even when I'm pushing it hard. Once these fans kick in, the temp drops immediately. In my most recent test, temps climbed up to 61C, and then dropped back down. I'll have to run Wolfenstein later and run a similar comparison.

Ok, your GPU fan speed should absolutely not be at only 44% when you have that much load/heat on your card. Your issue is most certainly a cooling issue. Whoever set the values for that card wanted it to fail. I'd blame the manufacturer. Thankfully you can override the fan settings with Afterburner or Precision, and set the values to something more reasonable. Might also want to ensure that you have good airflow in the case as well. Just changing airflow took my pair of 1060's from 80C to 65C.

Gratz! I finally got this myself on the PC version a few weeks ago.

Most likely it's still calculating SI changes from the collapse. You may need to sit in the area for a while in order to get it to finish, and then return to normal.

My Min-spec testing was on an Intel Core 2 Quad Q6600 @2.4GHz with 8GB DDR2 800MHz RAM, a 1TB 7200rpm platter drive, and a GTX 660Ti. I was able to achieve 60FPS with a fair bit of cutting in the graphics options and texture resolutions. My most recent test I fried the 660, and used a 770, but the overall results are pretty much the same. (Since the client relies on the CPU and RAM here, and the GPU isn't utilized due to the lack of VRAM, the end results are almost identical between the two cards.) My primary PC until just about a year ago was an i7-3930k. You can see some comparison tests I ran with it here.

That's why I included the file. You won't need to generate it. Just download the map and extract the folder to your Generated Worlds. You can then select it from the pre-made maps when starting a save.

Please read the Pinned thread on How to Report an Issue before posting your issue. If I could guess your problem based on that lack of information I would be a multi-billionaire from winning the lottery all the time. (Because the odds of a win are about the same.)

We haven't been using the dedi to make maps since a18 because you can do it WAY faster on the client. Whatever you read about Gamesparks on dedi's was wrong. It does the same thing it does on the client. To deal with the issue, (and so you don't have to wait two hours to make a map because of no GPU usage in the dedi), make the map on the client and copy it to the dedi. This has been the thing to do since they moved map generation from the CPU to the GPU. They are well aware of the issue, and it is being worked on.

Nice big city in this one. And if you want to play it, here's the world data to drop in your Generated Worlds folder. https://drive.google.com/file/d/1zT9atUGe73tYta-d66dNwmH20MKmRrnX/view?usp=sharing

You just have to be early enough to get a voucher. I stopped in this morning because it was the day they receive product, but did not arrive early enough to get a voucher.

Not just making the video, but making the product for the video. That was simply inspired. Loved the ending.