Mod sometimes fails to cull entities

[cajunphoenix]

I installed this mod to fix lag issues with mekanism and create, and initially, it worked very well with fixing lag. However, I noticed that if I move far away from a chunk and then walk back towards it without actually entering the chunk, the mod sometimes fails to cull the entities inside it.

This is what happens when I do what I mentioned above

and this is what happens when i just walk towards the same point without fully leaving the area.

[tr7zw]

I can't fully follow. EntityCulling has no concept of chunks that have been entered or not. Also, some blocks of Create are excluded from culling. Onto of all of that, since you are using shaders, so the f3 numbers are garbage due to the shadow passes.
Check without shaders, then it should make more sense.
Doesn't help that this is 1.20.1 Forge with Oculus/Embeddium, which both are dead and unsupported. God knows what kind of bugs/janky behavior they have.

[cajunphoenix]

did the test without shaders same thing happened i think the jank finally caught up with my world

[tr7zw]

Huh, if the 18860 block entity number is true, that is concerning 😅. The culling itself seems to run fine, assuming the last pass number does change, so either these are whitelisted/have culling disabled, or some other technicality is going on. Sadly haven't yet implemented the debug functionality I want to better diagnose stuff like this. I have to make a release today due to 26.1.1, I could try to quickly smash together a debug tool to get a better idea of what is going on/what it is/isnt rendering.

[cajunphoenix]

Well if you need my world to test i can give it to you

also heres a youtube video github wouldnt let me include
https://www.youtube.com/watch?v=ZR3prail_dw

[tr7zw]

Ok this is really weird. Will try to bodge some debug code together that dumps out what its doing and why.

[tr7zw]

@cajunphoenix The 1.10.1 release has some debug stuff, but sadly it's probably not complete enough yet to fully figure it out. Get into the 2 situations, and enter into the recipe book in your inventory entityculling_debug. That will generate a json file with some info. Upload these 2 here (bestcase labeled), then I can try to see if anything sticks out.

[cajunphoenix]

Hey, my bad i forgot to tell you, but I think I found the problem. It seems "net.minecraft.world.level.block.entity.BlockEntity" only works within 8 chunks of the player no matter what render distance, simulation distance or closerThan is set to.

I was able to fix it though using chloride, since it lets you cull everything outside of a set distance.

[tr7zw]

Oh yea thats by design. The vanilla entity render distance is 64 blocks aka an 8 chunk square around the player. Increasing the culling distance further than that would eat too much memory for the caching and be slower than just rendering in many cases.
But I don't understand your answer, the distance is this 64 block distance, outside of that block entities are not rendered. So what did you change using chloride to achieve what?

[cajunphoenix]

The main problem was with mekanism pipes outside of the 8 chunks or 128 blocks werent by caught by entity culling and were still rendering for some reason and what chloride does it forces everything past 128 blocks not to render

[tr7zw]

That sounds more like you have some mod increasing the blockentity render range. That would explain everything I think, since entering the area updates the culling values then going out of range they stick. Usually thats not an issue, since they are not rendering anyway. And then flying in from outside, the flags arent setup since its outside entitycullings area, so they render due to the increased renderdistance.