Jugginator

Moving to WIP, things related to this are up for discussion (max zombie counts, getting zombies to spawn for quests if the limit has been reached, etc.); large topic though, performance reasons and other factors need to be considered. If you hit a POI where there's an error in how it's setup that's a difference case though.

This should be fixed for A21.

Confirmed, there were a number of changes to quests which made this odder. Ticketing.

Confirmed, there were a number of changes to quests which made this odder. Ticketing.

Running some tests to get the bigger scope but confirmed ty

Here' s something simple to check: Verify your ram is actually running at 3600. Open task manager and look under Performance: You probably can turn on Resizable BAR in your BIOS (google it for your motherboard, as most of them put things in different spots/call them different things), XMP if your ram is not running at 3600 is likely not stable. If it is running at 3600, list what the XMP profile it set it to (like 16/18/18/36/54), the timings may not fully be stable.

Actually, @Chris O, you can do a decent test and go into services.msc (the services app), sort the tab by Startup Type then look through and start disabling the ones that aren't Windows processes. You'll also want to disable any third-party antivirus programs besides Windows Defender -- if you don't crash, you'll know it was one of the one(s) you prevented from starting up. To stop them: right click, go to Properties, click Stop at the middle-bottom area, then change the startup type to either Manual or Disabled (Disabled to be sure) and reboot the pc and try again.

That was pretty impressive for an AI bot, only a few very minor grammatical errors. Crazy.

I don't even want to know what ram cache is. But, @Chris O, that error is pretty specific although there could be one of dozens of causes: something is blocking access to core files (game or system, system being modules required by the program) or general corruption (loaded modules getting corrupted in ram). So, could be bad ram, but I'm more leaning towards some software/antivirus/drivers/OS corruption.

Glad ya got it resolved, would you be fine with sharing what was wrong/what fixed it?

Sounds like an antivirus getting in the way, or just really spotty internet. Check the antivirus first

So, to fix this, go into your main game directory, run the 7Dlauncher, click Tools (from here, if you would be so kind, I would like a copy of your registry for debugging. If so, click Open Game Settings, right click the 7 days to die folder (left-hand side), click Export, then upload it somehow to me in a private message, if not, no biggies!), click Open Settings, find the 7 days to die folder on the left-hand side, then delete that folder. You will need to make a new profile and change your settings and such again, but that should get you going.

Those streaks show a bad mod conflict between the server and client actually, if you're playing on a sever. If not, you've got some UI mods causing issues.

A log file may help, but it sounds like the chunk that he was in got corrupted. 6gb of ram for the server is below the minimal spec, too. You'll want at least 8gb especially for an 8k map. You may want to try teleporting him somewhere safe, like at 0 0 while he's logged in (you can do it as soon as he establishes connection, even if in the loading screen still).

Hello! Did this resolve it?

I'd say this is intended. The crosshair represents the spread's deviation at the effective range, not based on what you're currently aiming at. I attached some screenshots showing this. Up close and within an effective range, the shot spreads haven't hit the range at which they start to heavily deviate; this is further escalated and shown at a max range, which the shots start tight and "spread" out to fit the crosshair's representation perfectly. The only thing that could change is to have the crosshairs dynamically changed based on what you're aiming at, which as far as I know isn't feasible and hasn't been done in any games. If the shotguns start the trajectory at the max deviated spread, shots beyond up-close in your face would never hit anything and the crosshairs would be inaccurate beyond this range.

https://account.xbox.com/en-us/Settings?rtc=1&wa=wsignin1.0&activetab=main%3aprivacytab I've read that it could be account privacy settings, something is preventing the Xbox app from using multiplayer

Could you grab and post a log file from your friend on pastebin.com and post that here? Make sure it's set to public.

It was a live fix done on the EOS/EAC end (as in no update needed on your end). The server likely needs to be rebooted. Try reverifying your files too through Steam. If none of that helps, try doing this: From Windows Start, search for cmd. Right click on Command Prompt and click Run as administrator. In the console, type the following command: ipconfig /flushdns If the command was successful, you will see the message "Successfully flushed the DNS Resolver Cache": Afterwards, type: netsh int ip reset Once done, restart your computer

Thanks for reporting back, glad it's resolved

This should have been fixed in the backend. Try again and report back.

This should have been fixed in the backend. Try again and report back.

This should have been fixed in the backend. Try again and report back.

Log file please.

Yeah this is normal behavior, including idles hitting around 19.95 fps or so, the only time you should be getting concerned is if the fps goes below 20 with heavy action going on.