Adam V

Just an update for anyone who is concerned. It seems that my Minecraft realms functionality has been restored, although I'm not entirely sure how or why. The only thing I have done in the past week that was Minecraft related was just playing a single player world for about thirty minutes. Perhaps this error was remedied by playing single-player, an update that was personally experienced on my PC, or it is just dumb luck that It was fixed through the passing of many months. 

Alright. Thank you for trying to help me. I appreciated it. 👍

Where is the link supposed to take me? The official Minecraft website?

It still cannot be reached. Is there another link I can use?

Oops. I thought I copied and pasted it. Thanks for catching that. 

When I try to use the link, pc.realms.minecreaft.net in the search bar it says the site cannot be reached. I tried removing and then giving chrome access through windows defender, but the web site won't load through the link in step #1. 

Ok, I see that. It only says "Use bundled Java runtime," 

I do not believe I am using a custom Java Runtime. How would I be able to check? 

I am still having this problem. I am currently in 15.2 and cannot get into the realms menu.

Confirmed 1.10, Had a village spawn with 4 farmer huts and a church. Occupants were 2 librarians and a priest.

I've found the best solution (for me anyways) so far. I was reading a bit about 1.9 on the minecraft website and it says they're aware of massive graphical glitches such as this one and the AMD one. It suggested to turn VBO's on, Vsync on, Mipmap levels to off and turn the render distance to something under 16. This has worked for me, I only see the unloaded chunks rarely, usually when travelling somewhere I haven't been before. I also find the unloaded chunks are just a straight line of them, instead of the usual where some chunks are and some aren't loaded.

Not only that, but it's decreased my memory usage a ton and increased my average fps from 15ish (slow computer 😛) to 25ish.

@unknown I know it was a bug since coal blocks can smelt 80 items, (800 seconds of fuel, according to the wiki). I smelted 72 gold ore and as you can see from the pictures, the fuel didn't go down.

The only steps I can give is what I did:

I put the full 72 ore into a hopper connected to the furnace, let it fill to 64.
I put one coal block in the fuel slot and let it cook.
I took 40 finished gold ingots out when they were finished and let the rest finish.

The fuel level never went down during this, however the one on the other furnace did, and I did the exact same thing for it, except I had something like 250 ore and 3 coal blocks

Is it a visual glitch tho? I've been able to cycle my difficulty (Locked at hard from world gen) and it still gives the whole blurb about locking the difficulty when I click the button.

I haven't actually played on any other difficulty to see if there was a difference and I haven't cycled to peaceful (In fear some of my named hostile mobs would despawn)

Also, confirmed 1.9.4

@unknown But it would seem to be a bug, since many players (although apparently not that many) had no problem in 1.8.9, but do in 1.9+. So many of us are having pretty much the exact same issue, at the exact same interval in the version history.

Unless some of the additions from 1.8.9 to 1.9.4 have put something of a strain on the rendering? Because some of my friends with beefed up computers seem to have no problem.

All I know is this 'issue' is beyond irritating, makes exploring or really anything requiring movement of more than 5 chunks near impossible, even when just walking in a straight line as I have tried doing with my distance on 2 chunks... I always run into the invisible chunks.

I'm just hoping to get a solid answer, even if it means getting a better computer etc. I've been searching for something that works and so far, nothing.

**EDIT: What's funny, actually, is I don't seem to get this glitch in the Nether, nor the End.

If you're playing on anything other than the windows phone version, it won't be fixed yet.

All the device are still in 0.11.1 build x except for the windows version. Once they release 0.12 it should be fixed though.

Same issue, IPad 2 on version 0.11.2