Thanks for the info! To be honest, I think I could give up AA if I really had to considering I went through potentially having to give up either Forge or OptiFine in my search for finding the actual source of the problem.
Another issue I've noticed, which I don't think is related, the "Custom Font" option doesn't seem to work.
As in, setting it to "off" doesn't seem to turn off custom fonts.
I haven't tried it with any pack other than Dokucraft, so it could be related to the resource pack itself, but I figured I'd let you know in case it was actually something to do with OptiFine.
Worse comes to work. I can just delete the font from the pack too, so no worries!
EDIT: Thanks for the update too! Didn't notice it fixed the actual ingame AA issues!
In the words of many before me, "you da real MVP".
The option "Custom fonts" controls which font texture to use, the mcpatcher one or the default one. However the resourcepack can also override the default texture.
Some resourcepacks override the default texture with a simple HD version and put the full HD version in the mcpatcher folder. Other resourcepacks override only the default one.
The Meaning of Life, the Universe, and Everything.
Join Date:
2/25/2015
Posts:
61
Location:
Somewhere in Illinois
Minecraft:
TheSavageHybrid
Member Details
DUDE I LOVE THE MOD!! In fact, I live off of it. But there's just one problem: Since 1.8.3 B1, I've just been crashing constantly. I don't know if it's me, but I'll put down the crash report anyway. This was Optifine 1.8.3 U D3.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007feedd93826, pid=5904, tid=6072
#
# JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ig4icd64.dll+0x43826]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Nate\AppData\Roaming\.minecraft\hs_err_pid5904.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
AL lib: (EE) alc_cleanup: 1 device not closed
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
DUDE I LOVE THE MOD!! In fact, I live off of it. But there's just one problem: Since 1.8.3 B1, I've just been crashing constantly. I don't know if it's me, but I'll put down the crash report anyway. This was Optifine 1.8.3 U D3.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007feedd93826, pid=5904, tid=6072
#
# JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ig4icd64.dll+0x43826]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Nate\AppData\Roaming\.minecraft\hs_err_pid5904.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
AL lib: (EE) alc_cleanup: 1 device not closed
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
Sounds like you need to update your Intel drivers. This is very common with ShadersMod and Intel-based systems.
Any driver version ending in 39XX or 40XX will work just fine.
The new Official MC Launcher sets up its own instance of Java, so it doesn't use/share the system Java.
That version happens to be JRE 1.8 U 25.
Good for me, because I can't update to Java 8 on some of the websites that I use, so Java 7 U 72 is my system-wide java install -- and 8 U 25 is for MC. Works perfect :).
I suppose, I could download the JRE ZIP for 8 U 45, and unpack it into the folder.. But, meh.
I'm still having problems with unplayable turning sensitivity, and changing java version didn't help. My settings are not different, and changing my sensitivity has no effect on the bug. It only happens on Optifine, not vanilla.
The Meaning of Life, the Universe, and Everything.
Join Date:
2/26/2011
Posts:
44
Member Details
Minecraft client crashes right when it's about to enter the main menu. I disable optifine and it works fine. But in game i saw only 40 fps so i depend on this mod
I had to update forge because latest recommended TiC needs it.
- Forge 1.7.10-10.13.3.1389
- Optifine OptiFine_1.7.10_HD_B6 tried and its ultra version. B5 started crashing even before updating Cofh mods that so i didn't even attempt to downgrade.
Minecraft client crashes right when it's about to enter the main menu. I disable optifine and it works fine. But in game i saw only 40 fps so i depend on this mod
I had to update forge because latest recommended TiC needs it.
- Forge 1.7.10-10.13.3.1389
- Optifine OptiFine_1.7.10_HD_B6 tried and its ultra version. B5 started crashing even before updating Cofh mods that so i didn't even attempt to downgrade.
...
OptiFine is not compatible with the very latest versions of Forge, which were released several days ago and added a loading screen.
I have been comparing the way mipmaps work in Optifine 1.8.1 and Optifine 1.8.3 and it seems that something is not right in version 1.8.3. I have included two screenshots below of the exact same scene with the exact same Optifine settings, one image from version 1.8.1 and one from version 1.8.3. In particular, notice the rails. When traveling along rails in version 1.8.3 the rails in the distance are so heavily obscured that they are not recognizable as rails, and when moving diagonally the mipmap blurring shifts back and forth, which results in a very distracting image. These effects are not evident in version 1.8.1.
I did try changing the mipmap levels, however; the smallest level (1) on 1.8.3 is more heavily blurred than the largest level on version 1.8.1 (4). It seems that something significant changed in the rendering with regards to mipmaps. Personally I preferred the 1.8.1 mipmaps. Can you confirm whether this is a bug or if it was changed to work this way intentionally? If it is intentional then I guess I will learn to live with it. I cannot use AF without a severe FPS hit on my current system, so for now that option is not available for me. If you save both images and cycle between them then it really highlights just how significant the differences are between versions with regards to the mipmap settings, especially with rails.
The error comes because the graphics driver is complaining that it has problem to render something.
You can try to:
- update the graphics driver
- use another resource pack
- update the used mods
- disable some of the mods
- turn off some video settings
The error is general so it is hard to say what exactly is broken.
The option "Custom fonts" controls which font texture to use, the mcpatcher one or the default one. However the resourcepack can also override the default texture.
Some resourcepacks override the default texture with a simple HD version and put the full HD version in the mcpatcher folder. Other resourcepacks override only the default one.
When no serious bugs are found.
Question: what's it like being you?
DUDE I LOVE THE MOD!! In fact, I live off of it. But there's just one problem: Since 1.8.3 B1, I've just been crashing constantly. I don't know if it's me, but I'll put down the crash report anyway. This was Optifine 1.8.3 U D3.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007feedd93826, pid=5904, tid=6072
#
# JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ig4icd64.dll+0x43826]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Nate\AppData\Roaming\.minecraft\hs_err_pid5904.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
AL lib: (EE) alc_cleanup: 1 device not closed
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
Thank you for updating OptiFine 1.8.0 HD U D3!
Because I don't know another ingame minimap as VoxelMap for LiteLoader, I'm stying with MC 1.8.0 (no LiteLoader build for MC > 1.8.0 found)
offtopic:
Why JRE 8.0.25? Update to last Java, 8.0.45.
Any fixes for 1.8.4? I get instacrash with the latest builds
Getting a graphical glitch when using OptiFine 1.8.0_HD_U_D3 and Forge 1371. Starting game just blinks and flashes
Older Optifine D2 works like a charm tho.
Video Settings -> Other -> Reset?
Error log?
Sounds like you need to update your Intel drivers. This is very common with ShadersMod and Intel-based systems.
Any driver version ending in 39XX or 40XX will work just fine.
The new Official MC Launcher sets up its own instance of Java, so it doesn't use/share the system Java.
That version happens to be JRE 1.8 U 25.
Good for me, because I can't update to Java 8 on some of the websites that I use, so Java 7 U 72 is my system-wide java install -- and 8 U 25 is for MC. Works perfect :).
I suppose, I could download the JRE ZIP for 8 U 45, and unpack it into the folder.. But, meh.
I'm still having problems with unplayable turning sensitivity, and changing java version didn't help. My settings are not different, and changing my sensitivity has no effect on the bug. It only happens on Optifine, not vanilla.
The thing is... there's no error log. Only in launcher, in Game Output there is:
I'm getting exactly the same look of minecraft 1.8.0 (forge 11.14.1.1375), and my multimc log spams me with
[15:55:17] [Client thread/ERROR]: ########## GL ERROR ##########
[15:55:17] [Client thread/ERROR]: @ Pre render
[15:55:17] [Client thread/ERROR]: 1281: Invalid value
With the latest optifine.
The problem appears to be with the Shaders mod. They work fine separately, but fail to do so together.
Yes, you're right. GLSL ShadersMod v2.4.11
Minecraft client crashes right when it's about to enter the main menu. I disable optifine and it works fine. But in game i saw only 40 fps so i depend on this mod
I had to update forge because latest recommended TiC needs it.
- Forge 1.7.10-10.13.3.1389
- Optifine OptiFine_1.7.10_HD_B6 tried and its ultra version. B5 started crashing even before updating Cofh mods that so i didn't even attempt to downgrade.
Crashlog: http://pastebin.com/bGmWxmjt
Actually this was error i had with forge 1291
"The mod TConstruct (Tinkers' Construct) requires mod versions [Forge@[10.13.3.1384,11.14)] to be available"
edit: Definitely TiC, not Cofh that requires it. I have for now reverted TiC to 1.8.3b.
OptiFine is not compatible with the very latest versions of Forge, which were released several days ago and added a loading screen.
With "almost very latest"
version 1371, Optifine 1.8.0_HD_U_D2 works fine.
Just did a clean reinstall of Windows on a new hard drive,no background programs. It only occurs with optifine.
I have been comparing the way mipmaps work in Optifine 1.8.1 and Optifine 1.8.3 and it seems that something is not right in version 1.8.3. I have included two screenshots below of the exact same scene with the exact same Optifine settings, one image from version 1.8.1 and one from version 1.8.3. In particular, notice the rails. When traveling along rails in version 1.8.3 the rails in the distance are so heavily obscured that they are not recognizable as rails, and when moving diagonally the mipmap blurring shifts back and forth, which results in a very distracting image. These effects are not evident in version 1.8.1.
I did try changing the mipmap levels, however; the smallest level (1) on 1.8.3 is more heavily blurred than the largest level on version 1.8.1 (4). It seems that something significant changed in the rendering with regards to mipmaps. Personally I preferred the 1.8.1 mipmaps. Can you confirm whether this is a bug or if it was changed to work this way intentionally? If it is intentional then I guess I will learn to live with it. I cannot use AF without a severe FPS hit on my current system, so for now that option is not available for me. If you save both images and cycle between them then it really highlights just how significant the differences are between versions with regards to the mipmap settings, especially with rails.
Thanks for all your hard work on Optifine!