Have you tried playing around with the graphics settings like 'fast' and 'fancy' to see if the problem is there on all of them or only on a particular setting?
im on 1.8.1 and I havent had this dark glitch you guys are talking about but I would like to see this for myself so what do youi do for it to turn dark? or does it just do that randomly? If so I cant help because I dont have this problem. Also dont download Optifine I dont have it and thats just a waste of your time to download.
Yes older worlds are reported to have this problem, new ones do not. Destroying them and placing them again may fix the problem, if it doesn't it's strange but still an old world problem.
Nope. I get the same problem on alpha worlds as I do on 1.8/ 1.9 worlds.
I've had this problem since 1.8, but only with chests. Signs work fine. Replacing the chests or surrounding torches doesn't do anything; it even flickers in low light levels.
Rollback Post to RevisionRollBack
"Some scientists claim that hydrogen, because it is so plentiful, is the basic building block of the universe. I dispute that. I say that there is more stupidity than hydrogen, and that is the basic building block of the universe." -Frank Zappa
it happens to me all the time it is annoying! try backing up your save of world then delete your minecraft re download it then put world back in + = :angry.gif:
So has the conclusion so far been that this is not reproducible on computers on which it is not already occurring? That does seem to indicate a driver or hardware bug, likely triggered by some changes that went into minecraft in recently.
I have only ever seen this when updating an older world to the pre-release, and then the issue is always resolved by changing the lighting - removing and re-placing a torch near the object. I've never seen this issue come up in new worlds, nor have I seen it resurface once addressed in old worlds.
That bites, It's been occurring with me on chest and even signs. But if it's a problem on players end due to the changes in the lighting system I guess there's nothing much they can do about it.
Just waiting for Forge to officially release for 1.13.x to remove unneeded mobs from 1.13, like Phantoms, from the game because, in my gameplay based opinion, they add nothing of value to the game.
Fun fact: Clicking a bed every 30 minutes doesn't make you a better player, it makes you one who clicks a bed every 30 minutes. Wouldn't you rather just mod them out of the game completely?
I've never had this problem with a fresh world, only with bringing 1.8 worlds into 1.9. Jeb has disregarded it as no one is able to show a fresh 1.9 world doing it. If someone does, he will reopen the report.
Sorry for poke in the wrong direction earlier, all you make it seem like some hardware doesn't have, or doesn't properly implement, an OpenGL extension that Minecraft now uses for lighting, perhaps relating to the double texture layering that the light now uses. If that's the case it would be very hard to fix because it would require a total rewrite on how the new lighting system works on a fundamental level. What would be nice is being able to switch back to the old smooth lighting. Perhaps a mod could be made to do such a thing, and have it become an unofficial patch.
In my experience, this has to do with integrated graphics. I've seen Minecraft 1.8 run on 4 different PCs, this only happened on the the two laptops with integrated graphics. Both My computer and the other with a stand alone GPUs (1 with AMD and the other nVidia) haven't seen anything like it, with the exception of repeaters and paintings. That's just me though.
That's funny... considering I'm running an entirely AMD/ATI system, happens a lot to me. It happens almost everytime I place a picture.
That happens to everyone and is fixed in the pre-release. Also, AMD/ATI is known to have problems with OpenGL (look at complaints with Rage). The difference between EA and Mojang should be obvious, being an indie developer Mojang doesn't have as many people or as many resources (including testing computers) to find rare isolated problems early on, and completely redoing the lighting engine this late in development and this close to release isn't something ANY company can do. They're fixing the lighting bugs everyone has (stairs, paintings, and soon repeaters) as best they can. However, some people have problems on hardware level that deals with the fundamentals of how the lighting system works which wasn't known at the time because, like I said, they don't have a whole room of computers with different setups to test it on. Sadly, you can't please everyone.
As many of you know, there is a very annoying chest/sign lighting glitch happening since 1.8 for some users. This also occurs with hands. Jeb apparently cannot reproduce this, due to his graphics card, and has disregarded it as a fake glitch.
This needs to be fixed! I hate using chests and signs because of this! (it happens all the time) Heres some screenshots to show you what i mean:
For those who are still watching this I think I found the problem. Minecraft uses OpenGL 1.2, and has since it's creation. This makes it compatible with most operating systems and graphics hardware built by 1998, a desirable trait. However, recently Minecraft has started to use functions from OpenGL 1.2.1, a slightly older version (released in the same year). The functions used are Multi-Texturing extensions, which in this case is used for the lighting engine. The hardware in question that is having problems are probably old cards or chips built in early 1998 that doesn't support, or doesn't properly support OpenGL 1.2.1 and/or it's Multi-Texturing OpenGL extension.
Anyone who is experiencing problems with lighting on a permanent level (do say anything about old maps, repeaters, paintings, or stairs, those are normal) please report their graphics hardware. If what I said is true then you all may be out of luck, because the new extension is a fundamental part of the new lighting system and can not simply be patched. The only way to fix this is to have a toggle for the old lighting system. It may sound mean to say this, but you're lucky this game works for your computer thus far. If what I said about the problem is true, then your computer is 13 years old and can no longer be accounted for when producing games, or else what can be done to improve the game diminished greatly.
If what I said about the problem is true, then your computer is 13 years old and can no longer be accounted for when producing games, or else what can be done to improve the game diminished greatly.
Not true, I have the issue on one computer I use (chests, mobs, and the player's hand all flicker black frequently), and this is a semi-recent setup - Radeon X1950 Pro, 64-bit, Quad-Core.
Edit: Just checked which OpenGL version I have - it's 2.0
My brother has this issue sometimes. Changing the lighting settings fixes it for him.
Nope. I get the same problem on alpha worlds as I do on 1.8/ 1.9 worlds.
What's your point?
Just waiting for Forge to officially release for 1.13.x to remove unneeded mobs from 1.13, like Phantoms, from the game because, in my gameplay based opinion, they add nothing of value to the game.
Fun fact: Clicking a bed every 30 minutes doesn't make you a better player, it makes you one who clicks a bed every 30 minutes. Wouldn't you rather just mod them out of the game completely?
I've never had this problem with a fresh world, only with bringing 1.8 worlds into 1.9. Jeb has disregarded it as no one is able to show a fresh 1.9 world doing it. If someone does, he will reopen the report.
That happens to everyone and is fixed in the pre-release. Also, AMD/ATI is known to have problems with OpenGL (look at complaints with Rage). The difference between EA and Mojang should be obvious, being an indie developer Mojang doesn't have as many people or as many resources (including testing computers) to find rare isolated problems early on, and completely redoing the lighting engine this late in development and this close to release isn't something ANY company can do. They're fixing the lighting bugs everyone has (stairs, paintings, and soon repeaters) as best they can. However, some people have problems on hardware level that deals with the fundamentals of how the lighting system works which wasn't known at the time because, like I said, they don't have a whole room of computers with different setups to test it on. Sadly, you can't please everyone.
Placing a torch nearby helps abit
You didn't give an opinion?
I have the same problem, on a new gen world.. It goes away if you move closer to the item though? (hard to explain exactly)
Anyone who is experiencing problems with lighting on a permanent level (do say anything about old maps, repeaters, paintings, or stairs, those are normal) please report their graphics hardware. If what I said is true then you all may be out of luck, because the new extension is a fundamental part of the new lighting system and can not simply be patched. The only way to fix this is to have a toggle for the old lighting system. It may sound mean to say this, but you're lucky this game works for your computer thus far. If what I said about the problem is true, then your computer is 13 years old and can no longer be accounted for when producing games, or else what can be done to improve the game diminished greatly.
Edit: Just checked which OpenGL version I have - it's 2.0