Multimc5: MultiMC does not let you change the lwjgl version

Created on 24 Apr 2019 · 16Comments · Source: MultiMC/MultiMC5

System Information

MultiMC version: 0.6.5-develop-1223

Operating System:

debian testing

Summary of the issue or suggestion:

you cannot change the lwjgl version for minecraft 1.14, which is annoying in my case because it means I'm going to experience this bug:

https://bugs.mojang.com/browse/MC-144107

What should happen:

version is changed

Steps to reproduce the issue (Add more if needed):

Edit an instance (vanilla minecraft, mine is 1.14)
in the version tab, select "LWJGL 3"
click "change version"
select 3.1.6 (or any other one)
click OK

version is not changed. I closed and reopened multimc to make sure this isn't just a graphical error.

Suspected cause:

I found #2596 which may be related. but in 1.14, multimc forces lwjgl 3.2.1 even though minecraft ships with 3.1.6 (see also #2608). This can cause problems because of this bug:

https://bugs.mojang.com/browse/MC-144107

wai external metadata

Source

bogger33

👍1

All 16 comments

Also trying to manual edit LWJGL to a config of 1.3.2 (3.1.6) will crash lutris
`./MultiMC-4.log: 134.443 D "Req: org.lwjgl3 == 3.2.1" already has different version that can be changed. ./MultiMC-4.log: 134.443 D Setting version of "org.lwjgl3" to "3.2.1" ./MultiMC-4.log: 134.443 D "Req: org.lwjgl3 == 3.2.1" already has different version that can be changed. ./MultiMC-4.log: 134.443 D Setting version of "org.lwjgl3" to "3.2.1" ./MultiMC-4.log: 134.443 D "Req: org.lwjgl3 == 3.2.1" already has different version that can be changed. `

CGDoctor8 on 2 May 2019

This is not a bug.

peterix on 2 May 2019

This is not a bug.

Mojang has "resolved" their bug by downgrading LWJGL. If this is not a bug, please provide some work-around or persuade Mojang to pick a different fix. I really like MultiMC but Minecraft 1.14 is not playable with LWJGL 3.2.1 for myself and others...

Attempts at pointer capture by the window manager or other program (like x2x) cause nearly random camera movement. One moment you are mining happily Eastward in the Nether and the next moment you have broken the block below you and fallen to your death in lava.

gniftygnome on 23 May 2019

Just a note for any others here; it is possible to change the LWJGL version to 3.2.2 as described by Dinolek in https://bugs.mojang.com/browse/MC-144107 and that does resolve the problem. Hopefully Minecraft will soon change to 3.2.2 and MultiMC will not override it with broken 3.2.1 but (for now) there is a work-around.

gniftygnome on 23 May 2019

WAI

peterix on 7 Jan 2020

😕1

It may be "Working as intended", but the intended working in this case causes a glitch to happen because it conflicts with the fix applied by the actual devs of the game, and makes the game unplayable.
just add an exception so we can pick a different LWJGL version in 1.14/.15, jeez. Or give us a checkbox so we can force it on any version.
I tried manually adding a patch json that's just the 3.1.2 json copypasted and multimc had a segfault, is that "Working as intended" too?

DuendeInexistente on 20 Jan 2020

😄1

IDK what you mean, i can choose version from 3.1.2 to 3.2.2

Zetabite on 20 Jan 2020

IDK what you mean, i can choose version from 3.1.2 to 3.2.2

Peek 2020-01-20 19-48

DuendeInexistente on 20 Jan 2020

hm, why would you change the version? mine is on 3.2.2 and runs perfectly fine

Zetabite on 20 Jan 2020

hm, why would you change the version? mine is on 3.2.2 and runs perfectly fine

There is a camera bug related to the lwjgl version. See here : https://bugs.mojang.com/browse/MC-144107

It only occurs with linux versions, and it is really annoying. It is almost unplayable, as the camera orientation resets itself randomly. I have it on my system too

Blafy on 25 Jan 2020

👍1

Did you even try the workaround

Zetabite on 25 Jan 2020

Disabling the raw input ? Yes, it doesn't work anymore, see the last comments in the link above.

Blafy on 25 Jan 2020

👍1

Disabling the raw input ? Yes, it doesn't work anymore, see the last comments in the link above.

Killing unclutter ended up solving it, it's a program that hides the mouse pointer when it's not moving, and it must've been trying to wrestle control away from LWJGL for some reason.

Add 'pkill unclutter -e -i -9' to your pre-launch commands and see if that solves it.

DuendeInexistente on 21 Feb 2020

Actually, the problem occured only when I was using a non-native resolution in-game !
Changing it OS-side fixed it for me.

Blafy on 2 Mar 2020

To the pre-launch commands, I mean. Not arguments.

DuendeInexistente on 30 Mar 2020

Killing unclutter ended up solving it for me. Just add ʾpkill unclutter -i
-9ʾ to the pre-launch arguments. Maybe start it again when the game ends.
It's a program that hides the mouse pointer when you don't move it, it must
be trying to wrestle control away from lwjgl or something.
El 25/01/2020 17:52, "Blafy" notifications@github.com escribió:

Disabling the raw input ? Yes, it doesn't work anymore, see the last
comments in the link above.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MultiMC/MultiMC5/issues/2623?email_source=notifications&email_token=AEZZKH4GFQOASIVNHKZEHRTQ7SRAJA5CNFSM4HH7OTXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ5FGRY#issuecomment-578442055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEZZKH5YPMMV7ZGT2DLQSXLQ7SRAJANCNFSM4HH7OTXA
.