crash with nei about projectred HOT 8 CLOSED

Seconded, Whenever you view certain items in NEI it crashes the game.

from projectred.

the posted crash log is for Optifine. don't use it.

If you still are getting the crash, then u don't have the right mods installed.

from projectred.

I have the same problem

http://pastebin.com/5LH8UfR5

from projectred.

Then you should use the same solution: Don't use Optifine. That was posted literally directly above your comment, not to mention on every other page of the forums.

from projectred.

I understand it. But why does all other mods work perfectly with optifine? Gameplay is too slowly without optifine. I think that problem will be founded and fixed. Crashreports is the first step. I'll test and will try to help project some way.

from projectred.

It's not "this mod" that is throwing errors. Technically it's Optifine itself, but as you mentioned many other mods are fine. The reason this one is not is that it uses Forge Multipart now, which makes Optifine freak out because multipart blocks no longer have a single brightness value.

I have tried looking into this myself as I'm sure many others have, but the only viable solution is to either not use optifine or not use a Forge Multipart compliant mod such as this. Feel free to try and troubleshoot it yourself as well, but I would suggest you add your comments to one of the existing posts about this on Forge's forum, as that is much closer to the problem at hand.

from projectred.

Interesting fact: lastBrightness fields come not from Minecraft, but from Forge, and by @Chicken-Bones request: MinecraftForge/MinecraftForge#406. To be honest, I don't really like it myself, but I can't judge because I don't know if he had any other way to solve his problem.

For some reason, Optifine removes them. Why? Is it such a major performance issue? I don't know. But, since they are included in Forge, I see it as incomplete Optifine compatibility with Forge.

If it's the only issue that causes errors with Optifine, I think you should ask Optifine developers to revert removal of those fields.

from projectred.

It was indeed a necessity for correct rendering. I you read the comments on
the PR you referenced, I explain it better there. There is also no
performance impact, most likely options debs just overlooked it

from projectred.