While this is a pretty minor issue, I really need it fixed. I'm working on a PvP map and in one room of the map, and the one room alone, there is a single chunk that goes invisible when standing on the edge of its neighboring chunk. I'm currently on snapshot 16w44a. While the bug was discovered on multiplayer, it still happens when the world is played in singleplayer. I've tried to use a program to fix corrupt chunks and regions with no luck and have messed with vanilla minecraft's limited video settings (how did I live without optifine?) once again with no luck. This also does not happen if I fly outside of the room even when in the same place.
Screenshots:
I also recorded a video of the bug:
If you need any more info, please let me know. Thanks!
Just loaded the world in 1.10.2, first without Optifine and then with. When I loaded it without optifine the exact same issue happened. However, when I loaded the world in 1.10.2 with Optifine, the issue was gone! So Optifine should fix it once 1.11 is fully released and we get a new version, though it still would be nice to have it fixed for people who don't use it...
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
While this is a pretty minor issue, I really need it fixed. I'm working on a PvP map and in one room of the map, and the one room alone, there is a single chunk that goes invisible when standing on the edge of its neighboring chunk. I'm currently on snapshot 16w44a. While the bug was discovered on multiplayer, it still happens when the world is played in singleplayer. I've tried to use a program to fix corrupt chunks and regions with no luck and have messed with vanilla minecraft's limited video settings (how did I live without optifine?) once again with no luck. This also does not happen if I fly outside of the room even when in the same place.
Screenshots:
I also recorded a video of the bug:
If you need any more info, please let me know. Thanks!
Just loaded the world in 1.10.2, first without Optifine and then with. When I loaded it without optifine the exact same issue happened. However, when I loaded the world in 1.10.2 with Optifine, the issue was gone! So Optifine should fix it once 1.11 is fully released and we get a new version, though it still would be nice to have it fixed for people who don't use it...