1.17.30 update no longer renders chunks in the Papyruscs map

[RoboticRice]

If I load a save file from prior to 1.17.30 into Papyruscs, it generates a full map just fine.

However, opening up that old save file in Minecraft 1.17.30, then flying around a bit, exit & save, and finally trying to generate a new map using Papyruscs on the updated save file has blank chunks where you have traveled (aka, loaded the world using the new 1.17.30 codec?).

See my before & after screenshots. You can clearly see the path I took b/c there are missing chunks.

I'm not sure what changed between 1.17.11 and 1.17.30, but now chunks aren't loading into Papyruscs.

PS: I had imported a section of a save file that was saved in 1.17.11 into the world, which explains the additional content - it wasn't explored and added to the Papyruscs map, it was edited in using Amulet (world editor).

EDIT: I'm using release 0.5.1

[Kinboise]

Same issue here. It seems that papyruscs has rendered a lower Y layer instead of the top.
1.17.11:

1.17.30:

Please fix, a map renderer really means a lot to us, thanks!

[RoboticRice]

Upon further investigation, I believe the change that caused this is from 1.17.30 update is:

"Added logic to save and load SubChunks by absolute Y index to support data-driven dimension height ranges"

From what I've been reading, there are going to be changes to the world height and depth for the Caves & Cliffs Part II update not yet released.

It's strange that some chunks can still be loaded in Papyruscs normally, but the new chunks are loaded incorrectly. There's probably some flag in the db files that specify if it's been regenerated with the absolute Y index vs the old (presumably relative?) Y index. I anticipate that should be an easy-ish fix to implement in Papyruscs, now that you know what to look for.

Amulet was able to very quickly adjust their software to work with the 1.17.30 update, and that was their problem (sub-chunk loading errors).

[dopazz]

I am seeing the same: I run Papyrus using default Y limit and default ceiling trimming:

papyruscs --world "_level_import" --output "_output\normal" --dim 0 --forceoverwrite --chunksperdimension 2

Some of the chunks are rendering as the subsurface rather than the ground level. This only occurs in areas that I have revisited since the 1.17.30 update.

I also run Papyrus with limity = 12:

papyruscs --world "_level_import" --output "_output\slice12" --dim 0 --forceoverwrite --chunksperdimension 2 --notrimceiling --limity 12 --brillouin_divider 1

Instead of the chunks rendering as subsurface, they are holes in the map:

These holes are not the same chunks that rendered strangely at the surface level.