Skip to content

Releases: libgdx/gdx-liftoff

1.9.10.9 General Update and Bugfix Release

09 Jun 00:16
Compare
Choose a tag to compare

This release defaults to Gradle 6.5; they keep releasing versions, so I am too. Compile times seem to be sometimes quite a bit faster with Gradle 6.5, though I mostly noticed a speedup when IDEA was set as the build tool, not Gradle, and running Gradle tasks. This updates and adds to the now-22 KTX libraries, as per #13 , and also updates several versions of other libraries (notably Formic, which had some extra changes needed, and anim8-gdx, which should be usable out of the box now). Thanks to @Mr00Anderson for finding a bug with shared modules and submitting a PR; there may be similar bugs in other previously-unused modules, like ios-moe, so I'm glad at least this type of thing may be easy to fix in the future. This also adds a line to the "legacy" LWJGL2 desktop launcher that gets rid of the highly-irritating error caused by successfully exiting.

1.9.10.8: Grab Bag of Fixes and Features

29 May 21:46
Compare
Choose a tag to compare

This release is mostly focused on improving Kotlin support and third-party extensions. It also updates Gradle to 6.4.1, Groovy to 3.0.+, and Scala to 2.13.+, and there's some hopefully-usable work on the Android target. The third-party extensions added are MrStahlfelge's ControllerUtils (to handle controllers sanely, plus a scene2d option for the library when no controller is connected), crashinvaders' gdx-vfx (for nice and easy post-processing effects, including a predefined set of them as an extra dep), and tommyettinger's anim8 (for writing animated gif and png files from Pixmaps). This release also fixes the version check, and should pop up a toast if a newer version has been released and you're using this version. 1.9.10.2 to 1.9.10.7 had the version check disabled because I forgot about it. Whoops.

Thanks to QuillRaven for bug-finding several problems with Kotlin integration and/or Android stuff, and the libGDX Discord for actively testing 1.9.10.7 almost as soon as it came out. If you encounter any problems or just have requests for third-party libraries, feel free to post them as issues.

1.9.10.7 GWT Support Release

08 May 00:16
Compare
Choose a tag to compare

If you don't use GWT, this is the same as the previous release, but if you do use GWT, this should improve on 1.9.10.6 a lot. It makes the html:superDev task no longer require manually terminating a server process (it ends it automatically), which was also true of 1.9.10.6, but also fixes a bug in that release that didn't start the superDev code server. Now you can reload normally for superDev, using the bookmarklets or refresh button to recompile changed classes. This depends on Gretty, a Gradle Jetty plugin, to handle the server during development; this is similar to much older versions that used Jetty to launch a file server.

1.9.10.6 Library Update and Return to LWJGL3

27 Apr 02:34
Compare
Choose a tag to compare

This release mostly updates various libraries and adds some more that could be helpful for various types of games.
Many are improvements or fill-ins for missing features: ShapeDrawer is a high-performance replacement for ShapeRenderer in libGDX, TenPatch is an enhancement of the 9-patch support in libGDX, and Formic is a one-method library that allows String.format() to be mostly used on GWT (as Stringf.format()). Colorful-GDX allows changing colors in more ways than just multiplying channels. The Spine Runtime is selectable as a dependency, though you need a Spine license to use it outside of evaluation. Typing-Label, Artemis-ODB, SquidLib, and a few other libraries have been updated to newer versions.

This version goes back to using LWJGL3 and drops the pack task and the raw UI assets in general, though it can still copy a rudimentary skin into a project (but without needing to pack it). The gdx-tools dependency that pack added requires LWJGL2 to be used or excluded, and packing also adds a fair amount of time to a build, so now there's just a pre-built skin to enable scene2d.ui things to be used, and gdx-liftoff just copies it in.

1.9.10.5 Support Release, with Gradle 6.3

26 Mar 22:23
Compare
Choose a tag to compare

This release makes some internal changes to gdx-liftoff to hopefully address issues with gdx-tools and LWJGL3 conflicting, updates Gradle to 6.3 (which should allow Java 14 to be used; it could already be selected), and uses libGDX 1.9.10 both for user projects by default and for its own UI. This release may be less compatible with high-DPI screens because it uses LWJGL2 to show its UI instead of LWJGL3, but this should allow the texture packer to work from Gradle scripts.

1.9.10.4 Minor Update (Gradle 6.1.1)

05 Feb 05:36
Compare
Choose a tag to compare

This release is roughly the same in features as the last one, except that you can select Java versions from 7 to 14 smoothly on the Advanced tab, and the Gradle version projects will use is now 6.1.1. I don't know if Gradle 6.1.1 will be compatible with Java 14 when its final version is released, but you can use gdx-liftoff with Java 13 today.

1.9.10.3, with better Android support

11 Nov 07:15
Compare
Choose a tag to compare

This release is identical to 1.9.10.2 in most ways, but the Android project generation was pretty bad; I think it wasn't generating usable Android projects, or if it was, they needed some attention. This appears to fix Android project builds as long as you have all of your Android SDK installation in order; Android plugin version 3.5.0 seems to work well. It also turns off the daemon by default; it appears that some Android tasks run in the daemon use a phenomenal amount of RAM and don't give it back to the OS, meaning multiple daemons will quickly consume quite a lot of RAM.

Version 1.9.10.2 with Gradle 6.0 and Java 13 support

10 Nov 05:06
Compare
Choose a tag to compare

It's another release! Java 13 is out and now so is Gradle 6.0, which is the first version to support Java 13. This gdx-liftoff version defaults to Gradle 6.0, and though there's still no convenient way to choose language level 13 in the app, you can set it by changing sourceCompatibility in your desktop and/or lwjgl3 modules and core. It's still probably a good idea for some usage to use language level 7, which is what libGDX uses, but many projects can upgrade to level 8 at least. Java 9 and higher are, of course, not compatible with Android, iOS, or GWT.

1.9.10.1 with GWT adjustments

06 Sep 17:31
Compare
Choose a tag to compare

This release doesn't change much; it does make the GWT version non-selectable by users and instead matches the correct GWT version for the selected GDX version, since the two must change in lockstep. Hopefully this will fix lingering (unreported) issues with GWT versions when using gdx-liftoff.

1.9.10.0: Now updated to libGDX 1.9.10

29 Jul 04:02
Compare
Choose a tag to compare

This release primarily exists so the default version is 1.9.10, but it also makes some changes to match the official setup's support for resizable GWT applications (and it includes a useful part of a currently-unmerged PR, libgdx/libgdx#5691 ).

There's not many breaking changes in libGDX 1.9.10, so it's unlikely but possible that projects using 1.9.9 would encounter breakage. There are several breaking changes from 1.9.8 to later versions, so if you're updating from further back you may encounter some issues. I made this Gist that you can use to replace SpriteBatch if the changes to Batch color handling between 1.9.8 and 1.9.9 (and persist into 1.9.10) are a problem; in the uncommon case where rendering sets the Batch color extremely often, especially using packed float colors, then that Gist is something to try because it will make the API match 1.9.8 and should perform better if colors are being packed into floats often.