I've been planning this project for a long time, and with the recent release of Axe 1.1.2, I can finally begin to make it a reality!

YAAM

YAAM? How is a vegetable going to help me develop Axe projects?

YAAM is no vegetable! It stands for Yet Another Axe Mapper, my friend! It is an Axe library designed to make smoothscrolling tilemapping in Axe both fast and easy by providing all the necessary routines for you in an easy to use manner! Instead of having to write your own tilemapping engine to your custom specifications, select the options you want from the built-in variety of options in YAAM and your tilemapper is done! (This will be more true in later versions as I add more features)

But drawing a whole unaligned tilemap every frame is slow! I don't want my game to be slow!

Au contraire, YAAM makes scrolling tilemaps very quick by shifting the previous frame's tilemap and redrawing only the tiles shifted in, which is quite fast. If the tilemap doesn't shift between frames, you don't need to redraw it at all!

That sounds cool! What other cool features does it have?

Here, let me draw you up a quick list: Very fast tilemap shifting Handles all drawing and shifting through a few easy to use routines Works with any tile size up to 8x8 Works with any map width and height

But I want this feature! And fix this bug!

For any feature requests and bug reports, just post them in this thread. However, I am already planning many features for the future, so your feature request may actually already be on my to-do list: Spoiler For To-Do List: Allow many variables, like pointers and map size, to be defined as constants instead Allow tile sizes larger than 8x8 Add support for grayscale Implement optimized multi-pixel shifting Add support for inflated coordinates (256 = 1 tile, instead of 1 = 1 pixel) Add support for archived tiles and tilemaps Add support for nibble or bit tilemaps Implement packed tile reading (e.g. 4x4 = 2 bytes, grayscale 5x5 = 7 bytes) Optimize all the code!

Awesome! Where do I get it? How do I use it?

Easy there, one question at a time! The latest version of YAAM (v0.2) can be found attached to this post. It requires Axe 1.1.2. Download the zip file, send YAAM.8xp to your calculator, include it anywhere in your program, and you're good to go! Full usage details can be found in the included readme. No they can't, because I haven't written one yet. However, I have included a sample program using YAAM that should detail the basics of using it. You can also learn more about YAAM's options and variables by looking at the options section in the library itself, which has small comments to generally explain what everything is. To set constants like tile width and height to your own values, redefine these values before including YAAM. To set everything else like tilemap size and pointers, store values to the variables listed after including YAAM.

More features will be coming soon!

Looks nice! Keep it going!

Looks nice, so you plan to implement grayscale?
Also nice pokemap

Grayscale is right at the top of my to-do list.

Looks nice! Keep it going!

Will do!

That's look awesome, I like those optimization !

Just a question, what are apperr1 and apperr2 usually ?

appErr1 and appErr2 form a 26-byte section of RAM that you can use as scrap RAM in your programs, because very few things will write to them. As the name suggests, really the only thing that writes to this area are errors, but if an error message occurs, you don't need to worry about your program's data being destroyed because your program will have already quit. 26 bytes was about the perfect size for the amount of data I needed to store, so I chose this as the default RAM area to be used.

But, just like everything else in this project, I've planned to make everything customizable. If you want to change the RAM area used for some reason, you can by defining °MR to be something else before including YAAM.

Yeap, I noticed it, your code is beautiful, that's a kind of art.

beautiful and illegible
I guess that runer just knows every free ram area...

I'm not sure if I'll add animated tile support. The idea behind my drawing method, and what makes it fast, is only drawing tiles as they are shifted in. Having to redraw only a few animated tiles per frame might work. But if a large portion of the visible area was composed of animated tiles, my method would actually start to become slower than just redrawing the entire tilemap every frame.

Idea: Add Animated tilemaps (like water in your map)

The whole concept of Runers tilemapper is that it doesn't have to redraw the entire screen every frame, and doesn't even do anything if the screen isn't moving.  If you had animated tiles, you might as well just use a regular tilemapper and redraw the entire screen each frame. 

EDIT" Double Ninja'd

This is nice runer112. Hopefully this should make things much easier for people.

Does your tilemapper supports shifting more than one pixel in one frame? I mean like in Super Sonic Ball, for example, where you could scroll by 4 pixels at once and it even supported variable scrolling rates, as required by the game physics.

Yeah that's what I thought.

Also does your tilemapper regulate speed for vertical movement when it's aligned horizontally? In some games I noticed that it runs much faster when the map is aligned than when it's not. I know it's due to aligned sprites taking less time to draw, but it kinda looks weird in some games.