Quote:

Besides this, I'm not really sure how to use the other programs to try to improve the mapping.

Quote:

Info on how to compile smooth is in the file INSTALL.
Info on the authors is in the file AUTHORS
ChangeLog contains the changes in reversed chronological order
This program is licenced under the GPL


smooth is a program used to help in the creation of maps for Exult
games. Exult is an engine to run Ultima 7 on modern hardware but can
run self-made games as well.

The creation of a map is a fairly complex thing to do, since the map
is 24576x24576 pixels. Fortunately, the map is made of reused chunks
which are squares of 128 pixels, so we need only a map of 192x192
chunk. There is a hard limit of chunks that can be used of 256. It
makes sense then to use an indexed image (less than 256 colours) with
reused colours, each representing a chunk and to convert this image
into a map, thanks to an association chunk <-> colour. The tool to do
this is called mockup and can be found at:
http://si-french.sf.net/tools/

It is noteworthy that even creating such a map is a difficult
task. Either a lots of manual work in done on the image itself, or a
simple image is created, but the real map needs to be adjusted with
ExultStudio. In order to reduce this work and to automate tasks (thus
reducing errors), smooth has been created. smooth takes an image as
input and creates an image as output, making automatic changes thanks
to a config file. The changes that can be made for instance are:
* randomizing: to make a area (based on colour) appear in random colour
(from a pool set in the config file). Useful for forest for instance
* streamlining: transform a single colour representing a road into
adjusted colours to reflect the changes in direction. Usually, a chunk
for a east-west road piece is different than one for a north-south
piece.
* smoothlining: when 2 colours are beside each other, representing 2
chunk types, it is better if the transition from one to the other is
smooth. For instance, water and land would look better with a shore
between the two.

smooth uses a config file to know how to convert one colour into
another based on what is around or on what change to make.
Each section starts with [name]. A comment starts with a ';' or a '#'.
Each line in a section starts with the slave colour, that is, the
colour to transform into something else. This something else is found
somewhere in the rest of the line. Which one is picked depends on
which section it is in, and what the surrounding factors are or just
chance, as in the randomize section.

Most of the time, the order in which the colours are put in the config
file matter. If you happen to change the colours in the config file,
make sure you adapt accordingly the file "mapping.txt" from mockup.

# Config file for smooth
# each section starts with [pluginname]
# libsmooth_pluginname.so is consequently loaded
# comments start with # or ;
# empty lines are ignored
# "*" signifies whatever chunk. Used mostly for trigger.
# For instance, "[stream] slave * chunk1 ... chunk15" will replace slave by chunk1 or chunk2 ... or chunk15 no matter what trigger chunk is around
# while "[stream] slave master chunk1 ... chunk15" will replace slave by chunk1 or chunk2 ... or chunk15 only if it is beside trigger chunk

; colours used in rough.bmp: 725E0C 494949 878787 3C9134 102ABC 664747

# randomize replaces slave with one of master(s) chosen randomly
# format: slave (master)+

[randomize]
; we are allowed to replace slave by itself
3C9134 3C9134 931029 1B3D5F 349C1D

; but we are not obligated to do so
;102ABC F3FF1F 932029 1C3D5F 319C3D 654F2C


# stream replaces slave if beside trigger with one of masters chosen
# depending on position of other slaves around
# format: slave master 0 1-n 1-e 2-ne 1-s 2-ns 2-es 3-nes 1-w 2-nw 2-ew 3-new 2-sww 3-nsw 3-esw 4
# see README.Stream for more information

[stream]
; slave master 0 1-n 1-e 2-ne 1-s 2-ns 2-es 3-nes 1-w 2-nw 2-ew 3-new 2-sww 3-nsw 3-esw 4
; for water -- a bit of trigger will show on master so we must be sure
; slave is beside trigger
;000000 2340B3 101111 111112 111113 111114 111115 121111 121112 121113 121114 121115 121116 131111 131112 131113 131114 141111

; for large road -- we don't care what trigger is
;333333 * 601111 611112 611113 611114 611115 621111 621112 621113 621114 621115 621116 631111 631112 631113 631114 641111

;494949 * 010101 111111 212121 313131 414141 515151 616161 717171 818181 919191 A1A1A1 B1B1B1 C1C1C1 D1D1D1 E1E1E1 F1F1F1

494949 878787 010101 111111 212121 313131 414141 515151 616161 717171 818181 919191 A1A1A1 B1B1B1 C1C1C1 D1D1D1 E1E1E1 F1F1F1
# End of Config file - DO NOT REMOVE

$ ./smooth -c ~/u6test.txt -i ~/ultima6.bmp -o ultima6.bmp
*** glibc detected *** ./smooth: invalid fastbin entry (free): 0x08407370 ***
Segmentation fault (core dumped)