You can save some scene data for particular scenes into a file so that you can reload the preferred settings every time you want to run this territory. The following items will be saved
- Triggers, for instance buzzers.
- Entry/exit’s favored direction.
- Visible automatic signals.
- Permissive signals types.
- Option for 2-step route cancel.
- Time factor.
Note: the simulator needs to have started, and some of the data can only be set when it is running, but it may be stopped when saving the data.
Since it is critical that the configuration data match the territory it belongs to, unique identifiers in the territory file are used to make sure of that. If there is a territory update that is more than of cosmetic nature, this new file will have a different identifier, so the configured data will not load if you have updated the territory with a newer version since then. This will also be the case if there is a switch from one version to another within the same territory file, after you have received a registration code affecting this territory, e.g. from FREE to STANDARD.
The system keeps track of the territory file name, configuration file name, and the identifier. This means, while you can usually move and rename the files as you wish, you need to keep the location and names of the files – or restore to the original conditions – to make the reload work.
If the territory file does not have this unique identifier, saving of the scene configuration is not possible and the option for that is disabled.
Territory files may not have these identifiers in the FREE version, but the STANDARD and PREMIUM version will have them.
Tip: to keep it organized it is recommended to dedicate a directory/folder for your configuration files. You can locate and name the files and folders any way you like. Depending on the OS system you have and how you run it, you may have to tinker with the write access to the folder in which you want to place your files.