Jump to content

BlueKingMuch

Members
  • Posts

    7
  • Joined

  • Last visited

  • Days Won

    1

BlueKingMuch last won the day on October 2 2019

BlueKingMuch had the most liked content!

BlueKingMuch's Achievements

Dirt

Dirt (1/9)

2

Reputation

  1. Because you don't use the latest version, in your modpack you use 5.0.39, which also works for me. Could you do me a favor and also test with 5.1.51 EnderIO? (together with EnderCore 0.5.69)
  2. I just tested it - works fine. maybe because you also just have updated it i've one question: how did you solve? i've maybe a similar issue with my modpack. Do you use EnderIO? because the latest one won't work with technic launcher.
  3. please see this thread: try out the suggested solutions.
  4. there should be also a crash report with a decently smaller filesize. Try to open the launcher, go to the modpack that crashes and click to the small gear "Modpack Options", then a new window shows up where in the first line there should be an "OPEN" button. click on it. Then a new window will appear with the files of your modpack. Look for the folder called "crash -eports", double click, and search for the latest one. upload it to us so we can further help.
  5. it seems that the file you download is actually not only an installer, but also the runtime itself. you could create a new folder in C:/Program Files/anyname and put the launcher in it, then right click and "Send to Desktop", or put the Launcher directly on the desktop.
  6. [B#472] java.lang.IllegalStateException: GLFW error 65542: WGL: The driver does not appear to support OpenGL The crash report gives an hint: maybe during the update from 8 to 10, the graphics driver went gone. Try to download the latest one and install, then restart and try again!
  7. Hello! I've recognized a strange behaviour of the technic launcher when I tried to update my other modpack with the latest EnderIO & Endercore. It seems that something in the mod has changed, so the technic launcher has it's problem with it. to prevent strange inter-mod behaviour, i created a modpack with only forge ( 14.23.5.2838 ) and the 2 mods: EnderIO (5.1.51) & EnderCore ( 1.12.2-0.5.69 ). Before anyone declares this as an modpack issue: it isn't. it is working fine on other launchers: Technic Launcher: crash (java.lang.NoSuchFieldError: ELYTRA) Original Minecraft Lancher: runs new Minecraft Launcher: runs MultiMC: runs The test pack i've created can be found here: https://www.technicpack.net/modpack/bkm-testpack.1544969 The log of the launcher (with the crash during startup of the modpack) can be found here: https://hastebin.com/tafuyezuyi.coffeescript The crash report is here: https://hastebin.com/wimomegixo.pl How to fix? Thanks! BR, Michael Bigger Edit: In the Meantime i contacted the Mod Authors. In their last update they included a check for a class which should load early: static { if (com.mojang.authlib.minecraft.MinecraftProfileTexture.Type.ELYTRA.getClass().toString().equals("force a classload real hard")) { // this will crash some pirated clients. // better now than some weird and seemingly random crashes later in the game. } } The technic launcher itself seems to handle the authlib different than all other launchers. The problem is, that this class is not loaded when it should be, so the routine above fails and lets the boot-up crash. is this a bug? I think the technic launcher devs are needed to look into this. EDIT: After reinstalling technic launcher, it seemed to work again.
×
×
  • Create New...