Turns out the LOD renderer is much slower, and far less symmetrical than the internal renderer, that's not a negative thing, I 100% understand why this is. It's just very difficult to realize this is what is happening as it is possible to move in range for the internal renderer to render a chunk, pass through that chunk, and move out of render range of that chunk before the LOD renderer can build an LOD for that chunk which results in the chunk vanishing the moment it is outside of the internal render range. Increasing CPU load (if you can afford it) helps a lot but even on my 11900K it maxes out my CPU quickly.

Turns out the LOD renderer is much slower, and far less symmetrical than the internal renderer, that's not a negative thing, I 100% understand why this is. It's just very difficult to realize this is what is happening as it is possible to move in range for the internal renderer to render a chunk, pass through that chunk, and move out of render range of that chunk before the LOD renderer can build an LOD for that chunk which results in the chunk vanishing the moment it is outside of the internal render range. Increasing CPU load (if you can afford it) helps a lot but even on my 11900K it maxes out my CPU quickly.

I get that from an inside perspective this might seem extremely obvious but from an outside perspective it's not very obvious. That being said, given how many of the #help-me posts are about this or very similar issues that I believe are being caused by this, I dunno... "misperception", it might be worth adding this info somewhere. 

The issue seems to be that the LOD renderer doesn't render at anywhere near the same speed as the MC internal renderer. It's easy to have the misconception of "This chunk is loaded in game so the LOD for it must be good" and then leave that chunk and have it just disappear with no LOD and be confused about why that is.

With all normal rendering on I basically cannot outrun the MC internal renderer at 32 chunks which means there is no way to tell what is happen but disabling the internal renderer revealed I was outrunning the LOD renderer much sooner than I was outrunning the internal renderer so it was essentially skipping large areas of chunks behind me resulting in them disappearing the second they were out of internal render range. I assume this is due to a combination of deferred loading, priority scheduling, and frustrum culling causing LODs for chunks to be created in a discontiguous manner. Particularly the frustrum culling. It makes me curious how the frustrum culling is handled for chunks that move out of the field of view after LOD generation for that chunk has already started. Given what's happening I'd guess it dumps that process and re-prioritizes.

Turning off the internal renderer makes it extremely obvious what is happening though. Props to whoever decided to keep the debug settings exposed, thank you for that.

I get that from an inside perspective this might seem extremely obvious but from an outside perspective it's not very obvious. That being said, given how many of the #help-me posts are about this or very similar issues that I believe are being caused by this, I dunno... "misperception", it might be worth adding this info somewhere. 

The issue seems to be that the LOD renderer doesn't render at anywhere near the same speed as the MC internal renderer. It's easy to have the misconception of "This chunk is loaded in game so the LOD for it must be good" and then leave that chunk and have it just disappear with no LOD and be confused about why that is.

With all normal rendering on I basically cannot outrun the MC internal renderer at 32 chunks which means there is no way to tell what is happen but disabling the internal renderer revealed I was outrunning the LOD renderer much sooner than I was outrunning the internal renderer so it was essentially skipping large areas of chunks behind me resulting in them disappearing the second they were out of internal render range. I assume this is due to a combination of deferred loading, priority scheduling, and frustrum culling causing LODs for chunks to be created in a discontiguous manner. Particularly the frustrum culling. It makes me curious how the frustrum culling is handled for chunks that move out of the field of view after LOD generation for that chunk has already started. Given what's happening I'd guess it dumps that process and re-prioritizes.

Turning off the internal renderer makes it extremely obvious what is happening though. Props to whoever decided to keep the debug settings exposed, thank you for that.