libGDX 1.1.0 released

libGDX 1.1.0

As promised, we’ll try to do bi-weekly releases. If we miss one for some reason (vaccation, life), don’t be angry with us. You can always work off of the snapshot releases, which you can select in the setup ui or manually change to in the build.gradle file.

You’ll also notice that we increased the minor version (2nd number) instead of the patch version (3rd number). The reason is that we introduced a small API change in the Matrix4 class. While this is unlikely to hit more than 0.001% of our users, it’s still an API change. As per our policy (which is not exactly semantic versioning) we thus increment the minor version, so you know an API has changed.

Without further ado, here’s what’s new:

Note: it is very important that you update to the latest RoboVM Eclipse plugin if you use Eclipse!

If you want to update an existing project, read this wiki article. Use “1.1.0” for the latest release and “1.1.1-SNAPSHOT” for the latest nightlies.

If you create a new project, the setup app will already allow you to specify the latest release and snapshot.

11 thoughts on “libGDX 1.1.0 released

  1. “BitmapFontCache now supports in-string colored text through a simple markup language” That is fantastic. I was going to have to schedule some time next month to get this effect and BAM! you did it for me in a much better way than I ever would have! Thanks!

  2. Interesting. If I understand it correctly, I18NBundle makes it possible for the translator to provide different strings based on custom number boundaries, right? (like the example with “thousands of files”). That’s quite nice, but I am wondering whether it’s not too much work for languages with complex plural rules, because translators for these languages would have to repeat the rules for all plural strings, right?

    I also prefer English-based original strings to id-based strings, but I understand this is less common in the Java world.

  3. “Simulating different densities on desktop”, and the upgrade of box2d is what I’m most excited about, that’s fantastic.

  4. Takes hours to import the gradle project. It is very stupid. Most of us is using LIBGDX to build mobile game, usually small games. 90% of LIBGDX users do not need such a monster.

  5. I have an libGDX iOS application that works perfectly when testing in Eclipse via Run as iOS Device or Run as Simulator. However, when I use RoboVM Tools -> Package for App Store to get an .IPA file that I install on my iPad, it crashes after the libGDX splash screen.

    It isn’t a problem with provisionals or certificates since my Run Configurations are exactly the same as the options I used to export.

    This problem seems to be pretty common after gradle build, but I have not found a solution yet. Can someone shed some light?


  6. You have definitely a better chance to get an answer on the forum or the irc channel.

Leave a Reply

Your email address will not be published.