-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Neodymium Crash #47
Comments
Does it still happen if you add the By the way, you don't need Neodymium to fix the Intel rendering issue, you can also use CoreTweaks which fixes it more comprehensively. |
Hm, that looks the same. I managed to reproduce your crash now by changing my render distance to 32 and enabling Advanced OpenGL. And the same thing happens without Neodymium. So I suspect that this is not actually a Neodymium issue, and just an issue with your configuration. (Maybe before adding Neodymium, you had OptiFine which allows higher distances?) If that is indeed the case, you could remedy the situation by adding OptiFine (it is compatible with Neodymium). ArchaicFix also has an option to allow high render distances, but it's not compatible with FastCraft. By the way, I'd recommend turning off Advanced OpenGL because it tends to cause bad performance, but Neodymium should warn you about that once in-game anyway. |
To fix my rendering issue with GTNewHorizons, I was told to download Neodymium but after i got Neodymium game started crashing.
I think the issue is related to CoFHCore so posting both of their versions:
neodymium-1.7.10-0.2.2+nomixin
CoFHCore-[1.7.10]3.1.4-329
fml-client-latest.txt
The text was updated successfully, but these errors were encountered: