I killed it off a few minutes ago, but there is an "EAW32.TM" in its place.
The rationale was the simple ability to store the "EAW32.TM" file in the "DATA.CDF" rather than mess around with the ".tm2" extender.
As the data is in four bytes it was logical to use the name "EAW32.TM".
I now have it as I wanted it:

1. There is just one string file "tilename.str" with the default in "TEXT_ENG.CDF".
It is read....

BNField8.ter
BNGrass.ter
BNWater.ter

etc

.... and the names of the "BN", "LR" and "BP" files are generated by routines in the exe.

2. There is a folder "EAWTM2" in the root folder. It contains the default bump tile sequence in the "BumpVal.eaw" file. If there is a "BumpVal.eaw" file in the root folder the exe will use it in preference to the one in "EAWTM2". The data in it reads like this:
-1
-1
-1
3
4
5
-1
-1
-1
-1
-1
-1
-1
-1
14
etc

Tiles 0, 1, and 2 have a bump value of -1 so they have no bump tile.
Tile " "BNCoast1.ter" has a value of 3 so it is mapped to "BPCoast1.ter". In every case where there is a mapping the bump index is the same as the tile number.
Tile 14 "BNRiver1.ter" is mapped to "BPRiver1.ter".
For this to work with the original tiles only three BP files needed to be copied and the copies re-named. I have a batch file which does this.

3. It is working well with current and older scenarios. They just need the addition of the additional BP tiles (made with the batch file) and the "eaw32.tm" file unless they are using the defaults like SWOTL and ETO_01. So far I have had no problems with DAW, SAW, SPAW, Malta and Mod Squad BoB. I have a utility which reads the "eaw.tm" file and makes the "eaw32.tm" file.

4. It is working with more than 64 tiles.
The number of tiles is a now a variable and has a default value of 64. However, if there is a "Numtiles.eaw" file in the root folder it is read from that. In the screenie in my "White Christmas" post at SimHQ I was using one with a value of 65. All values of "2" in the normal "eaw32.tm" had been changed to "64" so the 65th tile was displayed instead of the normal water tile.

Jel

Okay. Dumb question no.1: how many tiles can we now have?

Moggy DCM

In theory 16777215 (256x256x256 -1) because the first three bytes are used as the tile ID and the fourth is either 0, 64, 128 or 192 for the orientation.
In practice I have limited to 256 (0 to 255 as the first byte) until demand increases

Jel

I have now integrated this into Ralf's V10 and have a compiled a working version

Jel

Possibilities are intriguing!

Moggy DCM

Grab the download and check it out
Now I need to edit the tilemap maker to accommodate the extra tiles.

Jel