How can this work as intended ? If there shouldnt be any Sugar Cane inside "cold" biomes why do they spawn there ? Why do Saplings and Wool appear anywhere in the World ?
OpenGL: AMD Radeon R9 200 Series GL version 4.4.12874 Compatibility Profile Context 14.100.0.0, ATI Technologies Inc.
Visual output: http://puu.sh/b4yOL/a01337ebc7.jpg
This flashed and changes when i move around. This happend after i changed my Render distance inside the Client from 8 to 32
I play with VBO on and 4 GB Ram and when i turn the Viewdistance to 32 Chunks the Bug is gone. But the memory usage is huge. I mean huge (2x-3x as in 1.7). And i don't think that a by default disabled VBO is the real solution for this (either it gets turned on by default on AMD/ATI or the real Bug gets fixed).
This affects all sorts of servers. And since the code directly shows that you exclude all servers (except the featured ones) makes me believe that there was a intention to break this for non featured servers? i don't understand why this exception is in place and when asked if this is a bug or not its just simply stated as invalid even though it clearly isn't.
This check in the packet handler was not there in 1.5 betas and lower versions. Why is it in there now?
Fabian Faßbender
MC-40365
MCPE-16450
How can this work as intended ? If there shouldnt be any Sugar Cane inside "cold" biomes why do they spawn there ? Why do Saplings and Wool appear anywhere in the World ?
OpenGL: AMD Radeon R9 200 Series GL version 4.4.12874 Compatibility Profile Context 14.100.0.0, ATI Technologies Inc.
Visual output: http://puu.sh/b4yOL/a01337ebc7.jpg
This flashed and changes when i move around. This happend after i changed my Render distance inside the Client from 8 to 32
The 1.8 release Version also has this. Why is this released when it Bugs on most AMD/ATI Cards ? I don't get this.
I play with VBO on and 4 GB Ram and when i turn the Viewdistance to 32 Chunks the Bug is gone. But the memory usage is huge. I mean huge (2x-3x as in 1.7). And i don't think that a by default disabled VBO is the real solution for this (either it gets turned on by default on AMD/ATI or the real Bug gets fixed).
This affects all sorts of servers. And since the code directly shows that you exclude all servers (except the featured ones) makes me believe that there was a intention to break this for non featured servers? i don't understand why this exception is in place and when asked if this is a bug or not its just simply stated as invalid even though it clearly isn't.
This check in the packet handler was not there in 1.5 betas and lower versions. Why is it in there now?