Constant Freezes on Alpha 19

A

Allexio

New member
Hi.

I have previously played A16, 17 and 18.

None of them had the following issue.

My set up:

I am using my PC as a dedicated server and I play on it at the same time.

Specs:

CPU: AMD Ryzen 1600 6 cores/12 threads at 3.2

GPU: Nvidia GTX 1080ti

RAM : 16GBs of DDR4

OS: Windows 10 1909

Storage: 7200RPM HDD

This was on a newly generated (post A19 stable release) 8000x8000 RWG world

Problem:

I play the game on my system at a constant 60+ FPS, around 70FPS in the forest biome.

In fact, I feel like the performance is better than it was in alpha 18.

HOWEVER.

Whenever I move around, and I don't mean move around at high speeds on a bike or something, I mean just walking, every few minutes (2-15 minutes) I get this crazy 3-10 second freeze. (someone else posted this video which is the problem I have except I have it while walking around: 


The game isn't unplayable. BUT. This has already caused my death multiple times. It's horrible. The game just literally freezes for a few seconds and then everything is caught up when it's over. It was so bad once (like 7-10 seconds of freeze) I thought the game had crashed.

I have been on multiple threads and it seems that people point towards POIs being the culprit with an Alpha 19 version 159 (I think?) being the culprit because it introduced in game loading of prefabs or something and the problem has existed since then...

Can't this be rolled back or an option added to the in-game options menu?

Playing the game like this is extremely frustrating.

I've also seen lowering terrain detail to low being recommended... I'll be honest I don't want to gimp my whole experience playing this game when my FPS averages 70. No really, the performance is good, it's just those freezes.

Any help would be much appreciated.

 
Have you tried without mods? The game uses a lot more data than most games so it calls your storage more often; your HDD could be a bottleneck on that. And make sure your page file is set to automatic. Oh, and make sure your worlds are in multiples of 1024, so 8k would be 8192

 
Last edited by a moderator:
That CPU isn't a real great performer either. It does ok with single-core speeds, but loses almost a third of it's power when programs utilize multi-core performance. You may have some luck in limiting the cores the game client uses.  

Will also note that the CPU is a big bottleneck for that GPU. At 1080p in a normal game you're looking at an immediate bottleneck of about 15% that will cause FPS dips and freezing. In a CPU-bound title such as this one that will be even more obvious.

 
@AllexioI get these occasional pauses too, (not 7-10 seconds, but more like 2-3 seconds).

I think it's the spinning hard drive. I 've tested on the same machine running from an SSD

and a spinning drive, and I get the pauses on the spinning drive, but not on the SSD.

 
SylenThunder said:
That CPU isn't a real great performer either. It does ok with single-core speeds, but loses almost a third of it's power when programs utilize multi-core performance. You may have some luck in limiting the cores the game client uses.  

Will also note that the CPU is a big bottleneck for that GPU. At 1080p in a normal game you're looking at an immediate bottleneck of about 15% that will cause FPS dips and freezing. In a CPU-bound title such as this one that will be even more obvious.
Click to expand...
This is just plain false.

The Ryzen series is *built* for multi-core usage...

I have also so far *never* been limited by my CPU in any game, this one may be the only exception, but I very much doubt that. I play at 1440p, but even at 1080p, it's VERY hard to be CPU bound at anything less than 60 FPS in 99% of games.

Also I really don't see how what you're saying has anything to do with my issue. Your comment is just so completely off the mark...

Even IF my performance on this game was CPU bound, that wouldn't explain the ridiculous freezes...

 
Last edited by a moderator:
Allexio said:
This is just plain false.

The Ryzen series is *built* for multi-core usage...

I have also so far *never* been limited by my CPU in any game, this one may be the only exception, but I very much doubt that. I play at 1440p, but even at 1080p, it's VERY hard to be CPU bound at anything less than 60 FPS in 99% of games.

Also I really don't see how what you're saying has anything to do with my issue. Your comment is just so completely off the mark...

Even IF my performance on this game was CPU bound, that wouldn't explain the ridiculous freezes...
Click to expand...
Do some actual research on your CPU. AMD's performance in the multi-core field was pretty poor until the 3rd gen chipsets. Single-core and dual-core they can keep up with Intel all day. Exceed Intel in some cases. Once you get past that though, it's bad. 

Also, 98% of the games in your library aren't CPU-bound. Probably as many of them aren't even Voxel games. You're comparing bicycles to motorcars as every one of those games is bound to the GPU and not the CPU. Higher resolutions with this title will put more load on your CPU. It's been shown in the past that limiting your particular generation of AMD chipsets to only 3 or 4 cores for this title can improve your performance, and that's exactly a result of how weak it is at multi-core performance. Many other games don't even utilize multiple cores. This is all common knowledge for those of us who work in IT and work on hardware on a regular basis. It's extremely well documented in product reviews and chipset comparisons. It's not like I'm pulling this out of my ass. It's reality. You can either accept it, and try to work around the limitations of your hardware to improve your situation, or ignore it and be disappointed.

 
As a few people already have mentioned, getting an SSD is paramount. This game shuffles a lot of data around and even with an SSD your setup with server and client on one machine may hit limits not many other games (or artificial benchmarks) currently even approach.

A RAM upgrade to 32G might improve things slightly because it allows bigger caches.

Whether SylenThunder is right or not, you could just try to turn off hyperthreading and see if it works better or not. Can't hurt to try.

 
You must log in or register to reply here.
Back
Top