Did you try turning off some of the graphical options to see if it makes any difference. If it does, it could give us some clues on what is happening here. For now, if you ring up the debug text, you will know what you are mining. The button to press is [.]. The period / full stop key.
Any update? I get the similar results on all C++ builds so far. In fact it, so consistently I’d thought it was due to the “dev” build nature of the servers, until my son tried on a windows machine. The render was so different at first I thought he’d respawned to a different biome… silly me.
We’ve been hacking away at the OS X rendering issues over the past couple of months. We’ve not forgotten them!! We’re working on them.
However, it’s proving difficult to track down as we’ve not replicated the issue with our Macs. This makes diagnosing the issue(s) and fixing it pretty random. We’ve even considered switching from OpenGL to Metal on OSX to get onto something that Apple is supporting.
We’ve also started thinking about a bigger change that would hopefully simplify the shaders and improve performance for all the platforms. (Tech: switching the voxel rendering from an atlas technique to a texture array technique.)
We appreciate that it’s frustrating that you’ve bought a game that doesn’t render correctly - but have confidence that we’re working on it and we’ll get there in the end!
Thanks @james. I appreciate it can be difficult. My personal suspicion is that it has to do with the newer OSX and the Intel HD 5000 configuration. but I haven’t made any forays into actually debugging the issue.
I also completely understand @james. It takes time to fix bugs.
I first noticed this issue right around the time that world regeneration was implemented for the first time in the worlds just before this wipe. I logged in for a couple minutes and just thought everything was snowy, and didn’t think much of it because I didn’t play for quite a while. I checked through my screenshots (because I regularly take pictures of interesting things I find) and this issue first occurred for me on May 12th. It was fine before then, so I think the Intel 5000 series chip just didn’t like some minor change. It’s weird.