Locomotive Databank

Content → Rocrail Server → Configuration

• General | Trace | Service | Automatic | Controller | R2Rnet | SVG | Finder | Command Mapping | Presets
• Locomotive Databank

The idea behind the LocoDB is to be able to access all locomotives on all computers with access to the same NAS/Cloud storage.
Even with an offline Rocview it will be able to access the locomotives and check their properties.

Without read and write access of the LocoDB this concept will not work.

The LocoDB path points to a directory which can be read and write by all users running Rocrail.
Every loco has its own directory named by its ID. Blanks are replaced with underscores; Blanks in IDs are discouraged and not supported.

This is an example of a LocoDB on a NAS:

LocoDB
├── BR01097
│   ├── BR01097.png
│   ├── BR01097.xml
│   └── DB01.png
├── BR120119-3
│   ├── BR120119-3.xml
│   └── m33535.png
.
.
.
├── RoT-1
│   ├── rot1.png
│   └── RoT-1.xml
└── V1002215
    ├── DB100.png
    ├── m3072.png
    └── V1002215.xml

Select a directory to open just one locomotive.

Open all locomotives in the LocoDB.

The "Workspace" and "Scale name" is used as selection in the LocoDB in case of automatically loading.

For selecting a locomotive from the LocoDB the "Workspace" and/or "Scale" field should contain a value which match the Plan properties.

With the "Locomotive database" option the export of the selected locomotives will be in the LocoDB.
The export will overwrite existing files.

Locomotives will be automatically loaded from the LocoDB if following is all true:

1. No local locomotives are defined.
2. The Locomotives database path exists and is accessible.
3. The Plan properties contains a selection by Workspace and/or Scale-Name.
4. Locomotives in the LocoDB matches the Plan properties criterium.