all of the mods are in the crash report, just not a description of what's causing the tesselating error.
I get these crashes ALL the time. it generally happens in Buildcraft's leftover quarry holes though, or in people's bases. it does not just happen in the middle of nowhere. if i crash, restart my game, log back in, and then keep looking in the same direction, i crash again within a few seconds. i honestly have no clue what is happening, because the crash report doesn't report what caused the crash, besides a tesselating error. i am the only one on the server that gets these crashes, and it's driving me up the wall. i'm not sure if it's driver related. if it's optifine, i have no clue what setting to change. however, i cannot run the modpack without optifine due to such low framerate.
To further clarify, the "Already Tesselating!" is one of those messages that occur when the game's Tessellator (part of rendering) is put into an illegal state. This specific one means that something is wanting to start rendering a face before another part of the game has finished rendering.
To further clarify, the "Already Tesselating!" is one of those messages that occur when the game's Tessellator (part of rendering) is put into an illegal state. This specific one means that something is wanting to start rendering a face before another part of the game has finished rendering.
i figured as much, i just didn't know what's causing it. correct me if i'm wrong, but it could have something to do with multi-threading/parallel-ization. i have since removed optifine and haven't noticed the problem, but FastCraft isn't as good as optifine in my mind.
Hm... I haven't really thought of that. I suppose if you had two separate threads both trying to run code to render at the same time then they might interfere with each other. But it would have to be extremely unlikely.
I don't think there is much multithreading going on between different rendering jobs, just separating rendering form other stuff.
first off, here's the crash report:
http://pastebin.com/RCEete8k
and here's my optifine settings:
http://pastebin.com/yndN99zd
all of the mods are in the crash report, just not a description of what's causing the tesselating error.
I get these crashes ALL the time. it generally happens in Buildcraft's leftover quarry holes though, or in people's bases. it does not just happen in the middle of nowhere. if i crash, restart my game, log back in, and then keep looking in the same direction, i crash again within a few seconds. i honestly have no clue what is happening, because the crash report doesn't report what caused the crash, besides a tesselating error. i am the only one on the server that gets these crashes, and it's driving me up the wall. i'm not sure if it's driver related. if it's optifine, i have no clue what setting to change. however, i cannot run the modpack without optifine due to such low framerate.
all help is appreciated, thanks.
To further clarify, the "Already Tesselating!" is one of those messages that occur when the game's Tessellator (part of rendering) is put into an illegal state. This specific one means that something is wanting to start rendering a face before another part of the game has finished rendering.
Start Tessellating -> ... code... -> Start Tessellating -> Error "Already Tessellating!"
So this is very likely a problem with Optifiine clashing with another mod's rendering code.
Sounds about right. I suppose he could try updating that.
I remember having trouble with it before in a modpack, and installing a newer version fixed helped.
well, if it is cofh core, i wouldn't be able to update it until an update for the modpack is released, but i can talk to the owner about it.
i figured as much, i just didn't know what's causing it. correct me if i'm wrong, but it could have something to do with multi-threading/parallel-ization. i have since removed optifine and haven't noticed the problem, but FastCraft isn't as good as optifine in my mind.
Hm... I haven't really thought of that. I suppose if you had two separate threads both trying to run code to render at the same time then they might interfere with each other. But it would have to be extremely unlikely.
I don't think there is much multithreading going on between different rendering jobs, just separating rendering form other stuff.