I have two different routes sig files (SIGCFG.dat and SIGSCR.dat) and I wish to combine them.
How do I do that?
Can it be done in ROUTERITER?
Thanks,
John from New Zealand
They are two distinct files that preform different function for the signals. Do not believe you can combine them.
Geary "Mr. Hart" Gerhardt - Owner and CEO of Hart Rail Lines, Hart Commuter Railways, and Hart Rail Cars. Also the defunct Hart Electric Transit.
Its Your Train Sim World, sim as you please.
Here are the instructions from TSUtil to modification the signaldefinitions and merge two routes.
25) Replacement/Modification of the signaldefinitions of a route
This function ('chgsig') may be used to replace or modify signaldefinitions within a route. Changes are
controlled by a special command-file, which has to be created. This file must be placed together with the
target-signalfiles (sigcfg.dat,sigscr.dat) in a additional directory within the route-definition.
This command-file contains a set of modification-commands for each signal, which is used within the route.
The syntax of these commands are decribed in Annex D.
The result of this modification is written to the '/newroute'-directory. The new signal-files are also copied
to this directory, so that the current signalfiles are replaced with the new ones.
This function may also be used to delete signals or rename signal-shape-definitions (compare to Annex D).
19) Merge a route-definition into another route
This function ('merge') creates a common route from two Route-Definitions. It merges another route into
a basis-route. In order to get no errors, the following conditions/considerations have to be met:
- Both routes must not contain a common tile-definition.
If a common tile-definition still exists, it is ignored from merge-route and not used.
This may lead to inconsistencies of the databases (*.tdb,*.rdb,...) and will raise
appropriate error-messages.
This concerns to LO-Tile-Definitions, too.
- The basis-value for dynamic tracks has to be the same and must correspond to the current
global 'tsection.dat'-file.
While merging, Shape-, Texture-, Terrtex- and Sound(sms/wav)-files, which are necessary for the common route
and which are not defined in the basis-route, are copied. This is a critical process, because the basic-route
may contain other shapes/textures with the same name. These files are NOT copied to the 'newroute'-directory.
Signal-definitions are also merged. However, if a signal-name already exists in the target-route, the
definition is NOT transfered. So, there may be problems in signalling, if this occurs.
Merging two sigscr files is pretty easy to do manually, just make sure there are no duplicates. Sigcfg files are a bit more diffuicult, as not only must there be no uplicates, but counts must be maintained, and the structure is a bit more rigid
I did this years ago manually to a long pulled from the F/L route. Took me a few times to get it right. I did B&O, C&O and NW signals in one route. It's a bit tedious manually. But I know of no other way personally to do this.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We do not share information about our users with anyone. For additional details, refer to our Privacy Policy.
By clicking "I UNDERSTAND" below, you consent to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment