Hi
@faatal I've been testing a bit. First of all, good job on the kynematic body issue. I couldn't find it anymore, resulting in smoother combat and hunting .
FEEDBACK A19 B180 full wipe (AppData, profiles, steamapps, everything) , new map:
The two previously reported issues (loading and unloading of elements and simultaneous spawns & sleeper spawns) are still the main problems for performance.
VRAM seems to be better and better the more you guys look at it. LODs of decoration seem to work better overall. Graphics performance is OK for the moment until more content is added. Memory still fills up too much over time and doesn't restore as well as it should, but it definitely increases slower than before.
Freezes? still a lot because of said problems. Less than a19 b169+ ? Yes, definitely. I can play for up to half a minute running through a town without freezes.
The problem with these freezes is that I cannot catch a screenshot in which you see the drop, because if my PC is freezed I can't take the screenshot in the exact moment and steam detects it just when the fps restore, so you would always see, both in console (on INF messages loading/unloading) and in game 60 frames after it happens.
Here's a new one. You might already know it, but I've never reported it with screenshot:
"WRN Spawn class xxxxxxxxx can't walk on block sleeperidle with wal Type 4."
This freeze happened while several sleeper volumes were also loading. so it is difficult to say if the main cause is the sleeper issue or the bug that resulted in that warning.
I can confirm that this warning was sometimes there when the "spawn freeze" was happening. At least 1 in 5 times, according to my testing data.
Next issue is a known one. DECO stuff is generating warnings like crazy and freezes the game like there's no tomorrow. Instead of unloading properly, it generates hickups to a point that freezes the game on lower systems. This madness seems like Unity colliding with genious programming. I don't know if the chunk saving and the INF lines after the warnings (INF [DECO] WRITTEN 0) are somewhat helpful to the problem. The RSS memory feed surpassing the 4 gb line and generating bumps is also a reason for concern.
Notice that the game ramps up the memory usage too fast
I had to change the resolution to 720p to continue testing, but only 5 minutes into the game with one 720p to 1080p resolution adjustement and the RSS feed on the console went from 3500Mb to 4200+Mb with no resets (from higher res to lower and the memory keeps ramping up too fast, THAT is a problem). While RSS might be no reliable indicator of memory usage, if it goes up too fast that means that stuff happens and garbage hurts .
Good news is, it NEVER started in 3500+ Mb. EVER. So things are improving. Before it was 3890 Mb minimum at the very start.
I hope that within this post you find something that is remotely helpful.
Cheers!