Note.notepad
it was a rendering screen error.
Posts by ADVENTUREUPDATE
-
-
note:i got it fixed but ars magica items tab makes this
http://pastebin.com/i5cpnLPr -
Crash logs are always needed when you have a crash. Otherwise the devs will not know what's the error. However, ForgeModLoader-0 logs are preferred over crash logs.
To solve: update all your mods.
If that doesn't work, try removing mods one by one, EXCEPT IC2, until you remove the one that does not make it crash. Then tell the author of the mod (that when removed, does not crash) to update IC2 API.
Additionally delete all the ic2/api/ folders in all your mods. This will make them less likely to crash when updating to a new IC2, but that will make the mods require IC2 to run.all i got to say about that is....thats just insanity in my world because i dont know which mods i need updated and i got aton of mods so how do i know whats which to be updated if they are outdated
-
well i dont wanna say much about this so im gonna keep this short and sentenced ic2 when i install it it crashes when i uninstall it no crash
if you really want crashy the crash log then.
http://pastebin.com/NzEt15kV -
yeah but what if you delete them and you find when it works and you re-add it to see if it works again... Confused Much?
It's never a good idea to paste the crash
ingreport directly or upload to mediafire. Use http://pastebin.com/ and give us the link instead.Your problem is that one of your mods is using an outdated IC2 API and is packaging the outdated one also. To solve, either:
- Update all the mods. E.g. Forestry, MFR, PowerSuits, Tinker's Construct and MPSA are outdated.
- Delete all the /ic2/api folders in every mod file EXCEPT IC2. Note that this will make all those mods require IC2 though.
- If that doesn't work, try removing the mods one by one until you remove the one that makes it not crash. Then bug the mod author for that mod about it.
