I experience this as well with a 7.1 surround sound headset (Razor Kraken Forged). I know of other people experiencing the same problem, not sure what their configurations are.

Wouldn't it be funny if the APEX non-owners didn't see vehicle assets as well. Every time someone drives in a new vehicle they would just see players in a seated position floating through the air.

Yes it happens on BattleEye protected servers.

I'm not sure how this can be considered resolved.

No, the players getting kicked do not own DLC.

At least two other tasks going on this. It should be a higher priority.

At least two other tasks going on this. It should be a higher priority.

For more information please see https://feedback.bistudio.com/T120747

Ultimate Wasteland server has the same problem. All server traffic stops completely for anywhere from 10 seconds to 2 minutes. I recently saw it freeze with only two people online when the server fps was at 47, the freeze lasted more than 60 seconds. When the server finally resumes the fps starts out near 0 and works its way back up to 40-50. On the physical server itself the ram/cpu utilization were both below 20% during the hang.

The problem appears worst immediately after a restart, when the server has high FPS and low player count. I've noticed with higher player counts and lower server FPS the freezing is less frequent.

I'm actually a software developer, from the symptoms it would appear to me that a deadlock is occurring. I assume this is some blocking code during thread synchronization. Here is my reasoning... the system resource utilization remains normal so it's not like an intense process is maxing out the CPU, it more like a wait on a locked resource, plus it happens more often during high FPS periods which makes sense if a "thread safe" resource was being accessed 2-4x as often.

The S3K Wasteland server is having the same issues ever since the 1.42 patch. We typically run with 100 players on Stratis, and our bandwidth usage ranged from 15-25mbps, our CPU usage was about 10-20%.

Since update... Approximately 1-2 hours after a restart we get a spike in CPU and Bandwidth. The CPU goes to 30-100% usage and the bandwidth jumps to 40-50mbps. The error log is spammed with "Server: Network message f8817a1 is pending". It comes in waves, initially it seems to subside after 10 minutes, but every time it happens it gets worse and lasts longer until restart.

For example last night the error started at 22:58:42, and by 23:04:15 it had written that error message to the logs 219529 times. That's less than 6 minutes and makes up about 50% of the log file and the instance had been running for 5 hours at that point. Earlier in the log file there are shorter bursts of the error which seems to start about 1-2 hours after restart.

Please resolve asap.