The shadow can break and repeat under specific conditions, not related to the resource pack (or .mcmeta files).
The issue seems to be related to the location of the item frame with the compass in it, and where you throw an item. It can be reproduce in a new world:
Steps to reproduce:
Use default resource pack (or any other)
Switch to fancy graphics (GL ERROR won't show up at fast graphics)
make a new creative mode/superflat world or use the attached world MC-18752.zip
do the command /tp @p 0 5 0
middle click grass, place one
get an item frame and compass from creative inventory
place item frame then compass
## GL ERROR ## : @ Post render 1281: Invalid valuewill throw in the dev consolewhile looking at it, throw something on the ground near it
Affects AMD Catalyst 13.12:
OpenGL: AMD Radeon HD 6700 Series GL version 4.3.12618 Compatibility Profile Context 13.251.0.0, ATI Technologies Inc.
Also affects nVidia GTS 450, NVIDIA Driver Version: 319.32, NV-CONTROL Version 1.29, GL version 4.3.0.
Minecraft / OpenGL / LWJGL gets messed up after that, the shadow effect will affect other worlds too until Minecraft gets restarted, or until resource system is reloaded (such as f3+t or changing resource packs).
Related issues
is duplicated by
Attachments
Comments
migrated
kumasasa
Please force a crash by pressing F3 + C for 10 seconds while ingame and attach the crash report here.
Ok, crash report uploaded. Also, deleting 3rd picture as that wasn't uploaded by me. EDIT: I take that back, it won't let me because you are considered the owner. Someone else uploaded mcissue1.png.
kumasasa
Please update your graphics drivers, current ver is 319.23: http://www.nvidia.com/object/linux-display-amd64-319.23-driver.html
kumasasa
Please check your Java installation:
Crash report: 1.7.0_21
Environment: 1.6.0_27
Do you really think that is the cause of the issue? (even still, wouldn't Mojang want to support more drivers than freshly released?)
I am on the latest version considered "stable" by Ubuntu developers. Even Steam only wants 310.14 (which is still called "experimental beta" within the packages).
I've had nVidia drivers on windows (hit-and-miss), so I really don't feel like installing something that has only had minimal testing by nVidia that could potentially wreck my system and have to reinstall everything (I've made my own script, but still).
If Steam games are happy with my drivers, Minecraft definitely should be, too. I would at-most upgrade to 310.14 if I really needed to, at least it probably has some testing by members of the community.
Ok, removed Java 7 (Minecraft doesn't seem to want to use it anyways) now just using Java 6. Error still occurs, re-triggered and re-uploaded crash report.
Erik Broes
We need some way to properly reproduce this because I seem not to be able to.
Ok, so this apparently seems to be an issue with the world, some rare edge case. It used to happen in my world, but now it doesn't. I found a backup version of the world, and the error still happens, even in the 1.6 pre-release.
I have uploaded a .ZIP of both worlds so you can hopefully find out what is causing the issue.
I have also uploaded a screenshot of where the error usually occurs, and as you can tell it has quite a few different things, that in combination, could cause the error.
Ezekiel
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Still happens in 1.7.4 (uploaded screenshot of it happening) with attached world (error_happens.zip). I hadn't answered because I personally don't have the issue anymore, although it seems it still exists.
I'm not sure what causes it, but I've uploaded 2 versions of the same world, one where it happens, and one where it doesn't. It should allow someone to find out what the cause is.
Wow, thanks, that is indeed the cause of the GL error which messes up shadows!
I was able to not only fix it in the world that it was happening in with the compass (as well as re-create it), I was able to cause the issue in a newer version of the world in which was no longer affected by the bug!
What I'm not sure of though, is exactly how to reproduce it other than the compass. As I said I was able to reproduce it in a newer version of the world (with different blocks and items in the item frames), but it didn't happen immediately. I tried it a few times, and it was working fine. After a while, I tried it again in another position, and may have stumbled across the true cause....
It only happens near the center of the Z axis! I was able to 100% reproduce this by making a new superflat world, /tp @p 0 5 0, and then making a compass in an item frame!
Is this possibly related to another axis/early chunk bug?
Also, Kumasasa if I may ask, what is your hardware/OS setup?
kumasasa
@all: Sorry for the flood of edits, but the ticket was turned inside out...
But finally there are perfect steps to reproduce that issue.
Does this still happen in bleeding-edge snapshots e.g. 14w26b?
kumasasa
No, don't get this with 14w27b anymore (AMD Catalyst 14.6-rc).
Seems fixed on my end as well (14w27b, Linux, Nvidia driver version 337.25).