Got this problem in old worlds and new 1.14 worlds. A friend of mine reported me the same. World generation just doesn't keep up at all when flying in creative.

Pre-release 5 of 1.14 did manage to keeps up, didn't have these problems there. The pre-release is more playable then the release. But I mainly play on realms so I have no choice but to play the latest release version.

Can confirm this is happening to me too! It's most extreme when migrating older files (doesn't matter how old as long as its pre release 1.14-5 or earlier) but I definitely experience it on brand new 1.14 worlds. 

Edit: Also probably useful to know I have a monster of a computer that I use to do hardcore animation work, so it's not my computer! Other heavily intensive games play fine.

Switching back to pre-release 5 for the time being.  This makes the game unplayable especially on a world where I use elytras, horses ect.

Confirmed, completely unplayable at the moment.

I'm on a pretty good machine so the chunks load in, but I did find out that the chunks aren't rendering in order at all. Instead of chunks "spiraling" outwards from the player, they tend to randomly appear. Most times, chunks at the edge of my render distance (9) render before a chunk right next to me or that I'm currently inside of.

I can confirm that:

• In the official 1.14 release chunks render in an apparently in random order. Chunks near the player may not render and I can outrun the rendering.

• Reverting to 1.14 pre release 5 causes chunks to render in the expected way, with chucks rendering from nearest to farthest

First world I loaded in 1.14. Chunks were rendering haphazardly. The blocks were there but you couldn't see them.

I'll add that it seems to be partly related to the "don't render invisible chunks" optimization, as sometimes a whole sections of the world flash out of existence and back in as I look to sides. The chunks that get stuck invisible always loaded for me when I walked into the chunk, albeit sometimes with a small delay. This is similar to a bug before 1.14 where some chunks would stubbornly refuse to render until you broke a block in them.

Confirmed, 1.14 is unplayable. Chunks load very slowly.

I can confirm this bug. I am coming from 1.13.2 and chunk rendering is extremely slow. Sometimes even the rendered chunks in distance disappear when you get close and sometimes it doesn't even load until you give a block update. Please fix the as soon as you can. This literally makes the update unplayable 😞

An otherwise awesome update ruined by this

Please, make a nice presentation for the description of the bug! Thanks! (Model below)

And also, the title is not entirely correct because it is much more than a simple problem of rendering which is slow! It's about the generation and the loading of chunks itself!

I propose instead: The generation and loading of chunks is a nightmare in 1.14

And also, do not forget to add tags like these ones: lag, lagspikes, world-creation, world-generation, world-loading, rendering

The bug

There are big performance issues with Minecraft 1.14.

A lot of lag spikes appear when the game loads and unloads chunks.
The generation is really very slow and some chunks do not even appear at all.
Sometimes, chunks can not charge at all or can flicker.

We have the impression that we came back in 2018 with the first snapshots of the 1.14 with the new rendering engine!
How was it done to regress at this point? Because it was not too bad in 1.14 Pre-Releases...

How to reproduce

1. Create or load a world in 1.14

2. Once in play, press Alt+F3 to display the lagometer graph
3. Explore your world and keep an eye on the graph

@unknown O.o The title change was actually made by the assignee himself. They are already aware of what the issue is.

@@unknown Sorry I did not know.

Nevertheless, there are other problems with the loading and the generation of the chunks and yet, they have closed my report about that...
I was repatriated here...

There's a simple way to check if you have this issue or a different one. Try the following:

1. Press F3+A. Do the chunk work now? Then you have the issue described in this ticket.

2. Place a block in one of the chunks that doesn't show up. Does it show up now? Then you have the issue described in this ticket.

If neither of those work, please create a new ticket.

when reloading with f3 + A the chunks next to me are reloaded but those after (after 2-3 chunck) are not all loaded but only some and if I wait it is not always said that in the end all are loaded. In case everyone loads and I fly with the creative or with the elytra the chuncks have the same loading problem. While if I place a block on the invisible chuncks these are immediately updated correctly, but the neighboring chunks do not change remaining invisible unless previously loaded

invisible  Chunck                                                                     updated chunk with block    

then sometimes it happens that if I am moving fast and then I land on a chunck block already loaded this is recharged very slowly.

Can confirm, this is quite annoying. It goes away for nearby chunks when I reload chunks using F3, but shows up as soon as i move out of the immediate area.

FWIW happening to me as well. Fedora 28, openjdk version "1.8.0_201", nvidia GTX 1050 Ti with proprietary 418.56 driver from negativo17.org.

Chunks are certainly loaded but do not render until block placement etc. 1.14pre5 is fine. Changing all graphics settings to the lowest option does nothing to help.

Unplayable as is.

I am also having trouble getting chunks to load.  If I sit long enough they will but if I'm exploring an area the chunks lag badly or blink in and out if I move the camera around.  It makes exploring difficult to accomplish.  My computer is also working way too hard to resolve the issue, I've checked as much as I'm capable and tried a few basic things but my computer seems to be working fine.  It's the game that's pushing it too hard after the update.

Going into video settings and disabling vsync seems to fix the problem for me. I remember that this was the fix for a similar issue back in version 1.7

I am getting exactly the same issue as this. I have tried running the game on Version 1.13 and I do not have this problem. It's 1.14 which has made chunks load very poorly.

@violine1101 @boq Any progress reports on this would be appreciated.  I trust this is receiving the highest of priorities.  To be clear, this is a game breaking bug with no reasonable workaround.  1.14 is unplayable for a large portion of the customer base; rolling back clients and servers to 1.13 is the only way to actually play the game.  Under most considerations, this is worthy of a hotfix and I certainly hope no one internally thinks that waiting until 14.1 a month or two out is an option.  It needs to be understood plainly, the game is broken.

I am also having this issue. It is absolutely terrible - flying with elytra is an aboslute pain, F3+A does not help either.

Can somebody please try to confirm my vsync work-around?

Disabling vsync does NOT work for me unfortunately. Neither does F3+A :/

I have this issue too and it makes the game unplayable.

Brian Ronald
Sadly disabling vsync doesn't do anything to fix this problem.
You sure you had the exact same problem? You can check with mod violines instructions to see if your bug was the same.

Everyone on my realms server confirmed that they have this problem in singleplayer and on the server.

I also have this issue.  The chunks will finally load in but they tend to fill in randomly and not closest to the player.  This current server was 1.13.2 fresh install upgraded to 1.14.  My hardware is nothing impressive but 1.13.2 never did this and actually ran quite smoothly.

Also if I'm traveling too quickly and rendering new chunks it causes massive server lag spikes which may or may not be related to this issue.

Same probleme, looks like the biggest of all.

And structure datapacks Don't load propaly because of this issue

Plz fix this soon

me too, in MC-149173

it happens and blocks and entitys such as dropped items will fall through the unloaded blocks

this is what I was met with opening a new world

@@unknown: We (mods and helpers) can't give any progress reports, as we aren't Mojang employees, but rather normal Minecraft players who volunteer to help managing this bug tracker. However, I can quote this tweet by @unknown:

Hopefully we’ll have a hotfix out for you soon! 👍

I recently opened a ticket the same issue with screencap, shows resolve and referenced this ticket. Still doing it(here's the screencap)

@violine1101 @HelenAngel Thanks for letting me know, I was unaware of the Mod role in everything.

Helen, further updates through official (here, I suppose) channels is desired; more don't monitor Twitter.  Words articulating a mutual assessment of priority/urgency and ongoing ETAs are helpful.  As a server admin, I have users that are particularly anxious.

I can confirm this happens on my system too. 1.14 Pre Release 5 was fine.

i7 8700k

GTX 1070

^{1.14 release. Here is a screen recording of the problem with F3 open. Issue not present in previous releases. Looks terrible!}

^{The seed is -5289714038411177434}

1.14 causes this problem (referring to the previous video sent by Foo bar) to be verified by all those who play there even with very powerful computers.
I hope for the immediate release of 1.14.1 also to solve this bug only!

There is also a weird clipping effect when you move the camera

.

I have had some players have this problem to a greater extent than others. They set MC to be 64-bit, and removed all the JVM arguments other than setting available memory, and that seems to alleviate the issue.

Same here!

added my crash report to the mix this was while flying and pertains to the chunk errors

Confirmed. I'm guessing it's because of the update, since it has so many new details.

It looks like it priorities keeping your fps steady while loading chunks... Which I hate! I can't even fly elytra properly. I don't mind some lag, as long as the world loads fast.

the 1.14 pre-release 5 didn't have this problem and it was also a snapshot! It seems strange that then in the official version this serious problem occurs (solved in old snapshots and in any case tolerable, not like now, which is worse than the snapshots)

@doge The problem unfortunately is not the lag of the version, because on this it is very well optimized, the real and proper problem is in the loading of the chunck that is full of bugs. The problem will be in the game codes that do not know which chuncks to load giving slowness and randomness in their loading.

@Ami Sato It's probably a bug in the chunk loading code. Most of the new features were added in the snapshots and 1.14 pre-release 5 worked just fine.

Hey! I have found a temp solution. update a block (place, break, activate, etc.) inside the chunk and it will immediately load. 

Also dont stand in unloaded chunks. they can kill you if they load later. happened to me.

I just wanted to add that I am having the same problem. I can run faster than the chunks are loading in. I played over 5 hours in pre-release 2 and didn't have this issue at all.

Edit: I forgot to mention that my roommate is having the same issue.

having the same problem, makes the game unplayable 

Code cause: In ChunkRenderDispatcher (or the class that has a ThreadFactory making threads called "Chunk Batcher N"), the constructor only adds one buffer to the queue of available buffers, essentially forcing all chunk rebuilds to be serialized, run one by one.

So we get a glimpse of what it would be like if we went back to pre-1.8 non-multithreaded chunk batching 😛

I confirm experiencing this bug in Minecraft final version 1.14.

Version 1.14-Pre-Release-5 worked much better when it came to chunk loading and lighting.

How was this final version ever released with such a major bug being present???

was so excited to play 1.14, but this issue makes the game essentially unplayable.

i dont have the most powerful computer at hand, but i could load chunks just fine in previous versions. :T looking forward to this bug being fixed

I also have this big problem. In this condition minecraft is unplayable, please correct this very quickly.

also experiencing the same issues.
screenshots supplied by OP are accurate.

I would like to make my contribution with this video:

Getting this issue with a more than powerful enough system, can easily outrun chunks on foot and even quicker when on horseback. Chunk loading seems to almost freeze when the player is moving and only resumes when stationary. Never had this issue in 1.13.2 or any of 1.14 pre-releases. Even reducing or increasing allocated RAM doesn't seem to help. Hopefully this will be fixed soon, makes playing the game a nightmare.

Same here, our world existed loooots of versions ago.

In 1.13 we were able to play with 4-5 players (maybe more) with a rendering distance of 12.

Now we downgraded in 1.14 to a 8 chunks distances and it's still very slow, and the server crashes often 😞.

Make no mistake, Mojang shipped a broken product.  The fact that is clearly a critical level defect yet we receive no updates and seemingly no attention for multiple days is disappointing.  Thanks for leaving us busted on the side of the road.

Now worried that Mojang totally ignores this bug, it makes the game unplayable and yet absolutely no correction, no update, nothing in over 3 days, if its anything like the 1.13 release that had a very annoying bug (can't remember which one), we may have to wait up to a month before they fix this which is extremely annoying. I would urge anyone that want to play 1.14 to use the pre-release 5 version, if only we could find the download link for the servers for it at least.

Same issue. On our linux server that has run without a problem since 1.7, we're experiencing server crashes, horrendous lag, and incredibly-slow chunk rendering with 1.14, particularly when exploring new areas in a boat.

Exploring new areas in a boat is something we've noticed that brings the server to it's knees.  Full stop while chunks randomly load very slow all around.  Gotta just wait it out.  Another oddity is there will be times that I can place blocks and break them and get that immediate pop sound as the block breaks and immediately goes into my inventory... everything feels perfectly fine but I can't eat unless I hold the mouse button down for a long period of time.  And there are times where it never registers that I've eaten.

The only way we can play with minimal lag spikes is to all stay very close together very few chunks apart.

Guys, this is not a discussion platform, neither a support system. If you need assistance, go to Mojang support. If you want to discuss about current issues, please go to the subreddit.

What @unknown said. Please only post a comment when you have something of value to add to the report. (Also please don't add any more screenshots to this ticket, there already are enough.)

Yes, we know you have the issue as well. Yes, we know it's frustrating. And yes, this issue is known to Mojang employees. In fact, we have made a developer aware of this issue as soon as possible, and it is assigned to the responsible developer.

Mojang is currently working on releasing a new version 1.14.1 very soon. How soon that will be: We don't know yet. It'll most probably include a whole bunch of other critical fixes as well.

We will likely release a 1.14.1 very shortly with a few performance improvements and major bug fixes.

– @unknown in this tweet

Just wanted to drop some more information. Not sure that it will be of help but I am running 1.14 on Windows Server 2012 R2 with Java 64 bit. I have upped the max memory to 8G on the server and turned off "realm notifications" in the launcher and enabled the advanced options and allocated 16GB. This does make the game more responsive. Maybe this will help point in a direction to look. If you have Tons of memory, for now anyway, I would try it. It's important to note here that this issue was not immediate. It wasn't until 3 of us started playing on our internal network and started to do a lot of building and creating. One last thing, one of the players on our network has reported that turning VSync off helped to improve his playability. 

The following is my launch options for the server:

java -XX:+UseG1GC -Xmx8G -Xms4G -Dsun.rmi.dgc.server.gcInterval=2147483646 -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M -jar server.jar nogui

Hope this helps

When you have this issue, if you press F3 + A to re-render the chunks, they will eventually reappear fine if you stand still. In the case this doesn't work, then you don't have this particular issue at this time, and your chunks loading issue is caused by your server falling behind ticks. In this case, the issue may be caused by a large set of factors that might be resolved or not in the future. If you are in this situation, I suggest you to run a debug profiling (/debug start - close, report in debug folder), and then either try to understand the cause yourself and solve it, or open/search a ticket related to the cause of the lag.
This is why displaying information about the server part or saying that the "F3 + A won't work" will be irrelevant on this particular case. 😉

@Johnibur Thank you for adding this information! I was also going to report that chunks load almost normally when standing still (still not quite as fast as they used to). I will go ahead and add everything else I discovered:

• The issue is definitely client-side. I watched the server's network packets while flying around and noticed that network traffic nearly stopped way before the chunks were rendered in-game.
  In addition, the chunks still seem to exist even if they are invisble. I could boat through the ocean and over the invisible (void) chunks without a problem. I also noticed ocean (water) particles on the surface where the water should appear. It looks like the server and game are fully aware of the chunk and all the blocks in it, the game just has trouble displaying them. It still displays particles (and maybe other things besides blocks?).

@McDodge34 To download the pre5 server you can select the version in a launcher profile and there's a button to download the server. You can also visit the wiki, I'm sure its there.

Why is this set to resolved?

@Sip It's probably been fixed in 1.14.1

@Sip When a bug in this system is set to Resolved, it means that internally they reproduced the bug, made code changes, and tested that the changes correct the issue.  It does not mean the fix is presently available.  Normally the "Fix Version" field shows you which version the fix was included in.  Here, it says "Future Version" which is to say, they haven't created a record in the system for the next version (or named it even).  They are 'stacking up' multiple bug fixes and will release an update with many fixes altogether, this one included.

The bad part is that the new version is 100% broken for so many people due to this bug, that waiting on other fixes hardly seems worth it.  A hot patch would have been more appropriate, instead of waiting for the next minor release, presumably 1.14.1.  Mojang shipped a flat busted product and seems less bothered by it that their customers are.  And that's a shame.

Same problem (minecraft singleplayer, went down from view range of 13 chunks to 10 chunks and still encountered this issue). For me, mob spawning during night seems to be issued as well (hard mode, almost no mobs when running during night) - maybe the same root cause?

There's a different issue related to mob spawning: MC-147890

@violine1101 (or anyone at Mojang)

So where can we get an official update on when 1.14.1 will be available that doesn't include following every Mojang dev on Twitter?  A singular official channel that provides regular updates is needed. The silence is dismissive and to be honest, Mojang employees posting how awesome 1.14 is when so many cannot even play it is excruciatingly tone deaf.  Thanks.

Look at the Fix Version field. It is fixed in an upcoming release of the game. Likely to be in the 1.14.1 patch based on Nathan's (Dinnerbone) comments on Twitter. The issue is not closed, but they have resolved the issue internally in the code base; we just have not received it, because the fix hasn't been released / published, yet.

Chunk loading seems much better in 1.14.1-pre1, even though it's still too slow to fly in full Spectator speed. But chunks still occasionally appear, disappear again and appear again when they are generated and the world often completely disappears when I leave the loaded chunks. Should this report be reopened and edited or should a new one be made?

@unknown If you have a Twitter account, you can just follow this bot: https://twitter.com/mcsnapshotbot
Otherwise you can for example set up followthatpage.com to send you mails on updates of the launcher's version index: https://launchermeta.mojang.com/mc/game/version_manifest.json

1.14.1 prerelease 1 affected (rarely though) video evidence: https://youtu.be/FQwXg7e2j38

Please create a new ticket if you still experience this issue in 1.14.1 Pre-Release 1.

@Violine1101, ok... But don't know why I should make duplication of bug report and maintenance it, when this one have enough upvotes and is watched by over 100 reporters.

Can't we reopen this one? It definitely is still an issue.

As of 1.14.1-pre1 the issue is not nearly as severe as it was before. I doubt the cause is the same too. Besides, this ticket is already cluttered enough. And maybe not everyone who was affected by the issue in 1.14 is affected in 1.14.1-pre1 as well. As I said, please create a new ticket. If you don't want to maintain it, no problem, you don't need to.

Unfortunately it seems to have worsened in 1.14.1 pre-release 1 and the game is even slower.
Since it's a snapshot I want to hope that everything is finally solved with the new official version!

however I put 1.14.1 because it is not possible to put the pre 1 in afflicted versions for now

This issue is not entirely fixed, and 1.14.1-pre1 continues to have significant problems with chunk-loading.

As recommend, I created a new MC-151082 with debug reports and a video demonstration to contribute my findings. I imagine there are several other people doing the same thing.

Hopefully this helps Mojang find and fix the underlying problem for 1.14.1, because otherwise vanilla multiplayer servers will continue to experience game-breaking lag after players load so many chunks.

Why was my comment removed? I asked why this wasn't fixed in QA before and if this fixed the concurrent modification exception. Deleting valid bug related comments like that doesn't help anyone. If you are incapable of doing proper QA yourselves and need paying customers to do QA for you they have a right to ask questions.

Stop it. Please.

edit: This bug still exists, it's just harder to run into. It seems to be related to the 2GB memory limit as it only starts happening once a large amount of world has been rendered and memory is allocated about 100%. Reopen the bug please.

Night and day difference for me between 1.14 and 1.14.1-pre1.  A lot better.  After logging in, take about 2 minutes for all chunks to render.  I can fly without hitting any unrendered chunk when surrounded by land.  In 1.14, I could run into an unrendered chunk.  Oceans still seem to have an issue. I can easily row into an unrendered chunk when by an ocean.

@unknown This is not a forum for discussing the logistics of Mojang's QA process. If you want to discuss those types of things, we have a Reddit community dedicated to those issues, which you can find here. This bug had a large number of off-topic comments that were not relevant to the bug itself, which were removed.

New ticket about this happening in 1.14-pre1: MC-151084

@violine1101 Thanks for linking the new issue, but I think we should split this into at least two separate problems: (1) server-side chunk-loading and (2) client-side rendering issues. The report I created was aimed at (1) the former; perhaps this issue should be re-opened (or another created) to address (2) the latter.

Edit: Looks like MC-151084 was created to more-accurately extend this report (MC-149178), whereas MC-151082 addresses the lag in particular.

Thanks, I didn't notice that. Relinked this ticket to MC-151084.

• Affects Version/s: Minecraft 1.14, Minecraft 1.14.1 Pre-Release 1 

• Fix Version/s: Minecraft 1.14.1 Pre-Release 1

By definition, a bug cannot affect a version and be fixed in that same version.  Which is to say, this bug isn't fixed.  MC-151084 is proof of that.  This record should actually not have been closed since you know, it was never fixed.  God help Mojang is 1.14.1 gets released and chunk loading still isn't fully fixed, customer exodus is all but guaranteed.

I can confirm that the bug has been fixed! That's really nice!

@zenico13 And the masses rejoice 🙂  I can't test until later but many will be quite happy if it is solved for all.  Thanks.

The bug has not been fixed. Chunk loading is still horribly slow in Minecraft 1.14.1.

Please reopen this bug.

Version 1.14-pr5 still has the fastest chunk loading.

For chunk loading issues in 1.14.1 see:

• MC-151082 for server-side issues

• MC-151084 for client-side issues

I'd suggest opening a new bug with all of your own pertinent details because it seems like you may be hitting a different situation. The chunk rendering is back to normal on both of my PCs as of the full 1.14.1 release.