"We can never be sure if bending space around time is the right approach until we get feedback from you on the 14w29b snapshot that bends time around space instead. We do that by using the newly implemented threaded render batch system. That’s a lot a fancy sounding words, so if you don’t know what that means, it should improve performance even more. Or crash horribly. But without your feedback, we’ll never know which one is true." (mojang.com)
It crashes horribly.
What keeps happening is that in 14w29b, a world I upgraded from 14w26b to 29b kept having invisible chunks, then I try to load them (F3+A) and the game just crashes :/. Note: I did upgrade it to 27b, 28b, 29a and then 29b (after it started to keep crashing).
Linked issues
Attachments
Comments 8
I hope this is a fancy way of saying, "we changed stuff, let us know what broke."
In 14w29b There is massive block lag:
-When breaking crops (wheat, pumpkins, etc) and blocks, it shows as still there although it does drop as an invisible entity that can be picked up. After a few seconds, the block will disappear and the entity will be visible (if not already picked up.)
-When placing blocks, there is similar lag in that the entity is invisible but can be interacted with ie placing cobblestone, you can't see it for a few seconds, but it has a hitbox so you can't walk through it but you can stand on it. Torches are similar except you can see the flame particles and it takes a few seconds for the lighting update.
-Fence gates and doors also lag and can be walked through after opening them, but take a second to display as being open.
This is more pronounced the longer the game has been running or when exploring new areas. This does not happen with 14w29a or earlier snapshots.
14w29b
Win7 x64 SP1
JRE 7u60 x64
"14w29b crash" is a bit too less information for a diagnosis.
Incomplete without a crash report from ([minecraft/crash-reports/crash-<DATE>-client.txt|http://hopper.minecraft.net/help/finding-minecraft-data-folder]). Please attach it so that we can diagnose your issue.
Broken Intel drivers, see MC-14051
The crash doesn't show up in the log for some reason ...