Crash while checking crafting status over ME Network Bridge
JoJoDeveloping opened this issue ยท 8 comments
I wanted to auto-craft something over the ME Network bridge, which did not work (the window closed itself). I then wanted to check what is being crafted. The "craftiong status window" showed up for a fractrion of a second and then MC crashed and told me that "A fatal error occurred, this connection is terminated".
Stack trace / Crash log:
http://pastebin.com/YtMLMSBw
Please keep in mind that the method in which the crash happened, "func_75142_b", is "detectAndSendChanges"
AE2 Version: rv3-beta-6
Forge version: 1.7.10-10.13.4.1614 (latest)
No, in a galacticraft world. Btw it only happens occasionally, e.g. it works when using a wireless terminal (the extracells one), and if I use it first the bug does not occur when using a terminal.
Well it happened to me in an rftools dimension and I also can't autocraft anything from inside the rftools dimension
I had a similar problem, with the GUI closing when trying to auto-craft. But my client didn't crash. I narrowed it down to the method of chunkloading the QNB's. First I was loading them with FTBUtils (the chunk claiming/loading window thingy). After switching to chunkloader / spotloader (Chickenchunks), the problem seemed to have been fixed.
[edit] Actually, I did crash once now. Also, the chunk loading apparently didn't solve the problem. This is just a bug in something to do with the QNB's.
Chickenchunks are no good solution, they tend to cause chunk unload/reload loops and half loaded chunks! switch to MFR Chunkloaders or Railcraft Chunkloaders, thrust me on that :)
or did he fixe those bugs recently (i mean in the past two weeks, since i know the latest version still doing this funky stuff until then)
I also had that problem. After lots of testing, finally found out, that if you have something in this inventory slot and try auto-craft, you receive this error.
