SylenThunder

That CPU is your limiting factor. It doesn't even meet the minimum spec speed. We are running X5675's at 3.07Ghz, and are starting to see the stain on the CPU. You won't see your total CPU max out because the game sits on one core primarily. As it sits now with our setup, we're seeing some significant FPS drops on horde nights and when a new player is downloading the map. Otherwise, it seems to run just fine. Currently looking at building a new system with a R9 5950X and a X570S motherboard.

You really do need to update Windows though. Even in our enterprise environment we don't allow PC's with older than 1906 to connect to some things. The standard is 20H2, and the current latest is 21H2. Your machine is pretty insecure and lacks optimization at 1607. Even 1803 is pretty pathetic, and you aren't there yet. That may not have been the issue now, but it will be an issue in the near future.

AFAIK it isn't a bug, it's intended.

EAC is an Epic service. Also as Start69 stated, EoS was added in a20 to support cross-platform play. Something Steam could have offered for years, but won't.

You just make a copy of the files. Copy serverconfig.xml to MyServerName.xml. Do the same with the .bat file. Then edit the .bat to use the new server config file.

Also, never use the default files. Set up a separate config and batch file for your server so that when there is an update, you don't lose your settings.

Any time Windows does a semi-major update, you absolutely need to re-install the GPU drivers afterwards. Aside from that, I usually check every 4-6 months.

It's most likely your connection. GeForce NOW requires at least 15Mbps for 720p at 60 FPS, and 25Mbps for 1080p at 60 FPS Your 50mbit/s internet connection is only amounting to 6.25Mbps. Which is less than half of the requirement for the minimum. I've never used GeForce Now, but those are the numbers.

Just for anyone else visiting this running into the same issue. This type of thing is usually from one of two causes. The first being that it is blocked by security software because you did not exclude the client like you are supposed to. The second is just bad DNS records. Windows isn't great at managing the DNS stack, and just sitting on the server selection screen for five minutes can be enough to overload it. Often when you face an issue like this, just flush the DNS stack by running "ipconfig /flushdns" from the command prompt or reboot the system.

Ok, a few things. First is that Unity doesn't play well with some modifications. Under/Over-volting is one of these. Doesn't matter if you can run Futuremark and Prime95 at the same time without an issue, Unity will have a problem. Errors like this are often what you see. I have personally run into this playing with settings on my 6800 XT. Second, you never once mentioned installing GPU drivers. After any Windows install/Update/Upgrade you absolutely must perform a clean installation. Those errors are a common effect when you are running on the "Microsoft Certified" drivers that get installed with these updates. You should absolutely perform a clean installation of GPU drivers downloaded from Nvidia. Can opt out of the GeForce bloatware while you're at it as well. Third is that PSU. No offense to your purchase, but Corsair has had the highest rate of failure of any of the PSU's I have worked with over the past five years. I literally just replaced one of those a few months ago because it had failed for the third time and nearly baked my motherboard in the process. (It did roast one of the hard drives in my RAID configuration.) It could simply be that it is breaking under the strain. This title in an unoptimized game in Alpha development. Even without that, it is more demanding on your core components than nearly any other program is. The Corsair before the last one was in a similar state. It would work just fine for benchmarking, overclocking, and could run just about anything. Run 7 Days and the system would crash. After intensive testing with benchmark and burn-in software not resulting in failure, but 7 Days crashing the system contently, I finally pulled it out and ran some tests on it with a meter. The 12v rail to the motherboard was failing under load. This is actually a pretty common theme around here.

First thing I always do it gather a good supply of the basics. (wood, stone, fibers, feathers, chrysanthemum) Then I hunt houses for food and a pot.

There is a Pinned thread that tells you how to post. The title of the thread indicates that you should read it before starting a thread.

This is the section for PS4 and XBox console versions of the game. You want the PC Support Section. Don't forget to read the FAQ and the Very Important Pinned thread before you post there.

It is planned for the next console release. Not possible with the current release.

There isn't going to be an update. The next iteration of this game will be a whole new release. KB/M support is limited on consoles, but in the end, the decision to support it will lie on the new publisher.

Well to be fair, the next console version is probably a good 2-3 years away. Joel has said that he wants to make it backwards-compatible with the older systems. Like meganoth though, I'm not holding my breath on that. Unless the gold standard for it is 30FPS. I think it might be able to hit that after a lot of optimizations in the code.

It's literally the same as everything else. If you define your UserDataFolder in your server config file, that is where the Mod folder will be. (Honestly if you aren't defining this for a dedi, you're doing it wrong.) If you don't define your UserDataFolder in your server config file, then it will be in the default location. <User>/.local/share/7DaysToDie

Because you kept trying to join a week ago when you had a brand new account. New accounts aren't allowed in the Discord as an effort to combat bots. Each time you tried it kicked you, until you got too many infraction points and were banned. I have removed that ban, and you should be able to join now.

1. Check the Pinned thread about XBox MD5 issues. 2. This version is already dead. Thank you TellTale. 3. Thanks to the way TellTale released it, and thanks to them going bankrupt, this version is not capable of being updated.

I would also recommend actually reading the pinned banners, announcements, and active forum threads in the Console section of the forum. It's not like there hasn't already been an answer to your incoherent ramblings.

The LiteNetLib messages are an effect. It's not an error. It is merely reporting a failure in the data connection, which is external to the client. The cause is the data pathing being lost.

This sounds like CG-NAT, which is extremely bad for hosting.

That one definitely looks nice.

There are a number of causes for this. Most commonly, it's simply a result of a limitation in hardware or network connection between the host and the player. There were also some POI's in a20 that had issues with the spawn zones, but I think most of those have been fixed by this point. If you provide more information about the issue, we can likely help you at lease alleviate it some. Would need host/client logs, and details on which POI's you're having the issues with. Instructions are Pinned, and it even tells you to read it before posting.

Most commonly it's a NAT issue with your modem/router. Basically, the ports used by the console are directed incorrectly or blocked. If you Google "Xbox NAT issue", you should get a pretty large number of results with how to test and work around it.