| AMOS TOME Series IV Manual Index |
|
|
7 |
written.
The TOME Editor allows you to design these maps, and the TOME Extension commands you have recently added to your AMOS system give you commands specifically written to display and communicate with these maps in your program.
The only limits to the size of a TOME map are memory, and the maximum size of 32768x32768 tiles, which is about 4,473,924 screens using 16x16 pixel tiles, and just under 18 million screens using 32x32 pixel tiles. Unfortunately, this sort of map would take up 1 gigabyte (1024 Megabytes) of memory, but you could always work to CD Rom.
There are 5 types of file used for TOME, only 2 of which are vital, the other three are just useful.
We start with the Tile Bank. As far as AMOS is concerned, this is an Icon bank, where all the icons are the same size (e.g 16x16 or 32x16). This is loaded in exactly the same as a normal icon bank, i.e
Load "filename.abk"
which will load it into bank 2
You might want to change the size of tile that you want to use. Simply use the command:
Tile Size x,y
to change the size. X and Y can be 16 or 32, giving you 4 different sizes of tile, listed below with their pros & cons:
| Size | Advantages | Disadvantages |
|---|---|---|
| 16x16 | Uses less memory for the tiles, single tile changes are rapid, Best Collision detection. Best for general usage. | Slightly slower scrolling |
| 16x32 | Reasonable memory use. Fast for scrolling vertically, Reasonable collision detection | Slow at scrolling horizontally |
| 32x16 | Reasonable memory use, Fast for scrolling horizontally, Reasonable collision detection | Slow at scrolling vertically |
| 32x32 | Fastest scrolling | High memory usage, Inaccurate collision detection |