Concurrent Chunk Management Engine (Fabric)

Concurrent Chunk Management Engine (Fabric)

231k Downloads

Slow chunkloading when joining a world

DragonEggBedrockBreaking opened this issue ยท 3 comments

commented

This is similar to a tic-tacs issue, but has a few differences:

  • There is no FPS lag from my experience (tested both with and without sodium and the FPS is the same as without barium both times).

  • It is less extreme than with tic-tacs (in tic tacs chunkloading just stops working, in barium, it freezes for ~20 seconds, then chunks start loading, then chunkloading freezes again, etc.)

  • In tic-tacs, chunks stop loading after some time, whereas with barium, this issue occurs on joining a world, and becomes less severe after a few minutes. Even after a few minutes, it still freezes once in a while, but the freeze is shorter, and freezing becomes very rare.

  • If phosphor is present, the issue doesn't last as long, and chunkloading starts working sooner (the issue still exists tho). I have not tested yet with starlight.

  • If phosphor is present, i can interact with the unloaded chunks (e.g. place and break blocks inside them), and updating the chunks loads/renders them, but without phosphor, i cannot interact with the chunks. I have nt tested yet with starlight.

Hardware:

  • i3 6100U
  • 8GB 2133MHz RAM
  • Intel HD Graphics 520

Software:

  • LMDE (Linux Mint Debian Edition) 4
  • MultiMC 5; 0.6.11
  • Minecraft 1.16.5
  • Fabric 0.11.1
  • OpenJDK 11
  • Barium 0.1.0-rc2
commented

Can reproduce with:

i7 7500U
Intel HD Graphics 620
Windows 10 2004
AdoptOpenJDK 11

(all other things are the same, e.g. ram, mc version, fabric version, etc.)

commented

I have not tested yet with starlight.

Just tested with starlight, and the exact opposite happens to before; chunks load fine, but despite my earlier comment without starlight:

There is no FPS lag from my experience

Starlight actually causes decreased FPS (for ~30 seconds) on joining the world.

commented

Issue no-longer occurs with rc3 and rc4. Seems the issue was only present in rc2.