Steps to reproduce the issue
1.Build a classic nether portal chunk loader
2.Use the command /gamerule spectators_generate_chunks false, then switch to spectator mode to observe the lazy chunk
You can also use mods like Carpet-AMS's chunk-loading function to do this more conveniently
3.Place some entities prone to this issue (listed below) in the chunk, and use the method in step 2 to put this chunk into a lazy-loaded state
4.Then, you can clearly see the entity rendering issue
The entities I know that can reflect this issue：
all the falling_blocks
tnt
all the projectiles
wither_skull
llama_spit
I have verified that this issue can be reproduced in the vanilla game without any mods installed. The mods mentioned are only used to facilitate reproduction.
Expected result
Entities render correctly on the client side.
Actual result
In lazy chunk, entities render incorrectly on the client side.
Additionally, the rendering of high-speed projectiles in entity-ticking chunks is also incorrect. The degree of deviation increases as entity speed increases.You can refer to MC-299627 for specific details on this point.
Environment
both the single-player and the server
Attachments
Comments 12
Hi!
Thank you for your report!
Can you record a video of the issue and upload it to clarify how the incorrect rendering looks?
Could you please provide a world where issue occurs? (If the file is to big to upload it here please upload it to One Drive and post the link to it here)
Could you provide an example of “classic nether portal chunk loader” build that you use?
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
the “classic nether portal chunk loader” is a machine that let the minecart go through the nether portal frequently to make the chunk keep loading within a small area
this is the video in game
Hi!
Thank you for your report!
Your game, launcher or server is modified.
If you can reproduce the issue in a vanilla environment, please recreate the issue.
Any non-standard client/server/launcher build needs to be taken up with the appropriate team, not Mojang.
A world which had previously been opened with a modified client might be corrupted. Please try reproducing the issue in a newly generated world.
If your ticket does includes any issues mentioned above, then it's likely to be closed as Invalid.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
I accidentally set this report to Private. Could a moderator please change the visibility to Public? This is not a security issue.