MacraH

Looks correct w/o Optifine. So, who gets the ball (is it something to look at by you all or Optifine, as it was all good up to Forge 1230)?

I've been playing with MC Server using Linux, current Minecraft (MC from here out), Forge version 1.7.10-10.13.2.1230, and the forgeessentials (FE from here out) beta. I got a fresh build of the FE beta and the server would not start as FE had a new requirement for Forge 1.7.10-10.13.2.1258. In order to keep things simple, I upgraded my client (Win 7) and the Linux sever to both have Forge 1.7.10-10.13.2.1258. Synchronicity. When I started up an existing game, all the ore blocks looked either completely black or, if I changed perspective angles, see through to distant lava or built structures. I could break the ore and would get a drop, I had iron ore, coal, and redstone drops in this scenario. I then backed down just the client side to Forge 1.7.10-10.13.2.1230 and the ore blocks looked as expected (no black, no see thru). So, on the client side here are the logs from both runs (the only file with today's date was the file latest.log, no fml-client-latest.log as I was playing a remote game?): latest log for 1.7.10-10.13.2.1230 - http://pastebin.com/1cjmH6QX and it's picture file - https://diaspora.koehn.com/uploads/images/scaled_full_e66fd30079f7b4838382.jpg latest log for 1.7.10-10.13.2.1258 - http://pastebin.com/2aF3kBu0 and it's picture file - https://diaspora.koehn.com/uploads/images/scaled_full_93c7c2fd805277bf3f21.jpg I also have taken copies of the current logs from the server (I'd had it up quite a while today, I had to knock fml-server-latest,log down to the most recent 3000 lines in order to make pastebin happy that I was under the free size limit): fml-server-latest.log - http://pastebin.com/fxDNnqsg latest.log - http://pastebin.com/w9iRK4uB Let me know if you'd like further info.