genetapa 0.97
2/4/2005

Quick instructions: there's an Spanish FAQ, and multiple examples in all
versions. Try to make sense out of them; start taking a look at the demos
In its basic usage, each line is a duple [4-letter-label,number-of-repetitions] 
representing a road segment(around 200m), except kmXX, prtX, sprn, meta, 
slda,avtl, time, paso, gaso, pnel and bner which indicate objects and/or 
hot points associated with the next segment. There can be only one 
object/point per segment. For these labels, '0' means insert hot point
but not object, '1' means object AND hot point (except for km N banners), 
'2' means only object, no hot point, and '3', for km N banners, means 
object AND hot point. '1' is default. 'pprf' is a stage profile indicator, 
which helps building the .sb file. 'jump' allows building circular circuits.

New segments for pave: pave, pv04, pv08, pv12, pv11/p11i/p11d

Since v0.96b, you can import bin fragments from existing files. This is
meant for reusing the original 3D races. The idea is to import fragments
from those. See library.txt for examples. It's easy to understand, just 
two commands: 'load' and 'inse'.

You'll also need 'leetapa', that generates a .def file from a .bin stage. It tells
you which segments there are in the .bin, and gives information about distance,
altitude and direction (N-North, E-East, S-South, O-West) every 5 kms or so, so
you'll know what you import.

For loading a file, this must be in the folder where you run genetapa, or under
the 'etapas/' subfolder. 

Also, starting with v0.96b, genetapa reads information about objects from .trm files
in the 'tramos/' subfolder. This is fully backwards compatible. Just rerun genetapa 
on your old stage definitions and you'll have the same stages but with objects in 
most segments.

(c) Allroch
http://www.angelfire.com/games5/allroch/
allroch@yahoo.com
