Here's your answer (taken from the OptiFine Discords FAQ)
Q: Why isn't OptiFine working on Forge 1.13+?
A: OptiFine was updated long before Forge had any version available for Minecraft 1.13+. For the time being, OptiFine is NOT compatible with Forge 1.13. See this GitHub issue for more details: https://github.com/sp614x/optifine/issues/2148
Here's your answer (taken from the OptiFine Discords FAQ)
Q: Why isn't OptiFine working on Forge 1.13+?
A: OptiFine was updated long before Forge had any version available for Minecraft 1.13+. For the time being, OptiFine is NOT compatible with Forge 1.13. See this GitHub issue for more details: https://github.com/sp614x/optifine/issues/2148
Thanks for posting this. Allot of people don't have or use discord. I wouldn't have looked in discord for that kind of update. I normally come here to the forums.
Please excuse if this double posts. Using moble first time and had to reload in middle of this post. Not showing progress done. Thx.
Given the state that 1.14 has arrived in I am not surprised that the modding community is dragging its feet to embrace the new version.
There are strong indications that there are significant structural and design issues with 1.14 that were not adequately addressed during snapshotting, allowing a full release to arrive with issues that would normally have been squashed during early testing. Mojang seem to have been a little too willing to dismiss many tickets on bugs.minecraft.net as 'edge cases' and this has allowed a release to arrive with broken mechanics.
This goes beyond bugs. A bug is a malfunctioning piece of code, but I suspect 1.14 contains entirely flawed mechanics that will yield terrible results no matter how well it's coded, and then there are bugs in those terrible mechanics. I am increasingly worried that even if every bad piece of code was resolved tomorrow there would still remain fundamental mechanics that are hopelessly broken.
If a physical product was sold with sort of structural and design issues that 1.14 has it would be recalled, and I feel that we're approaching that point: Mojang need to honestly evaluate the situation and say "1.14 is not ready... we need to go back to the snapshot process and rework some of these mechanics. We'll see you in three months with version 1.15"
I have been playing since the 1.5 release. By 1.8 I was deeply interested in technical Minecraft and redstone machines, but the irony of the situation today is that you avoid redstone wherever possible. Need to send a signal? Use powered rail, it costs fewer clock cycles. Got a naked hopper? Cram a dropper on top to reduce its overhead. There are mob farm designs I built in 1.8 and 1.9 that I would never even consider on 1.14 because of the insane overhead they would generate.
I have found lately that I am using mob AI mechanics for mob farms as more dynamic and productive farms come with too much server lag (let alone needing Optifine near any water flushing farm).
SciCraft are sticking with 1.12 because 1.13 and 1.14 would annihilate their performance. Despite 1.14 having impressive levels of threading (compared to previous releases) it is the worst performing release. If I have to choose between new content and working redstone... well, redstone wins every time.
One light on the horizon are the very public issues Hermitcraft are experiencing with 1.14... With some front-line youtubers in direct contact with the devs we might finally see some real action from Mojang, rather than these frustrating half measures. I just wish that Mojang would pull their finger out and get around to actually communicating the scope of the issue with the community.
I used Optifine to use dynamic lighting and to disable particles
I am sad now
1.13.2 mod with forge doesnt load it says the jar file isnt a mod file i would reallt love to have optifine back as it gets rid of screen tears
Here's your answer (taken from the OptiFine Discords FAQ)
Q: Why isn't OptiFine working on Forge 1.13+?
A: OptiFine was updated long before Forge had any version available for Minecraft 1.13+. For the time being, OptiFine is NOT compatible with Forge 1.13. See this GitHub issue for more details: https://github.com/sp614x/optifine/issues/2148
http://www.johnsmithlegacy.co.uk/ - John Smith Legacy for Minecraft
Thanks for posting this. Allot of people don't have or use discord. I wouldn't have looked in discord for that kind of update. I normally come here to the forums.
Please excuse if this double posts. Using moble first time and had to reload in middle of this post. Not showing progress done. Thx.
Read what you just wrote...
"OptiFine 1.14 HD U F1 pre2" is now listed as download.
Preview version looks like it's working pretty good, but not updated to 1.14.1 yet, hopefully that won't be a big deal to implement.
"the update to 1.14 will continue as planned, and 1.14.1 will come after." from their Reddit page.
What do we do now that this forum is dead?
Given the state that 1.14 has arrived in I am not surprised that the modding community is dragging its feet to embrace the new version.
There are strong indications that there are significant structural and design issues with 1.14 that were not adequately addressed during snapshotting, allowing a full release to arrive with issues that would normally have been squashed during early testing. Mojang seem to have been a little too willing to dismiss many tickets on bugs.minecraft.net as 'edge cases' and this has allowed a release to arrive with broken mechanics.
This goes beyond bugs. A bug is a malfunctioning piece of code, but I suspect 1.14 contains entirely flawed mechanics that will yield terrible results no matter how well it's coded, and then there are bugs in those terrible mechanics. I am increasingly worried that even if every bad piece of code was resolved tomorrow there would still remain fundamental mechanics that are hopelessly broken.
If a physical product was sold with sort of structural and design issues that 1.14 has it would be recalled, and I feel that we're approaching that point: Mojang need to honestly evaluate the situation and say "1.14 is not ready... we need to go back to the snapshot process and rework some of these mechanics. We'll see you in three months with version 1.15"
I have been playing since the 1.5 release. By 1.8 I was deeply interested in technical Minecraft and redstone machines, but the irony of the situation today is that you avoid redstone wherever possible. Need to send a signal? Use powered rail, it costs fewer clock cycles. Got a naked hopper? Cram a dropper on top to reduce its overhead. There are mob farm designs I built in 1.8 and 1.9 that I would never even consider on 1.14 because of the insane overhead they would generate.
I have found lately that I am using mob AI mechanics for mob farms as more dynamic and productive farms come with too much server lag (let alone needing Optifine near any water flushing farm).
SciCraft are sticking with 1.12 because 1.13 and 1.14 would annihilate their performance. Despite 1.14 having impressive levels of threading (compared to previous releases) it is the worst performing release. If I have to choose between new content and working redstone... well, redstone wins every time.
One light on the horizon are the very public issues Hermitcraft are experiencing with 1.14... With some front-line youtubers in direct contact with the devs we might finally see some real action from Mojang, rather than these frustrating half measures. I just wish that Mojang would pull their finger out and get around to actually communicating the scope of the issue with the community.
Just wondering if there are any plans for making OptiFine compatable with Fabric?