Multi Colored Terrain Bug

This bug must be fixed as it also happens on my Samsung Galaxy Tab 4 7.0 🙂

Mojang I also have a Samsung Galaxy Tab 3 lite and thinking that would solve the problem formatted my tablet, please fix the bug as soon as possible!

guys i also have the same problem ,

I have made a report ... 'GRAPHICAL ERROR: a dark ring around the player'

guys we got to make these 2 reports popular so the developers look at the issues ,i have voted and i am watching this report, pls do the same with this report and my report so we can stop the problem with our samsung devices!! THANKS GUYS!!!

yes I too get the weird colours and the long round black shadow! - samsung sm-t230 guiscale 4

This might be the far lands..

My Got the same effect Samsung Galaxy Tab 4 7.0

This graphics glitch has occurred on versions 0.14.99.0 and 0.14.99.2.....
For me, it has occurred on one of three android devices. The device affected is the Samsung galaxy tab 3.7 (sm-t210)
The other two unaffected devices are Samsung galaxy S5 and Asus ZENPAD Z170C-PO1Z
(Can't seem to attach images but this issue is really noticeable on quartz blocks......They go from white to 'rainbow multi coloured')

Still affects beta build 2

Appear to be fixed in beta build 3

Has the same effect on my Samsung Galaxy S4, dark ring around the player

But it wasn't fixed in beta build 3

Still in 0.15.0 Beta build 3 according to duplicate MCPE-15250

As much as I can tell this doesn't affect my device anymore. Still may affect others.

Just installed the latest version and the graphics error is no longer apparent on my sm-t210.
Cheers for sorting it Mojang.....

This bug is in 0.15.0 for my Nexus 6.
for 0.14.2-0.15.0b3, I would get polka-dots. Now I get the shapes of all the blocks, however as described are all black. Anything enchanted is just a square with the enchanting pattern rolling over it.
This happens in all worlds (new and old), creative or survival. No mods, I tried to de-install, reinstall.
If I take my worlds and put them on my Pixel C, I do not see any issues with the worlds generated under the Nexus 6.
I can post a screenshot if needed, but this issue here is exactly what I am now seeing (well, since 0.14.2).
https://bugs.mojang.com/browse/MCPE-11285

I can confirmed that this affects 0.15.1
with B&N nook tablet HD 4
some of the items on the inventory are black
the game is almost unplayable

I can't play Minecraft anymore. Because of that dark landscape. Can't even fix it. Ugh

I have the exact same problem on mu Samsung tab 3. The landscape is way to dark and there is a ring of light around the player.

I have a similar problem cept mine is like a black crossword puzzle with tin items like gold swords and such

I forgot how to show a attachment but im MCPE- 15566 take a look

It´s the same on a Samsung S4 Mini I9192, like the guys on MCPE-15419. 0.14.x versions did not exhibit this behavior at all.

I have the same issue using Android 4.4.2 on my Samsung tablet. My son had it on his at first, but after he bought and installed the Plastic Texture Pack it was no longer happening. My guess is it's something to do with the default Texture Pack not rendering correctly at a distance of more than 16? blocks from the player.

I hade this issue too my mobile Motorola Droid Maxx with 4.4.4 Kit Kat My sister has Samsung Galaxy J5 his Game is Fine but why i am getting this issue @Minecraft_Dev's Need to fix it 🙂
i have mcpe 0.15.0.1 App

Fixed for me in 0.15.1 on Android 4.4.2.

Happens less frequently with 0.15.1.2, however it can still happen to me 2/3 times.
I will say that I have not seen the BLACK any longer, only the funny colors as is posted in:
https://bugs.mojang.com/browse/MCPE-14509
Check Screenshot_2016-05-29-12-19-41.png
(as of this post, it is the top-most right-most image in the above Jira Issue)
Still on Nexus 6 running Verizon's version of Android 5.1. Still do not see issues on my Pixel C.

We've tried Plastic as @Master TMO said... the resource pack is quite interesting, but unfortunately, the same blackness/shadow effect occurs from 7 or 8 blocks ahead and on.

Will check that 0.15.1... but was thinking IF maybe I try the 0.14.3 resources folder as a resource pack. I remember reading some pic+tweet from some Mojang dev about a Samsung Tab not liking his new shaders.

When i updated to 0.15.1 it also fixed for me

What I see is Pixelated, not Black.

The game is unplayable as it is. 😞

What more do I need to provide to help get this confirmed so it can be worked on? I have three devices with 0.15.1.2 installed. My Pixel C has no issue, nor does my Nvidia Shield. My Nexus 6 has all sorts of issues with this. I don't really see "black" as everyone else seems to. What I see is more Pixelated looking. This is with a FRESH install with deleting the /game folder.
Nexus 6, running Verizon Android 5.1

Refer to Screenshot_2016-07-06-16-18-21 and Screenshot_2016-07-06-16-18-34

Thanks!

Finally worked out 100% workaround which might shed light on the issue.
EACH time I clean load the game on my Nexus 6, the game shows the field as indicated above.
What I mean by clean, is swiped out of the recents menu.
To eliminate the issue, all I need to do is go into the Manage button for Textures, then add OR remove 1 texture. I can go back in and add the same thing back in later, but the trick appears to be to trigger the texture mappings to be reloaded. After that, I get 100% perfect MCPE play on my Nexus 6. I hope this helps to indicate the issue.

Please respond and add the current version if you can reproduce this issue.

@AMAN4700
0.15.6.
If I use a LAN server, the issue does NOT appear.
Toggle "No-Particles" texture pack, that appears to resolve this 100% of the time.
Toggle meaning, if the texture pack is loaded at game start, unload. If unloaded, load.

There might be other texture packs that work, but this one is the one that I am referring to throughout this post.
http://mcpedl.com/no-particles/

Steps:
*start game
*click play
*worlds tab
*create new world --or-- load an existing world
*see pixelated world
*push back button
*Quit to Title
------Resolution--------
*Options
*Manage (textures)
*If the No-Particles Texture Pack is loaded, unload
**If the No-Particles Texture Pack is unloaded, load
*click play
*worlds tab
*create new world --or-- load an existing world
*see correct world

It seems just forcing the game to go through the action of whatever the No-Particles Texture Pack is...corrects the issue. This also works with other texture packs loaded. For instance, if I use the CodeCrafted Texture pack, WITH the No-Particles, I can get the CodeCrafted loaded and working (again, needing to toggle the No-Particles as described above). NOTE: I have not fully tested this, but I have always kept the No-Particles texture pack on the TOP, when using other texture packs with this "resolution" method. Doing this seems to work, but i have to do this EVERY time I load the game, unless I choose a LAN game. I have not tried realms or any internet based servers at this time.

Reopened per @unknown's comment.

Please reply and update affected versions if you're still able to reproduce this issue.

0.15.10 still affected.

Management Level Summary:
*when using ONLY 0.16 worlds in the worlds folder, the issue seems resolved
*when using pre-0.16 worlds, other issues crop up, however the video bug is also present - in a different form
*the issue does NOT require a texture pack to work around any longer
*the issue only happens at the FIRST load of the FIRST pre-0.16 world, after that, the issue does not come back until next reboot of my phone (see below notes regarding loading MCPE a second time with pre-0.16 worlds in the game folder)
*after the first load of the first pre-0.16 world, the above issue seems resolved until next reboot of the phone.

0.16 update:
If I start with ANY newly generated 0.16 world. everything appears to be 100% resolved
If I load up an older world, the first time I open it, it is all buggered up, as in with the above issues.
After closing this world and re-opening, 10/10 times, this world is perfectly fine.
Closing, swiping away MCPE, then re-opening and loading the same -already once opened world repeats the process. The first time I open the world, the graphics are broken. After that, I do not have a problem. The MAJOR difference between 0.16 and previous versions that contained this issue, is I do NOT need to introduce a texture pack to correct this. Please see above post regarding No Particles TP. I only need to open the game, load the world, exit the world, re-load the same world.

If I then open a SECOND world, AFTER the above process, that world loads perfectly fine - without the need to quit the world and re-load. It seems that ONLY the FIRST time a non 0.16 world is loaded, do I have to exit the world and jump back in. After that, everything is fine and as noted, I do not need to play around with the No Particles texture pack in order to get my world to not be bugging out.

This happens to me on EACH world that was not generated in 0.16. 0.16 worlds appear to be 100% (as stated above).

I have opened a second ticket, with 0.16, if I have ANY pre-0.16 worlds in the worlds folder, the game crashes upon open, except the FIRST time that it is opened after a reboot. If I delete all my pre-0.16 worlds, the game functions perfectly fine. https://bugs.mojang.com/browse/MCPE-17553

Same with my bro on his Lg L65

tried with 17.1 and 17.2. Issue seems to still be present. However, it is much easier to clear things up. Now I only need to enter a world (any), then exit the world. After that, re-enter any world and as long as I do not exit Minecraft, everything stays perfectly fine. It it still annoying that I have to enter and exit, then re-enter. This drastically hinders my efforts creating mods or playing games - as I have to enter and exit often, so I end up entering worlds many times. At least it is now easier to clear up - vs what I used to have to do with the no particles texture pack.

--Another confirmation of the bug in 0,17.0.2: https://redd.it/5er3x2 .--

--Occurred on a Motorola MotoG3, Adreno 306, running Android 6.0 (Marshmallow).--

EDIT: Turns out that was a different bug... whoops!

Please reply and update affected versions if you're still able to reproduce this issue.

I am using 1.1.1.51 without any issues at this time. Sorry I was not able to keep up with testing, life got in the way.
I am ok with this being closed and will re-open the issue later if I have further problems.

Resolving as fixed, if anyone can still repro this bug, please let us know and we'll reopen the ticket.

It still exists in the released 1.14 update on iOS

@Dave B. that looks like a different issue to me. In your screenshot, a texture from another block (blast furnace) is being applied to the wrong block.