Qiso isometric tile engine v1.0.2 release

We’ve just pushed Qiso 1.0.2 live, with a couple of new camera features:

  • Panning is now restricted to prevent swiping away from the map itself. I.e. it’s no longer possible to swipe beyond the map boundaries.

  • Added a new lockCamera() function. When called with a character name, the camera will move to that characters position and remain locked on the character while it moves around the map. Calling lockCamera() again without any character name releases again. This approach means that it can be used to either locate and track a character (like in the old Theme Park / Roller-coaster Tycoon type games for example) or to create games where you play as a single character.

Full documentation, quick start guide, and sample isometric graphics + Tiled map file downloads at https://qiso.qweb.co.uk/documentation

Video and code samples at https://qiso.qweb.co.uk/samples

Qiso plugin available at https://marketplace.coronalabs.com/corona-plugins/qiso-isometric-tilemap-engine

We’ve literally only just pushed this update to the Corona repository so please do allow a couple of hours from the time of this post for the build servers to synchronise.

  • Panning is now restricted to prevent swiping away from the map itself. I.e. it’s no longer possible to swipe beyond the map boundaries.

I wonder where that idea came from? :wink:

Good work on the engine though.

Ha, the panning feature was a little useless without it really, to be totally honest. Very much didn’t intend it to take this long to update that!

Credit where it’s due actually - the previous 1.0.1 release brought some performance improvements sparked by our conversations, so thanks for that :grin:.

  • Panning is now restricted to prevent swiping away from the map itself. I.e. it’s no longer possible to swipe beyond the map boundaries.

I wonder where that idea came from? :wink:

Good work on the engine though.

Ha, the panning feature was a little useless without it really, to be totally honest. Very much didn’t intend it to take this long to update that!

Credit where it’s due actually - the previous 1.0.1 release brought some performance improvements sparked by our conversations, so thanks for that :grin:.