Windows .exe LWJGL Issues

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
Status
Not open for further replies.
Well, this should stop that error from making it crash, but I don't know if it will crop up somewhere else.
Add,
-Dorg.lwjgl.util.NoChecks=true
to the additional java parameters in the advanced options window.
 
huh, on the console window, switch it from minimal to debug and post a new log.
 
Everything I'm reading is either years old or was caused by corrupted drivers. You said it happens on vanilla minecraft, could you post a log from that? 1.5 if possible.
 
  • Like
Reactions: Booker The Geek
Your problem is this:

2013-04-29 11:06:45 [INFO] [STDOUT] LWJGL Version: 2.4.2
Click to expand...

Current LWJGL is 2.9.0. Here is what you do to fix this problem:

1) Download latest version here
2) REPLACE the following FROM /lwjgl-2.9.0/jar TO minecraft/bin
- lwjgl.jar
- jinput.jar
- lwjgl_util.jar
3) REPLACE the ENTIRE CONTENTS of the folder FROM /lwjgl-2.9.0/native/windows TO minecraft/bin/natives

You need to do this for EVERY instance of Minecraft you wish to play. Thus, if you are playing on the Ultimate pack, you need to edit the files in FTB/Ultimate/minecraft/bin.

WARNING: A 'fresh install' of minecraft will WIPE these changes and revert you BACK to 2.4.2. You will need to then manually change your LWJGL. Again.
 
Watchful11 said:
From what I can tell this is from a depreciated hook in LWJGL. But it's weird, cause all your logs say,
LWJGL Version: 2.4.2
which is the one minecraft ships with. I know you said LWJGL is at latest, what did you do to update it?
Click to expand...

Kiwi_EXE said:
That is a re-install after moving the install location but I went to the LWJGL website, downloaded a zip containing the latest libraries and followed the instructions, replacing each library with the later version, making sure to use the Windows libraries and not the Mac/Linux ones.
Click to expand...
 
I'm guessing that's what they will tell you to do on the minecraft bug tracker. So try doing that with vanilla 1.5.
 
Hmmm... well, at least it's a different error message now.

I'm wondering why it is trying to run in mixed mode, though. You've got a 64 bit processor, and 64 bit java, you shouldn't need that.

Either way, you've got a null pointer exception crashing things almost immediately.

Are you able to run anything else in Java?
 
Status
Not open for further replies.
Top Bottom