You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Troubleshooting.md
+14-12Lines changed: 14 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -302,11 +302,12 @@ handle at all. It causes a crash in native code (which can't be caught with try/
302
302
lock input to the rest of the Liftoff program as we were doing before, but permit the file dialog to do its thing, and
303
303
re-enable input when the dialog closes.
304
304
305
-
1.12.1.15 ~~and up~~ use a newer version of the file dialog library (we went from LWJGL 3.3.1's NFD binding to LWJGL
306
-
3.3.4's NFDe binding). This had some bug fixes, but also had all kinds of new bugs, so the current releases are
307
-
back to using 3.3.1. If anyone is using an older Liftoff version that uses NFDe from LWJGL 3.3.4 or 3.3.5, and
305
+
1.12.1.15 uses a newer version of the file dialog library (we went from LWJGL 3.3.1's NFD binding to LWJGL
306
+
3.3.4's NFDe binding). This had some bug fixes, but also had all kinds of new bugs, so many releases were back to using
307
+
3.3.1. If anyone is using an older Liftoff version that uses NFDe from LWJGL 3.3.4 or 3.3.5, and
308
308
encounters issues with that (maintained) code, you can send [bug reports to NFDe](https://github.com/btzy/nativefiledialog-extended/issues).
309
-
This might eventually let NFDe become useful for us here, but for now we need to use the older NFD.
309
+
Thankfully, LWJGL 3.4.0 came out in mid-January 2026, and with it an updated NFDe that seems to have fixed most of the
310
+
critical bugs. It's used by gdx-liftoff 1.14.0.4 . We'll just have to see if it works on macOS and Linux, though...
310
311
311
312
### The native distributions for macOS won't run how they should!
312
313
@@ -383,22 +384,22 @@ you want to bundle a different JDK version with your application, you have some
383
384
384
385
First, make sure Gradle itself uses the JDK version you want to bundle. In IDEA and AS, navigate to:
385
386
`File | Settings | Build, Execution, Deployment | Build Tools | Gradle` and select the version you want in the bottom
386
-
drop-down menu. If I want to build with and bundle Java 24, for example, I would select a Java 24 version from there,
387
-
like "Eclipse Temurin 24" or "BellSoft Liberica 24". If you don't have any Java installation of the version you want,
387
+
drop-down menu. If I want to build with and bundle Java 25, for example, I would select a Java 25 version from there,
388
+
like "Eclipse Temurin 25" or "BellSoft Liberica 25". If you don't have any Java installation of the version you want,
388
389
Navigate to `File | Project Structure | SDKs`, Click the `+` at top, and `Download JDK` to get the version you want.
389
390
If you just downloaded a JDK, you can do the first step again and actually select your wanted version this time.
390
391
Click Apply or OK once you have selected your wanted version in the drop-down.
391
392
392
393
Second, you'll need to make the links in `lwjgl3/build.gradle` match the JDK you selected, with the same major version
393
394
and hopefully the most recent minor version you can manage. The links currently used by default in Construo are taken
394
395
from https://github.com/adoptium/temurin17-binaries/releases , on the only section with blue links listed inside it.
395
-
If you want the recent Java 24, you'll want to look in https://github.com/adoptium/temurin24-binaries/releases instead
396
-
(note, the only change is from "17" to "24"). Other versions are similar; 17 is just about the first version of JDK that
396
+
If you want the recent Java 25, you'll want to look in https://github.com/adoptium/temurin25-binaries/releases instead
397
+
(note, the only change is from "17" to "25"). Other versions are similar; 17 is just about the first version of JDK that
397
398
Construo should work with, and is definitely the only one still receiving support from any OpenJDK vendor. The actual
398
399
links probably don't matter too much, but you may want to copy the link matching a description like
399
-
`OpenJDK24U-jdk_x64_windows_hotspot_24.0.1_9.zip` to make sure everything matches. The reason the link doesn't matter is
400
-
that you can usually just change the version from `17.0.15` to `24.0.1` (in this case) and then change the last number
401
-
where it appears to match as well (`6` to `9`), which is after an `_` underscore in one place and after the escape `%2B`
400
+
`OpenJDK25U-jdk_x64_windows_hotspot_25.0.1_8.zip` to make sure everything matches. The reason the link doesn't matter is
401
+
that you can usually just change the version from `17.0.15` to `25.0.1` (in this case) and then change the last number
402
+
where it appears to match as well (`6` to `8`), which is after an `_` underscore in one place and after the escape `%2B`
402
403
in another place.
403
404
404
405
Once you've changed the link for each platform you want to support (probably Windows, maybe also Linux, and unlikely
@@ -420,7 +421,8 @@ while changing the source code, saving, and seeing the changes as soon as the pa
420
421
under "gwt"). The differences here are that `dist` runs a lot more quickly in the latest version, and that (for reasons
421
422
I haven't fully figured out) `superDev` now depends on running `dist` when it first starts up. More importantly,
422
423
`superDev` pops up a Swing window (using GWT itself to do so) that provides a link to your re-load-able page. It isn't
423
-
hidden in the Gradle output text anymore, which is nice.
424
+
hidden in the Gradle output text anymore, which is nice. You may need to wait a few seconds for the link to appear near
425
+
the top of the Gradle window, and you can also copy the URL into a browser of your choice.
0 commit comments