Me and also among my buddies wished to play some modded Minecraft with each other (1.12.2), and also we mounted a number of mods. Nonetheless, as quickly as my good friend attempts to sign up with any kind of Singleplayer globe, his video game accidents. That"s weird, taking into consideration that we have the very same variation of Forge, the exact same mods (clientside and also not) and also it functions like a beauty for me. I"ve attempted to fix by going through his accident log; as it ends up, all the mods show up to pack with no mistake, however the only (deadly?) mistake I see is "No OpenGL context located in the existing string.", so it shows up that the collision might relate to making, hence I informed him to upgrade his NVIDIA Video Card Drivers, however still the video game collisions upon signing up with a globe. Exists anything I"ve missed out on in the log? Just how can he repair this trouble?
Collision Log: https://pastebin.com/Xxn6HE2h
Web link to commentShare on various other sitesMore sharing choices ...
Published May 24, 2019
Online forum Group
Published May 24, 2019
The filenames of several of your mods recommends you are not obtaining them from main resources, please review my trademark for even more information on why this is a negative point.
This is my Online forum Trademark, I am presently trying to change it right into a tiny overview for taking care of simpler concerns utilizing looter obstructs to maintain points clean.
As one of the most usual concern I feel I need to place this outside the primary mass:
The only authorities resource for Forge is https://files.cardonafam.com.net, and also the only website I rely on for obtaining mods is CurseForge.
If you utilize any kind of website apart from these, please have a look at the StopModReposts job and also mount their internet browser expansion, I would certainly additionally recommend running an infection check.
Logs (Many problems call for logs to detect):
https://gist.github.com/: 100MB Calls for participant (Free)
https://pastebin.com/: 512KB as visitor, 10MB as Pro ($$$)
Minecraft 1.14.4 and also more recent:
Blog post debug.log
Please upgrade ...
Blog post your installer log, discovered in the very same location you ran the installer
This log will certainly be called either installer.log or called the like the installer however with.log on completion
Keep in mind for Windows customers:
When the.log is included the log will certainly show up with the.jar expansion [Windows conceals data expansions by default so the installer might show up without the.jar expansion then [/p>
Mojang Launcher: When making use of the Mojang launcher debug.log is discovered in.minecraft \ logs.
Curse/Overwolf: If you are utilizing menstruation Launcher, their arrangements damage Forge"s log setups, the good news is there is a simpler workaround than I initially assumed, this functions despite Curse"s setup of the Minecraft launcher as long as it is not introduced via Twitch:
See to it you have the proper variation of Forge mounted (some packs are greatly based on one certain develop of Forge)Make a launcher account targeting this variation of Forge.Set the launcher account"s GameDir building to the pack"s circumstances folder (not the circumstances folder, the folder that has the pack"s name on it). Currently release the pack via that account as well as adhere to the "Mojang Launcher" directions over.