2

Regardless of when I crash, it's always the same console message that I see.

2013-07-02 08:14:32 [INFO] [STDERR] java.lang.ArrayIndexOutOfBoundsException: -1 
2013-07-02 08:14:32 [INFO] [STDERR] at ic2.core.block.BlockMultiID.d(BlockMultiID.java:59)
2013-07-02 08:14:32 [INFO] [STDERR] at ConnectedTextures.isNeighbour(ConnectedTextures.java:663) 
2013-07-02 08:14:32 [INFO] [STDERR] at ConnectedTextures.getConnectedTextureVertical(ConnectedTextures.java:750) 
2013-07-02 08:14:32 [INFO] [STDERR] at ConnectedTextures.getConnectedTexture(ConnectedTextures.java:265) 
2013-07-02 08:14:32 [INFO] [STDERR] at ConnectedTextures.getConnectedTexture(ConnectedTextures.java:198) 
2013-07-02 08:14:32 [INFO] [STDERR] at ConnectedTextures.getConnectedTexture(ConnectedTextures.java:154) 
2013-07-02 08:14:32 [INFO] [STDERR] at bbb.k(RenderBlocks.java:2993)
2013-07-02 08:14:32 [INFO] [STDERR] at bbb.b(RenderBlocks.java:7858)
2013-07-02 08:14:32 [INFO] [STDERR] at WorldRendererThreaded.updateRenderer(WorldRendererThreaded.java:158) 
2013-07-02 08:14:32 [INFO] [STDERR] at WrUpdateThread.run(WrUpdateThread.java:116) 
2013-07-02 08:14:32 [INFO] [STDERR] java.lang.IllegalStateException: Already tesselating! 
2013-07-02 08:14:32 [INFO] [STDERR] at baz.b(Tessellator.java:504) 
2013-07-02 08:14:32 [INFO] [STDERR] at baz.b(Tessellator.java:494) 
2013-07-02 08:14:32 [INFO] [STDERR] at WorldRendererThreaded.updateRenderer(WorldRendererThreaded.java:128) 
2013-07-02 08:14:32 [INFO] [STDERR] at WrUpdateThread.run(WrUpdateThread.java:116) 
2013-07-02 08:14:34 [INFO] [STDERR] java.lang.IllegalStateException: Already tesselating! 
2013-07-02 08:14:34 [INFO] [STDERR] at baz.b(Tessellator.java:504) 
2013-07-02 08:14:34 [INFO] [STDERR] at baz.b(Tessellator.java:494) 
2013-07-02 08:14:34 [INFO] [STDERR] at azr.a(EffectRenderer.java:139) 
2013-07-02 08:14:34 [INFO] [STDERR] at ban.a(EntityRenderer.java:1592)
2013-07-02 08:14:34 [INFO] [STDERR] at ban.b(EntityRenderer.java:1117)
2013-07-02 08:14:34 [INFO] [STDERR] at net.minecraft.client.Minecraft.J(Minecraft.java:884) 
2013-07-02 08:14:34 [INFO] [STDERR] at net.minecraft.client.Minecraft.run(Minecraft.java:773)
2013-07-02 08:14:34 [INFO] [STDERR] at java.lang.Thread.run(Unknown Source) 
2013-07-02 08:14:44 [INFO] [STDOUT] Stopping! 
2013-07-02 08:14:45 [INFO] [STDOUT] SoundSystem shutting down... 
2013-07-02 08:14:45 [INFO] [STDOUT] Author: Paul Lamb, www.paulscode.com

closed as off-topic by galacticninja, Robotnik, 5pike, Studoku, Mathias711 May 28 '15 at 10:47

  • This question does not appear to be about videogames or videogame consoles within the scope defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • Latest graphics drivers and Java version? – tombull89 Jul 2 '13 at 12:22
  • I tried to format this into a spoiler and couldnt get it to work, so I made it as easy on the eyes as possible. My apologies. – Ender Jul 2 '13 at 12:25
  • 1
    @FEichinger well I'm playing FTB, so yea there is a lot of mods, but... they are supposed to play nicely with eachother... – Ender Jul 2 '13 at 12:33
  • 3
    @Ender Select everything, then click on the {} icon (preformatted text). Easier than indenting every line manually by four spaces :-7 After all the site's enginge stems from the programmer's stackoverflow.com. See gaming.stackexchange.com/editing-help#code – Zommuter Jul 2 '13 at 12:33
  • 5
    This is a known issue with the Industrial Craft 2 mod. as shown here bt.industrial-craft.net/view.php?id=295. I suggest turning off connected textures (thats part of the issue) or updating ic2, or removing ic2 completely. – RhysW Jul 2 '13 at 13:26
5

I found the same issue as yourself here on the IndustrialCraft 2 bug page.

You can tell it is an IC2 issue because of line 2 of the error saying ic2.core.block

Some other mods, FTB included, also use the core part of the IC2 mod, which might explain why some people will get the issue without knowingly installing the full IndustrialCraft mod.

What I can gather from this is that the version of IC2 isn't able to properly map connected textures with a certain block type, which is why your issue appears intermittent yet always the same.

I suggest doing a combination of the following:

  • Disable connecting textures
  • Update to a later version of IC2 if one exists
  • Disable IC2 and see if this stops the issue
  • Thanks for making your comment properly an answer! Here's a +1 to start the ball rolling. – SevenSidedDie Jul 2 '13 at 15:33

Not the answer you're looking for? Browse other questions tagged or ask your own question.