I kid you not...
While making an experimental modpack I have the game (1.7.10 (vanilla launcher)) create a new world.
Wait for a time that makes me wonder if it has not froze, yet the log scrolls on. (game shows the dirt background)
After a brief flash (too fast to read) of two small lines of text, game enters the world, then...
I would have to agree with scarycreepa: Regardless of whichever other mods you are using, ChromatiCraft is the mod throwing the error. It seems that ChromatiCraft is trying to either multi-thread (which seems to be disallowed by your build or configuration), OR perhaps there is a separate mod that is trying to do generator actions at the same time as ChromatiCraft.
I too suggest that you pull ChromatiCraft to see if it has any further issues. If either of my speculations are correct then, perhaps there is a setting (or group of settings) which may be altered. Furthermore, deactivation of all other world generators, may be a troubleshooting angle to take... run it that way with ChromatiCraft active, and see if the problem recurs. From there, you will have to determine your next, preferential step.
Also, it appears that MrTJP Core appears to be throwing the 1st error. That is perhaps, the first thing you may want to deactivate to compare against ChromatiCraft.
I am not willing to pull Chromaticraft or any other Reika Mod, for the entire suite (excepting Legacy) is the base of this pack.
I have seen this error before... several times
Previously, the remedy was to delete mods in the ".../mods/1.7.10" directory and then reinstall via Curse's modpack builder app.
I later learned that the MC(?)/Forge(?) Dependency loader did this on it's own.
But now... at the end of the first alpha candidate, the above remedy no longer works.
Curiously still...
I *did* successfully build a world, let it "percolate" for several hours (stability testing), messed around...
Saved...
Re-entered...
Messed around some more...
HOLY!!! It's repeatable!!!
Until the next mornings reboot.
Now, my tricks have all been exhausted <sigh>
Does this only happen when you are creating a world, when you are re-entering a previously created world, or both/either? Furthermore, removing ChromatiCraft was not the only troubleshooting method offered...
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI kid you not...
While making an experimental modpack I have the game (1.7.10 (vanilla launcher)) create a new world.
Wait for a time that makes me wonder if it has not froze, yet the log scrolls on. (game shows the dirt background)
After a brief flash (too fast to read) of two small lines of text, game enters the world, then...
Multi-Crash 1
30 seconds of the world rendering in game, then dirt or black background with...
Multi-Crash 2
(and maybe) Multi-Crash 3 is very similar, maybe identical to 2nd crash report and appears to be irrelevant.
Latest Log
Looks like Chromaticraft is causing a problem. Try deleting it and see what happens.
If you want a quicker reply from me then be sure to hit the
Reply button.
I would have to agree with scarycreepa: Regardless of whichever other mods you are using, ChromatiCraft is the mod throwing the error. It seems that ChromatiCraft is trying to either multi-thread (which seems to be disallowed by your build or configuration), OR perhaps there is a separate mod that is trying to do generator actions at the same time as ChromatiCraft.
I too suggest that you pull ChromatiCraft to see if it has any further issues. If either of my speculations are correct then, perhaps there is a setting (or group of settings) which may be altered. Furthermore, deactivation of all other world generators, may be a troubleshooting angle to take... run it that way with ChromatiCraft active, and see if the problem recurs. From there, you will have to determine your next, preferential step.
Good luck!
Also, it appears that MrTJP Core appears to be throwing the 1st error. That is perhaps, the first thing you may want to deactivate to compare against ChromatiCraft.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumClarification(s)
I am not willing to pull Chromaticraft or any other Reika Mod, for the entire suite (excepting Legacy) is the base of this pack.
I have seen this error before... several times
Previously, the remedy was to delete mods in the ".../mods/1.7.10" directory and then reinstall via Curse's modpack builder app.
I later learned that the MC(?)/Forge(?) Dependency loader did this on it's own.
But now... at the end of the first alpha candidate, the above remedy no longer works.
Curiously still...
I *did* successfully build a world, let it "percolate" for several hours (stability testing), messed around...
Saved...
Re-entered...
Messed around some more...
HOLY!!! It's repeatable!!!
Until the next mornings reboot.
Now, my tricks have all been exhausted <sigh>
Does this only happen when you are creating a world, when you are re-entering a previously created world, or both/either? Furthermore, removing ChromatiCraft was not the only troubleshooting method offered...