In my work with TM2 I have produced an exe which generates the names of the bump tile from the name of the terrain tile.
This overcomes the problem in previous exes where the names are in a hardcoded list embedded in the exe.
It was worth doing this because the names of almost all bump tiles match the name of the corresponding terrain tile, so they already existed- stored in the terrain.cdf file. For example the terrain tile "BNCoast2.ter" has a matching bump tile "BPCoast2.ter" - all the bump tiles start with "BP".

To achieve what I wanted I only needed to copy three bump tiles, each of which was referenced by two different terrain tiles. I name the three copies so that all the terrain tiles which require a bump tile had their own individual one, with a matching basic name. I have made a new "terrain.cdf" with all of the tiles in.

However, in order to check which additional bump tiles needed to be made I cross checked the names of the existing terrain tiles and bump tiles. As a result I have found a few anomalies, and wonder if any of you can shed more light on the matter:

In the previous code a cross referencing system occurred. Each terrain tile had an associated bump value. If this value is -1 (false) the terrain tile did not use a bump tile. Otherwise the value is the ID of the associated bump tile. In my cross checking to match bump tiles with terrain tiles I found that five of the existing bump tiles were not associated with any terrain tile.
First there is a "BNRiver3.ter" but its bump value is -1 so it does not associate with "BPRiver3.ter"- and nor does any other terrain tile. The other four non-associated bump tiles are "BPForst3.ter", "BPForst5.ter", "BPForst7.ter" and "BPAlcty5.ter". Each one of these has a matching "BN*.ter" terain file, but with a bump value of -1 they are not associated.

The remaining mystery is that there is a "BPCoast7.ter" bump file. There is neither a "BNCoast7.ter" nor a "LRCoast7.ter" (low res) file, and in the code "BPCoast7.ter" is not referenced by any terrain tile.

Any info would be appreciated.

Jel

posted all my old analysis thread findings in your thread at The Gen, look there for the details

as far as the


Just another artifact I guess, as usual.. we have many of these leftovers probably from changes of the programming team during Microprose EAW development

Also to be sure sometimes we have had errors in packing our own .cdf's etc.

My new code has been posted at the Gen

Jel