-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.16 Forge doesn't seem to work #1
Comments
This single line is also buried in the logs. Might be useful
|
Try adding -Dfml.earlyprogresswindow=false to MultiMC's Java arguments. Earlier this month I was trying to get ATM 6 (the forge modpack) working under wayland and I essentially independently came to the same solution you found with patch 0002. I found the above java argument because people reported it fixed some glfw issues with forge on m1 macs, and it also seems to fix glfw issues with forge on wayland as long as you apply patch 0002 as well. Also, you also shouldn't need patch 0004 with the argument as I believe it bypasses whatever code is triggering that function. |
I believe the root cause of this issue is because forge patches minecraft to create the glfw window itself so that it can create the "early progress window" as seen here. Forge then delays showing the window as seen here which, referencing this commit in Kitty's Github repo, wlroots seems to not like. (the later half of the comment in that commit is extremely petty, but the former half gives a useful explanation). Also, thanks for patch 0001! I tried it out a few days ago when you released waynotgonnaland, and it fixed the freezing issue that caused me to give up on getting this working earlier this month. |
|
No window appears, and this error is printed
The text was updated successfully, but these errors were encountered: