Here is a haXe demo of parallax scrolling layers made using Molehill. Haxe now includes an easy way to write shaders using hxsl (haXe Shader Language).

The graphics were “evolved” using the Random Art Evolver. The map is generated from Perlin noise.

Try the demo here (requires Flash Player 11 beta!):

• Molehill Tilemap Demo (press F11 for full screen, arrow keys to move and Space to change background color)

  There is no preloader so be patient, it may take 5-10 seconds to generate the textures and build the maps!

• TilemapDemo.zip (haXe source code)

[kml_flashembed movie="http://www.wieringsoftware.eu/wp-content/scroll.swf" width="320" height="240"/]

I’m releasing some base code here for haXe which I’m planning to use during the competition. This might also be useful for anyone who wants to start creating Flash games in haXe. Basically, the code is pretty much the same as the scroll demo I made earlier, but now ported to AS3 (for Flash player 9), which is a lot faster. The main thing the code does is make it easy to use graphics and maps created in Tile Studio together with haXe.

(click and use arrow keys)

This is a little demo, included in the package to show how to use the library. There is a readme.txt file which has step-by-step instructions on how to install everything (haXe, swfmill, Tile Studio, FlashDevelop) and get it working.

• Download HaxeBaseCode-1.7.zip (154 kb)

At first, the difference in speed appeared to be huge, but those were rather the result of other optimizations I did in the meantime. All these methods work at roughly the same speed if you’re using large tiles. But when you have small tiles (which I normally use for games) and you have hundreds of them on screen all the time, handling all those tiles seems to become far slower than rendering them.

Here are three methods I tried:

1. The first is the method used in the scroll demo. Every tile is represented by a separate MovieClip, the total number of MovieClips stays constant, when a tile goes off-screen, its MovieClip is reused for the tile that appears on the other side. Using this method makes it very easy to add animated tiles, since they are handled by flash.
2. The second method is the same method as above, but with only one MovieClip with a BitmapData attached to it (as the screen surface) and just “blitting” all the tiles to it using copyPixels. Here you need to implement tile animations yourself.
3. For the third method (demonstrated below), each layer has its own BitmapData object as a surface (size of the screen + 2 tiles), which scrolls along with the layer. That way, you only need to redraw the tiles that actually change (at the edges and animating tiles). When you start to scroll, you’ll run out of space on the surface, but it wraps around to the other side. So normally, the screen will be divided in to sections horizontally and vertically. To get all those back together, there are 4 MovieClips per layer and the BitmapData is attached to all 4 of them. By placing them next to each other, you get the entire screen in the middle. The Mario example only scrolls horizontally, so it only uses 2 of those surfaces (per layer).

This little demo is based on my Mario clone for DOS, there are no enemies and the only thing you can do is collect coins. If you are using FireFox, click on the game first. Use the arrow keys to walk and space to jump. Enjoy!