Render Crash with IC2 BlockCuttingMachine placed on QuarzGlass #2689

Closed
Cakestory opened this Issue Dec 7, 2016 · 0 comments

Projects

None yet

2 participants

@Cakestory

Description

All client´s near the chunk with the BlockCuttingMachine crash immediatly after login on the server. The crash was caused by a player placing a BlockCuttingMachine from Industrialcraft 2 on QuarzGlass from Applied Energistics 2. Reading through the crash report I found that it is caused by a failing BlockProperty request where one block tries to get the material of the other. Looking through the AE2 code on the lines mentioned in the crash report, it seems to be caused by QuarzGlass requesting an invalid MaterialProperty from the IC2 machine.
As I do not have access to the IC2 code and only a medium knowledge of Java it could be on IC2´s side to fix this issue. If so please tell me and I will post the issue on their bug tracker.

Crash Report

crash-2016-12-06_19.58.23-client.txt
or
http://pastebin.com/KAEhW6XK

Environment

  • On a multiplayer server with custom private modpack and multiple player´s
  • Crash occured first time when IC2 machine got placed, since then crash occures every time a player logs in and is loading the chunk the machine is in
  • There should be no rendering adjusting mods installed (e.g. tested with and without Optifine installed)

Versions

  • Minecraft Version: 1.10.2
  • AE2 Version: rv4.alpha build 8
  • Forge Version: 12.18.2.2171
@yueh yueh closed this in a2b20f1 Dec 8, 2016
@yueh yueh added the type-bug label Dec 8, 2016
@yueh yueh added this to the rv4 beta - 1.10 milestone Dec 8, 2016
@phit phit added a commit to Stonebound/Applied-Energistics-2 that referenced this issue Dec 19, 2016
@yueh @phit yueh + phit Fixes #2689: Do not pass our own blockstate to the adjacent block. eb83127
@phit phit added a commit to Stonebound/Applied-Energistics-2 that referenced this issue Dec 19, 2016
@yueh @phit yueh + phit Fixes #2689: Do not pass our own blockstate to the adjacent block. 9be4acd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment