Search results
7 sty 2010 · Downgrading drivers or using a dedicated GPU are still the only solutions that I've been able to find; the only other clue is that it appears to only affect release 1.0.0-1.7.10, but not newer or older versions, suggesting that there is something unique to these versions, but nobody has attempted to find/try to fix it (as far as I can find ...
- Forge 1.7.10 doesn't work anymore...? - Minecraft Forum
For whatever reason, adding Forge to 1.7.10 now causes the...
- Minecraft forge 1.7.10 not working - Java Edition Support - Support ...
I read somewhere that Java 1.8.0 isn't working with forge at...
- Forge 1.7.10 doesn't work anymore...? - Minecraft Forum
7 sty 2010 · For whatever reason, adding Forge to 1.7.10 now causes the game to take a fatal error and crash. This has occurred on multiple computers, without any further modification yet. Installing and running vanilla Minecraft 1.7.10: It works fine.
23 maj 2021 · I need to use Forge for Minecraft 1.7.10. I have launched it through the launcher and to see if the vanilla version works and it does. Next, I download the recommended files for Forge 1.7.10. I hit open with the Java SE Binary platform and the download says successfully downloaded.
7 sty 2010 · I read somewhere that Java 1.8.0 isn't working with forge at the moment. I use JRE 7 And it works Flawlessly.
22 maj 2018 · This was solved by updating AMD chipset drivers, Forge now launches and game runs without any further problems. Fresh install Forge 1.19.4 45.3.0 - exit code 1 By ImRatherMinty · Posted 9 hours ago
The first step is to download and install forge. Make sure you select "install" and not Universal. After installing, completely close and re-run your launcher. Installed versions are only cataloged when it starts up. Next, create a new profile for your 1.7.10 game. Also, make sure you use a dedicated folder just for 1.7.10.
20 kwi 2021 · I tried that setting and it either doesn't work too, or something else is the root cause. We also tried injecting a patched libglfw but it hasn't help either. Unsure if there is a path forward with this still or if the only option is to just upgrade to 1.20.2+.