Some Trees' Leaves/Logs get cut off at chunk borders prior to world generation

I can't confirm this a bug in 0.16 0
I believe this has been fixed as tress can be seen generated in new chunks have some of their leaves generated in old chunks. This is most visible in snowy biomes where snow will partially generate under part of the tree with none on top of that part with the rest if the tree covered in snow with no snow on the ground.

Found the bug in 0.16.2. The leaves still disappear.

Steps to reproduce in 1.1.0.0:
Load this Resource Pack that will display chunk boundaries.
Set render distance to 8 chunks.
Create a new infinite creative world with the seed Tree
Once spawned, you should be on a red line. Turn to face the sun (Note this is in 1.1.0.0) and fly up.
Now go towards the sun crossing 6 red lines below you (not counting the one you spawned on).
After passing 6 lines turn 90 deg to the right and pass 6 blue lines.
Turn right 90deg again and cross 6 red lines.
Turn right 90deg again and cross 12 blue lines.
Turn right 90deg once more and cross 11 red lines.
There should now be 2 birch trees to your right that have been cut off at the chunk boundry (shown in blue).

To compare, create a new world with the seed Tree again.
Cross you 11 red lines while facing the sun.
Turn left 90deg and cross 6 blue lines to see the same trees(now a little behind you) not cut off at the border.

Devices where the above steps worked:
Samsung Galaxy s4 Android 4.4.2
Samsung Galaxy Tab 4 10.1 Android 5.0.2

Cleaning up old tickets: This ticket has not been updated recently (1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

I created a world last week on the latest Bedrock release (with Experimental Gameplay turned off) and encountered this bug (see screenshot above).

Seed: 425558590

Coordinates: 155, 64, 186

Hardware: 2017 MacBook Pro

Software: Windows 10, latest version, on a Virtual Machine

This is still an issue in 1.14.60 on W10, they are forming along chunk borders.

I think this might happen because the chunk with the tree in is loaded, then the tree is generated while nearby chunks are still unloaded.

Affects 1.16.10

To reword what I think @77Tigers said: the "branch" chunk is loaded & then the "trunk" chunk is loaded. If the tree isn't present to generate, the branches don't cross the chunk border. But then the trunk is generated with branches that were supposed to hang over pregenerated chunks, which cannot happen (yet?).
To simplify, imagine chunk 0 is the trunk chunk & chunk 1 is the branch chunk. Chunk 1 is loaded first & because there is no tree populated in that chunk, no tree generates. Chunk 0 is then generated & the game is told that some branches need to be in chunk 1. Unfortunately, chunk 1 has already been generated & the result is a spliced tree.

Does this still affect 1.16.220/1.16.230.52?

Yes this is still an issue

Affects 1.17.10/11 Hotfix & [Ex]

Affects 1.17.40.20

Following the reproduction process I identified for MCPE-23416, MCPE-97295, and MCPE-141499, I discovered that a similar process can cause the generation of terrain features to be cut off at chunk borders. When a terrain feature such as a tree crosses a chunk border and only one of the two chunks has come within a player's simulation distance, the part of the feature in the neighboring chunk can fail to generate if the player moves in such a way that the never-simulated chunk is unrendered and then comes within simulation distance of the player during auto-saving.

Steps to reproduce

1. Set render distance to 8 and turn on the auto-save icon.

2. Create a world with creative mode, seed 1686104715, simulation distance 6, with coordinates on.

3. Move to 130, -12 without going any farther north than Z = -12. Notice the red mushroom tree in the distance.

4. Move to 130, 100 and wait.

5. When the auto-save icon appears, fly straight north to the red mushroom tree you saw in step (3).

Expected result

You arrive at a complete mushroom tree.

Observed result

You arrive at a slice of the mushroom tree cut off at the Z = -112 to -113 chunk border. See https://bugs.mojang.com/secure/attachment/445159/How%20to%20cut%20off%20generation%20at%20a%20chunk%20line%20.mp4

If you don't get it, try again--I reproduced this 3 times in 7 or 8 tries. I think the key may be simulating the mushroom tree chunk ASAP once auto-saving starts.

It still affects 1.20.15
I've met a couple within a few blocks' distance

Is this a problem for anyone else in new worlds? Note that already corrupted worlds cannot remove previously generated trees.

Affects 1.21.30 too.

I am also encountering this on 1.21.31, this one really ought to be fixed since it impacts dark forest/pale forest more, and that's a big part of the upcoming release.

In some biomes (like the dark forest, and it's pale variant), even if you delete the chunks and cause them to regenerate, the problem remains because the trees do not generate in the same way each time. 

It's just really upsetting how 9 years later the report this bug is still happening. My world has not only cut trees but also cut aquifers under and above ground. I don't even know if this is actually going to be fixed anymore because it was reported so long ago. The point is, this is such a weird and problematic bug that not only bothers me but also breaks the experience of playing. Just disappointing.

I'm also encountering this issue in 1.21.70, 1.21.71, 1.21.72, and 1.21.73. It really needs to be fixed, as it's causing a lot of problems and affecting parts of the biomes. The issue happened in some biomes, such as the new biome added in 1.21.50. It happened to me after 1.21.60. Since I'd already visited a few biomes and the new Spring to Life update was released, I installed the update on my server and wanted to see the new areas on how the old biomes had been upgraded, but this issue persists. Please fix it as soon as possible, even if it might take a while.

The bug is still there in version 1.21.73

The bug MCPE-11908 is still in version 1.21.73 please do a hotfix as fast as possible

The bug is still not fix in version 1.21.73

The bug is still in version 1.21.80

The bug is still in version 1.21.81

I want to second prioritizing this issue. It breaks immersion, and after the Spring to Life release, seems to have gotten exponentially worse because that release seems to have changed tree generation. The issue shows up now on every chunk border between chunks generated before 1.21.70 versus those generated after.

Yes it's true and this is a really problem right now and it's on servers too it's really annoying please fix this for real please

The is still not fixed and it's getting worse in 1.21.90

Please fix it please

Look, almost every Minecraft player complains about this! Almost every tree is completely broken by generation are all over the world and on servers And you almost don't care at all and don't listen to the comments

She's right and you're not interested in it. I've made lots of bug reports for it, ignored them, I've also Commentary and ignored you just told me to stop with Commentary even though I just want this stupid bugs to be fixed and you're not even interested in the community!

Are you for real now 1.21.92 hotfix and it's not fix are you even Listening to the community?

We want a hotfix update for this bug

I think this bug is actually easy to fix, or at least mostly mitigate. It can be fixed for old chunks and new chunks.

-When a chunk is loaded, load also the 4 adjacent chunks, and scan the borders for cut off trees.

-If one exists, regrow the tree, but only allow the regrown tree to replace air blocks

-Ignore chunks where the player has made modifications

-Maybe have some minimum size of the cut off tree that the algorithm tries to regrow (so a random leaf block or two, wouldn’t trigger a regrow)

This has the risk of breaking some custom trees, and builds based on leaves, but is probably better than immersion breaking broken worlds for everyone. To be safe, this can even be a custom setting that can be turned on/off by the player.

I'm sorry if previous comments were mean I was frustrated about this bug that's why I'm making this comment to apologize sincerely but also to share some pictures about this bug report and a world that I have on my server and play on it very often I have backups don't worry but you can test it in version 1.21.92 and see how it behaves and I have to admit it doesn't look so good and i hope it gets fixed Although there are only 8 votes for this bug report