[kamel]

Congratulations

[kamel]

roeter, on 31 May 2014 - 02:06 AM, said:

The recently introduced option to have OR-specific sigcfg.dat and sigscr.dat files have opened up the possibility to create new, OR-specific signalling functions.
The first of such functions have now been created and are available in release 2266.

Here is a description of what these are and how they work.
First, for those who do not yet know, details of how to set OR-specific sigcfg.dat and sigscr.dat files.

How to set OR specific signal files.

The following steps will create OR-specific signal definition files :

• Create a directory named OpenRails in the route's main directory.
  
• Copy the existing sigcfg.dat file to this new OpenRails directory.
  Do not change the file name or extension.
  
• Check the sigcfg.dat file for all required signal script files (defined in Scriptfiles statement at end of sigcfg.dat file).
  Copy all required script files to the OpenRails directory.
  Do not change the file name or extension.

Please note that the OR-files are full replacement files - these are not 'include' files or additional files, but the OR-specific files must contain all required definitions for signal types and signal shapes, as well as all required scripts.

Important note.
Because for route editing we still depend on the MSTS route editor, if any new signal types or signal shapes are introduced in the OR-specific files, similar named entries must also be included in the original MSTS files, otherwise these new signals can not be placed in the route.
If a new signal has an OR-specific signal function type, the definition in the MSTS files must be set to one of the original signal function types. When the route is still used in MSTS, care must be taken that this signal type does not conflict with existing signalling. If the route is no longer used in MSTS, then obviously this does not matter.

New signal types and signal functions will be detailed in the nexts set of posts.

Regards,
Rob Roeterdink

thanks