Optifine 1.8 and 1.8.1 betas have temporarily messed up Minecraft in way that I don't understand. I usually see at least 200ish fps on my pc (3.4 GHz i7, 8G RAM, GTX780Ti). Optifine 1.8 B2 works fine, but one of the earlier 1.8 versions dropped my fps down to single digits. Minecraft was unplayable. [deleted Fixes 1 through 6 that didn't work]
Fix 7, clear head from nice long sleep, download fresh launcher from Mojang. Victory!
So riddle me this: How does Optifine affect the launcher executable other than creating a new profile (that I deleted last night, BTW)? And why were my 1.7.x versions unaffected?
It doesn't. OptiFine only creates a new profile in which it is loaded as a library.
OK, that's what I thought it did. But why did a fresh launcher fix my fps problem, but fresh 1.8 and 1.8.1 jar files didn't? I'm not complaining, just curious.
You don't. All of these were updated using FML alone. And you can install FML alone, without Forge.
Except for Shader mod. Shader mod alpha is a non-forge version that will likely crash with Forge and/or Optifine. Just read it's release notes. It will probably crash with anything else loaded since it IS an alpha build meant for vanilla testing.
True. The GLSL Shaders mod isn't compatible with OptiFine, Forge, or FML.
Uhhh, it doesn't say roll back in my driver anywhere?
Then that means the old driver was completely uninstalled; hopefully you have the downloaded backup somewhere. If you know the previous driver revision you could simply redownload. Some drivers need to be installed cleanly (this should be habitually observed) to avoid installation anomalies from old drivers.
When I use this mod with some other mods, like BuildCraft, ProjectRed, Wireless Redstone, it makes all the not-full blocks (like repeaters or pipes) invisible. The vanilla blocks are fine, but not those. Does anybody know what the problem could be?
Regarding the new Preview OptiFine B2 for Minecraft 1.8.1 - I was able to test this version of Optifine for around 16 hours (two 8-hour sessions) over the last 2 days with between 2 and 3 players on my own private vanilla 1.8.1 server (I do not use Realms). So far so good, I did not notice any issues. I am more focused on smooth, consistent gameplay versus maximum FPS so I typically set max to 70 or 80FPS and turn off Vsync. With this setup using Optifine 1.8.1 my framerate held rock steady at 80FPS the entire time and I did not experience any noticeable lag. My local player (LAN connection) was also very smooth. The player connected via the Internet experienced some mild lag spikes, but only when traveling on rails and it was mild enough that the game was still very playable. Regarding the lag when traveling on rails/flying for Internet clients, this happens in vanilla MC as well, so it does not appear to be related in any way to Optifine. Interestingly enough, when playing with the 1.7.10 server my Internet client did not experience any noticeable lag even when traveling on rails or flying and even with the maximum server view distance of 15.
For reference, all the computers used for testing were Win7 64-bit, 6GB or more of memory, Java 8 64-bit, Intel Core I5 or I7 CPU and nVidia GPUs of varying types (GTX 650 or above).
The bottom line, for me the new Optifine 1.8.1 appears to be working very well. In my opinion quite a remarkable achievement given the fast release.
In regards to setting up a MCP 1.8.1 , Did you manage to fix the 42 decompile errors in 1.8.1 ? or have an updated conf folder i can drop into MCP 9.10pre1 to lesson the decompile errors ?
DcNdrew, that version of forge is pretty much the latest, it's only 5 versions old, since the newest version of Forge is 10.13.2.1240.
Exactly. If I use 1232, I have great crashes. Well, with 1236 (before 1240) there are lags, and so on. Earlier versions have issues too. 1240 isn't yet.
In regards to setting up a MCP 1.8.1 , Did you manage to fix the 42 decompile errors in 1.8.1 ? or have an updated conf folder i can drop into MCP 9.10pre1 to lesson the decompile errors ?
The decompile errors are trivial to fix - make all classes/fields/methods in net.minecraft.src public.
A proper update of MCP to 1.8.1 will need more work.
I dream of the day when Optifine is finally handed over to whomever runs Minecraft so that it gets placed into the default coding of the game. I cant play without Optifine, but alot of good mods wont run properly with it...A guy can dream.
The problem with Forge 1233 is that the class "net.minecraft.src.FMLRenderAccessLibrary" is now located in the default package when Forge runs. OptiFine looks for it in the "net.minecraft.src" package and does not find it. This seems to be a side effect from upgrading the Forge build process.
I will try to add a workaround for it in the next 1.7.10 version.
The problem with Forge 1233 is that the class "net.minecraft.src.FMLRenderAccessLibrary" is now located in the default package when Forge runs. OptiFine looks for it in the "net.minecraft.src" package and does not find it. This seems to be a side effect from upgrading the Forge build process.
I will try to add a workaround for it in the next 1.7.10 version.
You don't need FML for OptiFine, and no other mods are updated to 1.8, so why don't you just play without Forge installed?
I need Forge for Biomes O' Plenty, shaders mod, Inventory Tweaks, World Handler, and IronChests which all have a 1.8 version.
Which shaders mod?
Oh, oops.
Well, nonetheless, sp614x will release a Forge version of OptiFine when he's finished. There isn't one yet, so this isn't technically a bug.
OK, that's what I thought it did. But why did a fresh launcher fix my fps problem, but fresh 1.8 and 1.8.1 jar files didn't? I'm not complaining, just curious.
Jeff
True. The GLSL Shaders mod isn't compatible with OptiFine, Forge, or FML.
EDIT: As of the alpha 1.8 release.
Then that means the old driver was completely uninstalled; hopefully you have the downloaded backup somewhere. If you know the previous driver revision you could simply redownload. Some drivers need to be installed cleanly (this should be habitually observed) to avoid installation anomalies from old drivers.
In a pervious comment I stated any version of Forge above 1232 causes graphics issues when using optifine.
So downgrade your Forge version to 10.13.2.1232 and you'll be fine.
For reference, all the computers used for testing were Win7 64-bit, 6GB or more of memory, Java 8 64-bit, Intel Core I5 or I7 CPU and nVidia GPUs of varying types (GTX 650 or above).
The bottom line, for me the new Optifine 1.8.1 appears to be working very well. In my opinion quite a remarkable achievement given the fast release.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThat's not good. Some mods are incompatible with older Forges. I can't use even the penultimate version.
In regards to setting up a MCP 1.8.1 , Did you manage to fix the 42 decompile errors in 1.8.1 ? or have an updated conf folder i can drop into MCP 9.10pre1 to lesson the decompile errors ?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumExactly. If I use 1232, I have great crashes. Well, with 1236 (before 1240) there are lags, and so on. Earlier versions have issues too. 1240 isn't yet.
The decompile errors are trivial to fix - make all classes/fields/methods in net.minecraft.src public.
A proper update of MCP to 1.8.1 will need more work.
I will try to add a workaround for it in the next 1.7.10 version.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThank you!
- updated to 1.8.1
Preview OptiFine B1 for Minecraft 1.7.10: Downoload
- fixed Forge fog events
- fixed Forge sound record with custom resource
- fixed Forge custom mob spawning
- compatible with Forge #1240
- fixed CTM configuration with block names