POI Pop-Ins

VoltraLux

Member
I'm having terrible issues with POI Pop-in and rendering of chunks, I have recently upgraded my PC to hopefully fix these issues too but still having no luck. I've increased all the view and rending options to the maximum, along with region loading and increased object quality to maximum. All settings on max or high have no effect on the POI pop-in issue either. Tried fresh installing the game, but have at this point run out of options. 

This issue wasn't present for me in A20 or the early stages of A21, popping up sometime between Alpha 21.1 and 21.2. 

The crux of the issue is that the entire landscape in the distance will pop in (Trees/terrain) as well as structures and decorative blocks like cars within a 100m range or so. Everything looks pretty awful at a distance if its even visible at all. 

Is there something I'm missing or overlooked that would solve this issue? Appreciate any input or advice. 

Specs:

GPU: Nvidia Geforce RTX 3080 10gb

CPU: i9-11900KF 3.5GHz

RAM: 32gb 

 
I'm having terrible issues with POI Pop-in and rendering of chunks, I have recently upgraded my PC to hopefully fix these issues too but still having no luck. I've increased all the view and rending options to the maximum, along with region loading and increased object quality to maximum. All settings on max or high have no effect on the POI pop-in issue either. Tried fresh installing the game, but have at this point run out of options. 

This issue wasn't present for me in A20 or the early stages of A21, popping up sometime between Alpha 21.1 and 21.2. 

The crux of the issue is that the entire landscape in the distance will pop in (Trees/terrain) as well as structures and decorative blocks like cars within a 100m range or so. Everything looks pretty awful at a distance if its even visible at all. 

Is there something I'm missing or overlooked that would solve this issue? Appreciate any input or advice. 

Specs:

GPU: Nvidia Geforce RTX 3080 10gb

CPU: i9-11900KF 3.5GHz

RAM: 32gb 
As pointed out, that thread will tell you to post a log and how to do so.  However, it is very likely that you are experiencing a problem because you are using an Intel CPU that has e-cores.  These cheap cores are horrible for gaming and if the game runs on one of those, it will perform very poorly.  You can use a program to force the game to run on a normal core instead and you will probably see a big improvement. Google betrayed me.  Ignore this.  ;)

 
Last edited by a moderator:
As pointed out, that thread will tell you to post a log and how to do so.  However, it is very likely that you are experiencing a problem because you are using an Intel CPU that has e-cores.  These cheap cores are horrible for gaming and if the game runs on one of those, it will perform very poorly.  You can use a program to force the game to run on a normal core instead and you will probably see a big improvement.
I don't think 11th-gen had E-Cores.  Pretty sure those started with 12th-gen.

Intel Core i911900KF Processor 16M Cache up to 5.30 GHz Product Specifications

 
I don't think 11th-gen had E-Cores.  Pretty sure those started with 12th-gen.

Intel Core i911900KF Processor 16M Cache up to 5.30 GHz Product Specifications
I previously had a 12th gen CPU but lower spec, but had the same issue with the POI pop ins, though I'll follow your guidance and post more detailed logs etc later on in case that helps. I'm well above the recommended specs on both my rigs though so I shouldn't really be having this issue at all though, so need to figure out why this is the case for me. 

 
I previously had a 12th gen CPU but lower spec, but had the same issue with the POI pop ins, though I'll follow your guidance and post more detailed logs etc later on in case that helps. I'm well above the recommended specs on both my rigs though so I shouldn't really be having this issue at all though, so need to figure out why this is the case for me. 
Besides the log, can you clarify if this is single player or multiplayer?  If it's multiplayer, try the game in single player and see if you have the same issue.

 
For clarification here is the information I should have initially supplied apologies:

Mode: Singleplayer

Slots: 1 Player

Region: Europe 

Mod File: None

Main Issue: Poor Rendering of POI meshes, heavy LOD and Mesh Pop-In even at short distances, terrain rendering in large chunks with landscape and foliage popping in heavily.

Log File for RWG Single Player world:

https://pastebin.com/FupZdGew

Possible issue? Line 48. 

  1. Fallback handler could not load library E:/SteamLibrary/steamapps/common/7 Days To Die/7DaysToDie_Data/MonoBleedingEdge/data-0000019FD66FF0A0.dll



System Information:

GPU: 

GEFORCE RTX 3080 VENTUS 3X PLUS 10GB OC LHR

62% Utilisation

7.6/25.9GB GPU Memory

7.4/10GB Dedicated Memory

0.2/15.9GB Shared Memory

Driver Version: 32.0.15.5585

Direct X Version: 12 (FL 12.1)

CPU: 

i9-11900KF 3.5GHz

33% Utilisation

4.57GHz Speed

8 Cores

16 Logical Processors

1 Sockets

RAM:

32GB 3200MHz

15.6GB in use / 16GB available 

25.4GB/54.9GB committed 

16.1GB Cached

Paged Pool 589MB Non-Paged Pool 430MB

Attached is an example of how poorly the meshes are appearing even at close distances even with mesh distance at 2000, mesh quality set to yes, dynamic mesh on and off altogether, max region load, minimum region load etc Tried a massive range of settings at min, mid and max with no change to the issue.

Screenshot 2024-05-26 195100.png

Besides the log, can you clarify if this is single player or multiplayer?  If it's multiplayer, try the game in single player and see if you have the same issue.


I've supplied as much information as I believe I can above, but yes it was a single player game only, thanks for looking into this for me, I appreciate the support

 
Last edited by a moderator:
CPU utilization is meaningless. You aren't going to see that go any higher.

Disable all options with the word "reflection".

Set Shadows to Medium.

In fact, you should probably use video options similar to this, except with Shadows on Medium, and maybe turn off SSAO as well.

138E35B6A6D20DB093D0A65023991D43B1E26055


Also be certain you have fully excluded the game client and save folder from security software. 

Additionally, ensure you have removed any system bloat that isn't needed. Asus/Acer/MSI/Ect. tools to "manage or speed up performance" actually do the opposite 90% of the time because they are built on standards that are over a decade old. Crap like GeForce Experience doesn't make life easier in the long run. It just gimps your performance by heating up resources and automatically configuring games with improper settings for your hardware.

Possible issue? Line 48. 

  1. Fallback handler could not load library E:/SteamLibrary/steamapps/common/7 Days To Die/7DaysToDie_Data/MonoBleedingEdge/data-0000019FD66FF0A0.dll


Can likely be ignored, but validate the client a few times after you ensure it is properly excluded from all security software.

 
So, I changed all my video settings to the recommended ones in the screenshot, uninstalled geforce experience, verified the files and excluded the game exe and save folder from security software, but the issue wasn't resolved. Visited chunks are still popping, new chunks are popping in heavily, terrain and landscape the same. Not sure what else can be done, would have thought being well over recommended spec would have solved this issue, especially on a new machine and fresh install of the game. 

This is a video of what it looks like if it sheds anymore light on the situation. 

BADRENDERING.gif

 
So to update I've tried:

  • gfx lodbias command, this has no effect on POI imposters
  • changing CPU core affinity to 4 cores and no effect
  • changing dynamic mesh on/off no effect
  • changing max regions, mesh quality, mesh distance 2000/1000/500 no effect
  • disabling occlusion no effect
  • disabling all reflections no effect

I've researched Youtube creators' videos and while there is a level of LOD pop in for objects there isn't anywhere near as bad POI imposter exchange as I'm experiencing.

I've reviewed my own previous footage and POIs would stay fully detailed at larger distances than I'm experiencing now, despite reinstalling the same game version as the version the footage was taken on, so my suspicion is now on one of my components.

This issue has persisted over two completely different machines, one running an i5 and i9, one running a 3050 and 3080. Both running 32gb of RAM. 

If anyone has any insight, a useful command to extend the distance of the fully detailed POI before the simplified meshes kick in, or any advice hardware wise I would be much appreciative as I have hit a brick wall with this. I have seen a similar case of this posted in a video on reddit but the solution didn't seem to be found either. 

 
Back
Top