as3isolib is a great isometric library for actionscript 3

From building basic blocks…

To constructing sprites and objects with individual iso objects with their own bounding boxes.

This sample shows a two piece tree, a common issue with sprites in isometric is where to slice them up.  This sample shows a tree with the leaves able to be in front of a character so that you could walk under the tree and be in front of the trunk but covered by the trees.  Essentially height is respected.

Sample code for the tree tutorial:

package
{
import as3isolib.display.IsoSprite;
import as3isolib.display.primitive.IsoBox;
import as3isolib.display.scene.IsoGrid;
import as3isolib.display.scene.IsoScene;
 
import flash.display.Loader;
import flash.display.Sprite;
import flash.events.Event;
import flash.net.URLRequest;
 
public class IsoApplication extends Sprite
{
 private var scene:IsoScene;
 private var assets:Object;
 
 private var loader:Loader
 
 private function loadAssets ():void
 {
  loader = new Loader();
  loader.contentLoaderInfo.addEventListener(Event.INIT, loader_initHandler);
  loader.load(new URLRequest("assets/swf/assets.swf"));
 }
 
 private function loader_initHandler (evt:Event):void
 {
  buildScene();
 }
 
 private function buildScene ():void
 {
  scene = new IsoScene();
  scene.hostContainer = this;
  scene.container.x = 200;
  scene.container.y = 200;
 
  var treeTrunkClass:Class = loader.contentLoaderInfo.applicationDomain.getDefinition("TreeTrunk") as Class;
  var treeLeavesClass:Class = loader.contentLoaderInfo.applicationDomain.getDefinition("TreeLeaves") as Class;
 
  var grid:IsoGrid = new IsoGrid();
  grid.showOrigin = false;
  scene.addChild(grid);
 
  var s0:IsoSprite = new IsoSprite();
  s0.setSize(25, 25, 65);
  s0.moveTo(50, 50, 0);
  s0.sprites = [treeTrunkClass];
  scene.addChild(s0);
 
  var s1:IsoSprite = new IsoSprite();
  s1.setSize(125, 125, 100);
  s1.moveTo(0, 0, 75);
  s1.sprites = [treeLeavesClass];
  scene.addChild(s1);
 
  scene.render();
 }
 
 public function IsoApplication ()
 {
  loadAssets();
 }
}
}

current features

• simple scene creation
• 3 primitive types
• base class for displaying user-created content
• plenty of styling option on vector based primitives
• integrates well with a variety of tween engines
• standard 3D isometric positional sorting

So get busy building the flash version of roller coaster tycoon…

• Features of the library
• Online docs
• Download as3isolib at Google Cod
• as3isolib_tutorial_001 – Intro single block
• as3isolib_tutorial_002 – Multiple blocks
• as3isolib_tutorial_003 – Customizing sides
• as3isolib_tutorial_004 – Sprites and construction
• Blog post about the release

Be sure to check out the shadow demo that this is based on:

After posting my shadow experiment, Patrick Matte posed a question wondering if I would be able to do real-time reflections in a similar manner. The next day I had it done, along with some nice iterations along the way: orthographic and perspective projection (I can release those later if anyone really wants them). I’ve been sitting on it every since and finally decided I would take the time to write a little description into how its done and give the code to those who are interested (and I fixed up some code for backface culling in the reflection this morning).

• View the reflections demo
• View the reflections post
• View the shadow demo
• View the shadow post
  

• Post on the release
• Download the code
• API Reference (asdoc)

Here’s a peek at the classes in the API:

http://www.ffilmation.org/docs/api/1.0/class-summary.html

All Classes

Get your game on!

The author, who is currently anonymous, describes it as:

The FFilmation Engine is an AS3 isometric programing engine, focused mainly on game development. The aim of the project is providing a robust development platform, where game designers can work on the game’s details and forget about the render engine. It is intended to be really usable from a “real production scenario” point of view.

Unfortunately there is no name associated with the project yet, I think it would be wise to let that be known. The author has some info on the level structure of files and 3 great demos.

Here are some features and plans for the engine:

• Have a programming interface as small and easy as possible, no matter how complex the internal code is. From a software engineering point of view, the OO structure may not be as correct and clean as it could have been. It is not messy, but several decisions where made that improved performance and simplicity at the cost of breaking some “good OO programming” conventions.
• Rendering performance is a major concern when designing all the algorythms. Some of them have been rewritten 4 o 5 times from scratch until one fastest enought was found. If it doesn’t perform well, it is not usable. We’ve all seen several impressive actionscript demos that look really cool and invite to be used in your next project. But then if the effect takes 90% of your CPU, you can’t build anything on top of that.
• Graphic designers should be able to work on the application’s ( game or not ) environments without any programming skills, visually, and with almost immediate previews of what they are doing. Using the engine should be fun to some degree. If you have this terrific engine and adding a wall to your dungeon means you have to write 10 lines of OO gibberish, lazyness will eventually win you over. If art directors can draw and place the walls and lights an floors and enemies and see them appearing onscreen, you have more chances of reaching your deadline.
• Flash has built-in drawing and animation tools. You should be able to take advantage of them !!

All this is important because in reality projects depend on limited resources. Resources are money and time, but also the enthusiasm of indie developers or single individuals doing stuff “for fun” in their bedrooms. Projects, specially the “for fun” ones, have more chances of completion if the production process is gratifying to some degree.

Here’s a list of highlited features:

• One engine capable of handling several isometric scenes of different complexities.
• Create scenes from human-readable XML definitions, allowing easy edition of the scene’s topology and contents
• Graphic media can be split into several external resources and loaded when an scene needs them
• Flat textures. Paint your grahics directly into flash. Walls, floors and celings are edited as 2D graphics and projected by the engine. Elements and animated characters can be animated via flash timeline, no need for complex programming.
• Dynamic lighting, global lighting, real-time shadow projection. Multiple lights from multiple sources affecting the same objects.
• Bump-mapped surfaces. Still somehow buggy and a serious performance killer, but already there.
• An extendable material interface. MovieClip materials, autotiled materials, procedural materials.
• Automatic zSorting of all surfaces and objects
• Built-in collision detection. No need to program complex coordinate comparisions, simple listen to COLLISION events generated by the engine.
• Basic AI API helpers such as “is character A visible from character B’s position ?”

I plan to make the engine open-source, but I’ll wait until I have a release “solid” and documented enough.

I am looking forward to more updates and to find out more about the author. We have some great engines underway in ’08 for AS3 and it looks to be a very fun year in that aspect.

Because it is an isometric engine is is not true 3d but sprite based animation. However with planes and objects other isometric 3d objects can be built such as walls, boxes, buildings, cubes, etc. I wonder if there are any toolkits being used or if this is all custom built?

Keep your eye on this space. It is very similar to the Alternative Engine.

Here are all the Demos:

• Example 1
• Example 2
• Example 3

And some docs on the architecture:

• Documentation
  • 1. Design
  • 2. Usage
    • Material How-To
    • Object How-to
    • XML Definitions
    • XML Scenes
  • 3. API

Check it out!