Amir Kolic

It says Fixed In Version: 14w34b and it still happens in 1.8pre3 😛

Confirmed For 1.8pre3! 😞 For me this glitch happened when i created a new world and VBOs was on and Render Distance was 2 chunks for some reason.When i would change VBOs to Off and go anything above 2 chunks the glitch was shown.However when i was at 2 chunks the glitch didn't apear.To test this a generated a new world with VBOs=On and Render Distance 4.I tried every render distance(from 2 to 16 chunks for me) and the glitch did not apear.However when i turned VBOs=Off.Every render distance over 5 chunks with show the glitch.I did a 3rd test to prove this theory.I made a world with VBOs=On and Render Distance=8.With VBOs=On every Render Distance worked.When i turned VBOs off the glitch would be shown every render distance over 5 chunks(like in test 2).So it seems that when i turn off VBOs and my render distance is over 5 chunks the glitch apears.This might be because the VBOs doesn't work as wanted with AMD/ATI.This glitch should be a priority to fix as it is photosensive, or untill it is fixed there should be a way to warn people with photosensive epilapsy!