World chunk generation/rendering is slow and extremely laggy at times.

I have also tested this on a iPad Pro and the issue is 10x worse

I have an iPad 4 and have noticed this on 1.0.0 and 1.0.1. If I'm in creative and flying over the ocean it is especially noticeable. In some cases, when I hit an unrendered chunk and cannot move forward, I've sat still for several minutes and waited for the world to render out to my distance settings, but it will just sit there for minutes without updating the view more than one or two chunks to the side. However if I continue trying to push forward, it will sometimes render dozens of chunks very rapidly but only out about 4 chunks ahead of me, then I have to wait again.

The problem becomes much worse if I'm hosting a game with my daughters over wifi. If we are in different dimensions it is almost impossible for any of us to do anything.

If there is land ahead of me, it seems to keep trying / succeeding in rendering out to my max distance.

This is happening to me as well every since I updated with the latest upgrade in December 2016. I actually purchased the holiday resource. Now I am very sorry I upgraded and attained this resource. My game had very little glitches until I made the update. I cannot even walk and my would generate fast enough. I have to wait and come back! I hate it! My daughter, husband and grandchildren are all having the same problem. Please, someone, help... I am losing interest, and I started this game to please my grandchildren. They love the worlds I create for them to explore!

This is happening in version 1.0.3

Happens in 1.1.0.1 on kindle fire running fire os 5.3.2.1

im having the same problem on realms and on my world im on minecarft windows 10

Adding Android 6.0 MCPE 1.1.0.9 (and before) as also still being affected.

Is there any clue that the development team are aware of and acting on this issue? There is no point playing this game at the moment because 1.0.8 seems far worse than the previous version. Exploration is almost pointless once you have reached a certain size as it is agonising waiting for the chunks to load and render.

Same. It's less intense in 1.1.0.9 on my Note 5, but still buggy with ocean chunk rendering, especially with a big render distance and when holding out a map.

Have recently downloaded 1.1 for iPad. Rendering is far worse than it has ever been for me. Huge areas that take ages to render - over cave systems particularly and even on land now whereas it was worse in the ocean. The question is this. If the actual georgraphy has not changed that much e.g. Number of mines/caves for example, why does every release make is worse and not better? Basically it was OK once but recent changes are just dire.... I still do not know whether this failure is even on the developer's priority list.

On my + 820 MB world game is unplayable, massive lag spikes and chunks render veeery slowly especially in jungle area. Version: 1.1.1.

Have the same on my world i just started a week ago. had this problem since 1.0 and now ver.1.1.1 and its still isnt fixed.

Just downloaded the latest update 1.1.1 which was supposed to address this but it is no better on my Win10. Tried lowering rendering distance, reducing graphics, nothing helps. Still huge blank chunks in front of me. Game is unplayable like this.

Confirmed again in 1.1.2 on the Windows 10 edition.

Hello everybody I come to you today because I have a problem with my worlds there is a bug and it takes the sea from my world's and makes a huge hole and it 1200-2000 block's high and wife and I have a team working in it but they can't find an answer.

Our realm has been experiencing a lot of issues loading chunks since the 1.1 update in addition to extreme lag and frequent crashes. When the 1.1 update came out, we explored 10,000 blocks from spawn in order to find one of the new woodland mansions. Often when joining the game, a player has to stand still and wait 5-10 minutes for the chunks around them to load before moving. This happens in frequently traveled chunks like the spawn area as well as individual player bases and in the nether. Using maps seems to exacerbate this issue on single player games as well as multiplayer.

Confirmed in 1.1.4.51

My LP world had me been experiencing this issue. Chunks can't load or take a couple of min causing lag on the world. I know my device can handle it just MCPE not letting the chunks load. iPod 6 gen MCPE user.

In official part of changelog to 1.2 Build 1 there is a bug fix: "Optimized chunk generation and loading". That's mean's this bug will be finally fixed in Better Together update! Hurray!

Fixed in:
1.2.0.2

It s not fixed at me-Samsung Galaxy J5 2016 I have insane lag.

Same , its not fixed , And i am using my Windows 10 Device Too! It can deffinetly handle the game

In build 2 bug back for me. Unplayable again 😞

I get 2 fps on my world that was created in 0.15

1.1.4 was better. Loaded 1.1.5 and wish I hadn't. Game unplayable again. I am truly appalled that the game gets released with such memory issues that causes the failure to render properly.

The full 1.2 will fix all the issues. But when it coming? https://twitter.com/_tomcc/status/894294291467558912

I have the same problem with my iPad Air 2. When I travel by boat, horse or rail the terrain doesn't generate to keep up with my traveling. After about 30 blocks I have to wait 10-30 seconds for the terrain to generate. MCPE v1.1.5

The problem has gotten so bad (it takes minutes vs. seconds) to generate terrain that I've had to give up using my worlds on my iPad,

Edward Laska. I have found that installing the new software rather then applying the updates improves matters considerably. Of course you lose all the games which is a pain. Also, although everyone says that leaving apps open does not impede things they do. Something to do with memory clean up which apps do not do properly after closing - hence the well known tip to download something huge (game or films) so that the apps will tidy and free up space. Minecraft needs every ounce of space available therefore I have to shut all apps - especially safari and any BBC app. After that a hard reboot should sort it out. If the game gets bigger than 60-70 mb even with 2 gb spare for temp space then things really do start slowing down. Not the news you want to hear but I doubt very much Microsoft will sort this out for us 32 bit users.

Possibly relevant to this issue: I was playing on Xbox One last night, co-op, and as we explored overland we came across an area that just was not rendered. Or rather, I did. I was the host, and I could "see through the world" (much like the attached images) for a pretty large section (maybe 5-10 chunks?) but my co-op partner said everything looked normal. Mobs in the affected area were frozen in place and "vibrating" for lack of a better term. Trying to move, apparently, but glitched and having seizures.

The one difference I saw, compared to the attached pictures, is that chunks beyond where the glitch was were rendered fine. It was sort of like a ravine of un-rendered chunks existed between us and our destination (which was towards areas we had not ever explored before).

Closing and reopening the world corrected the issue, and we did not experience it again on our way back to base.

Image shows the effect I see in my world. In all cases where I've experienced this, I was in a boat, traveling at speed across the ocean. Possibly outstripping the game's ability to render chunks as I move.

I am having this issue on xbox1. The world will load, but there's a chunk missing where I can see through the world.

This was partially fixed in the 1.2.10.1 beta, but didn't make it to the official 1.2.10.2. However, I think it is partially fixed in the 1.2.13.5 beta

For those still experiencing this issue, could you please let me know if it ever happens in single player, and if so what the devices and triggers for it are?

Mega_Spud... I upgraded to iOS 1.2.11 and it is far slower than 1.2.10. I thought it had finally been sorted but the latest released version is far worse - a retrograde step. I always play single player and usually with wifi off and I have downloaded a RAM cleaner so that I can clear unused RAM before I start. It is glitchy, suffering from more freezes for measurable seconds, as you are digging for example. Using explorer maps has become a bit of a nightmare again with chunks taking a long time to load/render and this is with a small explored world is less than 30mb. So the problem has not been solved. Hope this helps.

Ok thanks for the info!

Mega Spud.... in addition, the time it takes between the Nether and Overworld is very much longer - so much so it is boring, frustrating and makes game play tedious. May not be connected but 1.2.10 was so much better

Still affects 1.6.0.1

Seems to mostly affect the mobile versions. I've been playing in W10 but its fine as long as I'm not travelling too fast via riptide+rockets with elytra. But I get about 15 fps or lower when in mobile even with the render dustance set to minimum.

Still affects 1.6.0.5

Still affects 1.6.0.6

Can confirm this bug with the latest edition for Nintendo Switch (as of July 22nd, 2018). Chunks can be slow to load depending on the terrain. This bug does affect multiplayer gameplay on the Switch and it has occurred several times. If we wait a long period most often the chunks do load but it does take some time (10s - 1min+).

World was generated new as of the Aquatic Update's release (bought newly for the Switch).

Getting this issue on Switch.  I have one area where several chunks refused to load even producing black blocks on a map.  Some of those chunks eventually loaded after going away and returning a few times but others stubbornly remain.  If you look into one there is no bedrock and you could fall into the void.  Mine are in an ocean SW of my house (near spawn) by about 1500 blocks.  I've given up flying as I keep running out of terrain and hitting an invisible barrier.  I also died once when I swam into an unloaded chunk, presumably I fell into the void.  

Still affects 1.6.0.8

Mods needs to re-evaluate this.

The main issue on this page is the rendering issue of how long chunks take to load, with two screenshots touching on a second opposite issue of the coding's permanent destruction of game chunks!

To that end, MCPE-38165 is NOT a duplicate because it is SOLELY about the coding's DESTRUCTION of ENTIRE chunks AFTER RENDERING had already occurred at least once in the game.

@unknown: Yes, I agree that your other report describes a different issue. I will reopen it momentarily. Sorry for the delay in noticing your appeals.

Can we please make this glitch a priority and not wait to fix it?  This one is particularly game-breaking, and I don't think we should wait!.. Also @auldrick My post was for Xbox One and this is for Nintendo/iOS, should it still be marked as Duplicate?

@unknown: This report is not marked as a duplicate, so I'm not sure what your question means.

Regarding priority, once a report has been turned over to the developers, we on the bug tracker can't really do much to move it along. You in the community actually have more power than we do in that respect, by voting for an issue. Since this report is already one of the highest voted, you can be sure it has a relatively high priority.

But priority isn't the problem anyway. The problem is that this isn't a bug, it's a performance issue, and there's a huge difference. A bug is relatively easier to find and fix because you know what the code is supposed to do and you can read it and figure out where it doesn't do that right. But that doesn't work for a performance issue.* With a performance issue, the code actually works correctly already, it's just too slow, so you have to take a different approach: You have to figure out a way to redesign parts of the program to make them run more efficiently. The key word here is "redesign": Designing is a creative process, not a technical one. It has to wait until inspiration hits, and there's no way to predict when that will happen or to make it happen sooner. And a lot of the time, an idea that sounds good at first doesn't work out and you have to start over again. On top of that, even after you've found a good idea that works, design changes usually require a lot more studying and code modification than bug fixes, so that makes performance issues take longer to fix too. I hope this explains why solving this problem is taking longer than everybody wishes it would. Unfortunately, it can't be helped.

(* Actually, sometimes bugs can cause performance issues too, but those are relatively quickly found and fixed. That has already happened in this case, which is why the problem improved for a little while before it got worse again.)

@Auldrick To be honest, I'm not a dev, and I'm not an expert coder... BUT, a lot of the bugs on Minecraft that I find are pretty cut-and-paste... All the stuff you're explaining, I  understand!  🙂  I have enough experience in Minecraft I can usually find a bug and the likely cause of it too!  I understand all the processes and things for fixing something, and I think a lot of the players of Minecraft do as well.  I asked about priority because I think we as players become frustrated when we have to wait for mild bugs to be fixed; and in this case, catastrophic bugs...  It worries me, for this glitch that it is so game-breaking it should be prioritized whether players up-vote it or not! 

I understand this is a performance issue, or combination of bug/performance.  But, regardless it can be classified as a bug and we don't really have an option to separate the two when submitting reports.

The "duplicate" I was referring to was the post I created for the Xbox One platform, they marked it as a duplicate of this which is for Nintendo, that was my question/confusion.

MCPE-39252

@unknown: Yes, marking your report as a duplicate was appropriate. Don't worry, we won't overlook fixing this on the Xbox One just because it's not listed as an affected device above, and your report won't be ignored because it's closed as a Duplicate.

As we're preparing to pass a report to the developers, we read through all the comments and linked reports to make sure we're getting a complete picture, and we look for relevant info to add from other reports. This particular problem occurs on all platforms, so listing them individually wouldn't be helpful. (Over 90% of bugs cross platforms, so we only highlight it when a problem is clearly limited to certain platforms.) Occasionally, we might overlook something relevant. If you think your report mentions something unique that we've overlooked and you're very sure it's relevant to this problem, we welcome you to add it here in a brief comment. Just please try not to speculate; that just adds to our (and the developers') workload.

The developers also have access to this system. If they find there's a platform-specific aspect of this problem they'll come back and look through the comments and linked reports for more info, so they can see your report if they need to. (Unfortunately, for a report like this one where there are dozens of duplicates, they probably won't read them all because that would take too much time. That's one reason we stress searching first to avoid creating duplicate reports.)

Load times on the Nintendo Switch also suffer a great deal, and it's gotten worse since the 1.8 update.

On my end, this seems fixed in 1.9.0.5

I have ram 4gb avaliable 1.2 GB ram, but lagg when fall some gravel world 1.1 GB, because fps is low and too much some memory (500-800 MB). But the chunk next generation is slowest when using some falling gravel with MCPE Master

Affect 1.13.0.2 and 1.13.0.4

Still not fixed on 1.14.1, chunks load really slow and random on nintendo switch.

Nintendo switch chunk loading is still slow. The custom tegra x1 may not be as powerful as the xbox one or ps4s cpus but it is not THIS much slower.

chunk loading also slow on v1.14.20 and v1.14.30

you can even fly elytra properly

I still have big issue to fly with my Elytra on my switch. Is there any solution on the way after more than 3 years?

Very slow loading while flying without elytra across the world on XB1X. I was hitting void area constantly.

Chunk rendering is very slow on bedrock especially on the switch I cant fly with my elytra properly the world around me needs so long to load PLEASE FIX THIS A LITTLE BIT

Affects 1.16.0.61

Affects v1.16.0

Flying with an elytra to fast can still cause you to hit a void wall.

Especially a problem with the nether, as chunks there seem to load slower (interestingly chunks in the end seem to load faster, but only with islands).

Additionally on switch chunks seem to have "lazy" loading, this can be seen when loading into a world, or just walking, chunks only load if they are relatively close to you, and not at the edge of the render distance (the fog).

Also, I don't know if this is a seperate issue, but when flying with elytra, then coming back to your base, the lighting is not loaded in, and it takes a couple of minutes to load in and make everything look normal.

Has this issue been acknowledged by the developers, or is it low on the priority, because this majorly harms the end game of minecraft, which is why the majority of players don't notice it.

It happens in creative, but it doesn't really have a consequence there.

All we can do is wait patiently.

i have a problem when i load in a world its all blank and i can see nothing only mobs and animals and some writing is missing and my custom characters head is missing and this is all on the windows 10 can you fix it?

This whole issue basically forces you to have a realm if you want to have a good experience in the end game.

@Borys janishweski I think your issue might be seperate to this issue, so you could create a new bug report for it (but search for duplicates first).

Absolutely a huge problem on Switch 1.16 as well now.

Don't even need to mention flight, the slowest horse is now too fast by about 30 seconds.

I tried flying on an old laptop from 2012 on battery power, and chunks still loaded faster than the switch version (no void walls were hit!), so maybe the switch version has an issue with it's chunk loading being lazy.

@unknown: The bug tracker staff is just community volunteers. We don't have access to Mojang's internal systems so we can't see what they're doing with the reports we forward to them. Questions about the status of a report need to be directed to the Community Management team. Also, please don't use the comments to make general remarks and chat with other users. The bug tracker is not a discussion forum (there are many others available). Comments are meant for providing additional information that the developers might find helpful when working on the bug.

@unknown: To report a bug, you don't just add it in a comment on some random unrelated bug, you need to create a bug report of your own, and if you have multiple bugs you need to create a separate report for each one. But it doesn't sound like you've actually identified a bug yet. I think you might need to try Community Support first (see links below). Incidentally, the bug tracker doesn't fix your bugs for you, it helps you report a persistent, reproducible bug to the developers so they can fix it for everybody. Community Support can help you solve your problems if they're not caused by a bug, or if they are the community can help you understand and describe it better so you can create a useful bug report here.

Everybody: This ticket was originally reporting severe lag and slowness in a very early version of the game. That problem crossed platforms and affected all but high end devices. It was caused by several pieces of inefficient code in that release. The developers tuned the code for better performance back in the 1.2 release, and I suspect most people were satisfied with the improvements by at least 1.211 because new comments about it virtually ceased at that point. Also, @unknown asked for comments from anybody still having this issue at that time and there was virtually no response.

We probably should have closed this ticket at that time, but we didn't because we weren't sure if the developers were done with it. (They work on tuning all the time, actually, and it's not always clear whether a particular bit they've changed will improve the slowness described here.)

Over time, a few more people have joined the report, leaving comments about it still affecting them. Since the great majority of people were satisfied long ago, we believe these later comments are caused by something other than the original problem reported here. For this reason, it would be best if they were reported separately instead of added to this report. The benefit is that a new report can give more specific information about what game mechanics feel too slow, and perhaps observations about conditions that make it better or worse. Since these aren't general all-platforms problems, the devs will need this more specific information to address these issues. So we're asking those of you who started commenting after March 2018 to create a new report that describes your specific experience of slowness or lag.

As for this report, I will soon be closing it as Fixed, unless any of the original (pre-March 2018) commenters respond to say it was never fixed for them.

Sorry about commenting here, I only did due to the fact everytime I made a bug report it got marker as a duplicate of this report.

Hasan: No worries. In fact I'm a little concerned that the helpers will do that with the new tickets I'm asking for, but I'll try to impress on them not to. If you know the number of your bug report that got closed, I'll see if I can reopen it so you don't have to create it again.

So should I wait until this bug report is closed to create new bug reports, or just create them regardless?

No need to wait, but did you see that I was offering to reopen the ones you already created? Just give me the report numbers if you have them.

Unfortunatly, I cannot find the old issues I may have created, likely because they were made on another jira account, so I'll just create new seperate issues.

Thank you for your continued assistance.

Made new bug report MCPE-85614

Can confirm this happens in 1.16.0 on Nintendo Switch. Will upload a video shortly.

@unknown: Thanks for the video. It looks pretty much the same as mine and, I'm sure, what may other people are experiencing in 1.16. The devs need to do some more tuning. which is what they had to do for this original ticket but the tuning will be in different code, and it will be easier for them if we make a new ticket to get rid of the information for the problems that were already fixed. So I'm going to make Hasan's new ticket, MCPE-85614, the parent ticket we collect these reports under. I will copy your videos to it, and you probably want to upvote and watch it because I'm about to close this ticket.

Edit: I just realized the video I looked at was attached by Hasan, not you, but I assume yours will look much the same. If you'd like, you can upload it to MCPE-85614.

This issue was mostly fixed in 1.2, with additional work done at an unknown later time.

Also affects on 1.17.0 on 2GB RAM phone