The Fail: messages are just reminders to me. For instance, some things in slick are optimized using display lists - which don't work on this renderer (yet?).

Yeah, noted that the logging was rather insistent.

Have to check how much work it is to create an app with a nice scrolling map in the background that can be zoomed. Any idea when this will be far enough advanced that one could prototype something like that? Everything I do ends up being a strategy game requiring the scrolling of some huge background map. Or would that sort of thing still be best to do straight in libgdx? I think I really need to do a game-independent implementation of this sometime and OS it - I never find any good examples/tutorials of this kind of thing.

No pressure, of course - but you know, if I don't ask, I certainly won't have an answer...

LibGDX is a great library already. Seems like it'd be a good fit for what you want. If you do want to use Slick for the purpose as far as I can see most everything will work - just not been tested on android yet

Yeah, but I might well emulate display lists with recorded in memory operation lists - or VBO backing or something.

The libgdx SpriteCache class sort of does this. It uses a VBO and does the bookkeeping for binding various textures. It is good for any static geometry and is currently being used for tile maps (example here). Looks like this...

Added your fix. Took some time, was busy with a lot of other stuff. If you happen to run it on a Samsung let me know what AndroidGraphics reports in LogCat. You'll either want to work from source or use the latest nightlies.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org