This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
FunshineX's profile picture

[1.3.3][SSP] Crash with latest Forge

Started by FunshineX, 15 July 2012 - 11:12 PM
FunshineX #1
Posted 16 July 2012 - 01:12 AM
In an attempt to upgrade my other mods I am required to update forge. This appears to break ComputerCraft. The game loads fine but receives Saving Chunks when loading or creating a world.

The error is as follows:

Minecraft Forge 3.3.8.152
FML v2.2.78.153

— BEGIN ERROR REPORT 7e360f10 ——–
Generated 7/15/12 5:07 PM

Minecraft: Minecraft 1.2.5
OS: Windows 7 (amd64) version 6.1
Java: 1.7.0_03, Oracle Corporation
VM: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
LWJGL: 2.8.3
OpenGL: Quadro FX 770M/PCI/SSE2 version 3.1 NVIDIA 189.92, NVIDIA Corporation

java.lang.NullPointerException
at ModTextureAnimation.a(ModTextureAnimation.java:119)
at aaw.a(RenderEngine.java:628)
at cpw.mods.fml.client.FMLClientHandler.registerTextureOverrides(FMLClientHandler.java:741)
at cpw.mods.fml.client.FMLClientHandler.loadTextures(FMLClientHandler.java:860)
at cpw.mods.fml.client.FMLClientHandler.onWorldLoadTick(FMLClientHandler.java:267)
at net.minecraft.client.Minecraft.a(Minecraft.java:2140)
at net.minecraft.client.Minecraft.a(Minecraft.java:2032)
at net.minecraft.client.Minecraft.a(Minecraft.java:1949)
at mw.c(SourceFile:171)
at iz.a(SourceFile:220)
at if.a(SourceFile:150)
at mw.a(SourceFile:192)
at lr.b(EntityRenderer.java:1083)
at net.minecraft.client.Minecraft.x(Minecraft.java:873)
at net.minecraft.client.Minecraft.run(Minecraft.java:750)
at java.lang.Thread.run(Unknown Source)
— END ERROR REPORT dd8eea82 ———-
MysticT #2
Posted 16 July 2012 - 01:19 AM
It doesn't seem to be a ComputerCraft error. I have the latest forge and CC runs fine. Try reinstalling forge, and see if it works without mods, then add CC and test again.
FunshineX #3
Posted 16 July 2012 - 01:26 AM
If I load without CC folder, world loads fine. If I load with CC folder, I get that error. However I'm following a lead that it could be caused by Optifine. Testing that now.

Yep it was Optifine. Upgraded to C3 and the error no longer occurs