Inscriber name plate resulting in game crash
bkbarbee opened this issue ยท 6 comments
- Minecraft Version: 1.12.2
- AE2 Version: rv5-stable-11
- Forge Version: 1.12.2 - 14.23.3.2655
So what I was doing was I had an Inscriber attached to my network, and a name plate already in it. It was not the name plate I wanted, but I went ahead and shift-clicked my Interface and other name plate into it. As the Inscriber began working (I assume using the top name plate) I shift-clicked the top nameplate out of the Inscriber, and the game crashed. I tried to reload my save, and the game crashed again. Unfortunately, I was unable to find the log for the first crash, but in the link below is the complete log from startup to crash when attempting to load the old save.
I was able to replicate the bug exactly as it happened the first time in a brand new game. The setup was simply a creative energy cell sitting beside a single controller, which had about 3 Dense ME Cables - Blue running directly into the Inscriber. I made two name plates, got an Interface (block version), and shift-clicked in the order of plate 1, Interface, and plate 2 in, and then plate 1 out. After about a second's time (I do not know if it was frozen or not), the game crashed. Below is the complete log.
EDIT: The bug has also once again made the world completely unplayable, crashing upon startup. That is really quite a pain considering I had a nice little world before hand. Poots.
Can you please post only the actual crash log? Scrolling through the full game log is a pain
Crash replicated perfectly once again, but this time with only AE installed. Once again, the save is dead. Below is the log, but only the crash report portion this time (sorry about that).
Possible duplicate of #3476 ?
At least the Erroring line and SourceFile are the same.
well not directly related but i would suggest to start the world without inventory tweaks and optifine jsut for a simple test
i do not get a grip while the grid update is running when a crafting recipe is done but i want to rule out other mod interactions first and all logs contained it and there were knwon issues in the longer past