Trainstore
Zdravím všechny příznivce MSTS.
Jak jsem pochopil a doufám že správně, tak se musí v nové aktualizaci, kterou vydá pan Šemora přehazovat Adresář Global nebo soubor z tohoto adresáře "tsection.dat". Já tomu sice moc nerozumím, ale myslím si, že program Trainstore toto umožňuje bez větších problémů. Bohužel neumím anglicky, tak zde dávám část návodu v angličtině. Prosím někoho, kdo anglicky umí, aby se k tomu vyjádřil a osvětlil tento problém. Já si bez Trainstore nedovedu start MSTS představit, protože nabíhá během pár vteřin. Díky předem za rozbory. Kdo bude mít zájem mohu návod na ovládání poslat mailem.
76(&7,21'$7)LOH6ZDSSLQJ
The TSECTION.DAT file is a very important file in MSTS. It exists in the GLOBAL folder
within the MSTS folder. It contains all of the definitions for the track sections used within the
installation, apart from dynamic track sections. There was no provi sion made in the MSTS
design for multiple TSECTION.DAT files, so the one file generally has to contain all of the
definitions. In the early days of MSTS there were several conflicting TSECTION.DAT
extensions which were produced, and this caused problems when an installation contained
Routes which required conflicting specifications. Since then, the community has developed
the concept of the standardised TSECTION.DAT file, which allows new track definitions to
be added in a way which is still compatible with the original MSTS track sections and later
developments.
However, there are still requirements for some Routes which use a non -standardised
TSECTION.DAT. This might be because the Route is an older Route which was developed
before the standardised TSECTION.DAT was developed, or rarely, the Route has not been
developed with the standardised TSECTION.DAT file in mind. Also, Route developers,
sometimes need to work on Routes with track sections which are not yet standard, so they are
not included in the standardised TSECTION.DAT file. They therefore need to change the
TSECTION.DAT file as they move from Route to Route.
The actual TSECTION.DAT requirements for any Route may differ, but generally the
following guidelines can be followed. If the Route has been developed with the standardised
TSECTION.DAT file, then a TSECTION.DAT file with that Build Number, or a higher one,
will be compatible with it for simulation and editing. Earlier Routes, which do not use any
extensions to the basic track sections supplied by MSTS will also be compatible for
simulation. If you are editing a Route, it might be safer to always use the TSECTION.DAT
file that was used when the Route was created. A good source of information for this can be
found at the XTracks web site on the page
http://www.geocities.com/okrasaghia/tk/documents/routes.htm
The TSECTION.DAT file swapping in Train allows you to specify : -
· A ‘default’ TSECTION.DAT to be used when you use ‘Unstore Everything’ or for any
Route for which you have not specified a TSECTION.DAT.
· For any Route, a specific TSECTION.DAT file, and how it will be used on unstoring
that Route, in Simulation mode and in Maintenance mode.
When multiple Routes are being unstored, processing is included which automatically checks
for conflicting TSECTION.DAT requirements and provides you with an easy visual method
of removing the conflicting Routes.
The TSECTION.DAT file processing is optional. It is only invoked when you have specified
a default TSECTION.DAT file, and at least one Route specifi c TSECTION.DAT file.
You do not need to use this feature unless you already swap TSECTION.DAT file with your
installation, and you want to automate this.
Page 62 15 November 2004 Train Store
6HWWLQJXS76(&7,21'$76ZDSSLQJ
6HWXSD76(&7,21'$7/LEUDU\
Make a list of which TSECTION.DAT files you want to use, and where you are going to store
them. It is important that once you have specified the TSECTION.DAT files to use in Train
Store, they are not removed from those locations. So, it is probably better to set up a particular
folder, or group of folders to accommodate them. Note, this is not essential, Train Store will
allow you to keep the files DOPRVW anywhere, and there is nothing restricting the files to one
location. But, it is probably easier to remember what you are doing if everything is in one
place.
The files that you specify must :-
· not be located anywhere within the Train Store Storage folder
· must not be the actual GLOBAL\TSECTION.DAT file
· must not be the TSECTION.DAT file within a Route (MSTS uses this to store the
dynamic track information).
WARNING: When setting up this library, if you move, or copy files to do this, you must
QHYHU overwrite a TSECTION.DAT file anywhere within the MSTS installation. It is not
necessary, and will damage your installation.
The Train Store TSECTION.DAT processing will accept files with any name, (it does make
very simple some format checks to make sure that the file looks like a TSECTION.DAT file)
so if you wish, you can store your TSECTION.DAT files in one folder with different names
(e.g. TSECTION 00019.DAT, TSECTION 00023.DAT etc.) On the other hand, you may
prefer to store files named TSECTION.DAT in separate folders which denote their Build
Number, or origin. (e.g. Build0019\TSECTION.DAT, Build00023\TSECTION.DAT etc.)
You can use whichever method you are more comfortable with.
6SHFLI\LQJWKH6\VWHP'HIDXOW76(&7,21'$7
Choose 7RROV2SWLRQV6\VWHP'HIDXOW76(&7,21'$76HWWLQJV from the menu. This will
open the 6\VWHP'HIDXOW76(&7,21'$73DUDPHWHU window.
Enter the full path and name of the file that you want to specify to be used for the System
Default TSECTION.DAT file. Use the Path button if you wish, to navigate to the file that you
want to use. This will open the &KRRVH76(&7,21'$7)LOH window
Train Store 15 November 2004 Page 63
Notice that the file name you choose does not have to be TSECTION.DAT. If you chose to
use the convention of keeping your TSECTION.DAT files in one folder with different names
to differentiate them, this where you would choose for example
‘TSECTIONBuild00023.DAT’. Train Store takes care of t he name change when it swaps the
file into the GLOBAL\TSECTION.DAT location.
When you have chosen the file, click on the 2. button, the window will be closed and the
path and file name you chose will be entered in the Path field in the 6\VWHP 'HIDXOW
76(&7,21'$73DUDPHWHU window.
You can enter a description in the form if you want to make any special note about this
setting. The description is stored with the Train Store data, and will be displayed whenever
information about this TSECTION.DAT setting is displayed. No changes are made to the
actual TSECTION.DAT file.
Now choose the actions to be used. The actions in this form refer to ‘Unstore Everything!’, or
to Routes which do not have their own TSECTION.DAT specification. Notice that there are
two sets of actions, one for use when a Route is being unstored in Simulation mode, and the
other when a Route is being unstored in Maintenance mode.
Page 64 15 November 2004 Train Store
The Action settings which are available are : -
· Use any TSECTION.DAT.
· Use any TSECTION.DAT with this Build No. or a higher one. The Build No. from the
TSECTION.DAT file that you have chosen is shown. In the case of early
TSECTION.DAT files where there was no Build No, the file’s date and time details
will be displayed instead of the Build Number. All TSECTION.DAT f iles without
Build Nos. are considered earlier than those with Build Nos.
· Use this specific file.
Click on the 2. button to update the settings and close the form.
6SHFLI\LQJWKH76(&7,21'$7IRUD5RXWH
You only need to specify a TSECTION.DAT file for a Route if it has requirements that will
not be met by the Default TSECTION.DAT specification.
Choose 5RXWHV76(&7,21'$76HWWLQJV, from the menu, or from the right-click context
menu. This will open the 76(&7,21'$73DUDPHWHUV form.
The entries on this form are similar to the entries on the System Default TSECTION.DAT
Parameters form except that these parameters refer only to the Route you have selected.
Enter the path and file name to the required TSECTION.DAT file, or else click on the 3DWK
button to open the &KRRVH76(&7,21'$7)LOH window, and navigate to the file you want
to use.
Enter any Description for the settings.
Enter the Action for Simulation and Maintenance Modes.
Click on the 2. button to update the settings and close the form.
Train Store 15 November 2004 Page 65
8VLQJWKH76(&7,21'$76ZDSSLQJ
There are no special actions that you need to take once you have set the TSECTION.DAT
swapping parameters. If you add new Routes, be sure to review their requirements, and add
parameters for them if necessary. Remember, you only nee d to add Route specific parameters
if the System Default TSECTION.DAT settings are not suitable for the Route. The
TSECTION.DAT swapping processing takes place automatically whenever Train Store
surveys the MSTS installation in preparation to moving files. The processing checks to see if
there are any conflicts in the Route specifications for the Routes which are going to be
unstored. Conflicts can only occur if more than one Route is being unstored, and if more than
one Route has a specific TSECTION.DAT setting. Even then, a conflict may not arise
because the specific settings which will be in operation may be compatible. If there are
conflicts found, Train Store will display the 5HVROYH &RQIOLFWLQJ 76(&7,21'$7
6SHFLILFDWLRQV window.
This lists each Route which is being unstored, together with the Build No. from the
TSECTION.DAT specified for it (either specifically, or as a result of the System Default
TSECTION.DAT specification), and the Action which has been specified. The actual file
name being used is also displayed (to the right of the Action, but it is not visible in this
screenshot).
On the left hand side of the window there are a series of checkboxes. Each one ticked means
that the Route is selected to be unstored.
An asterisk (
) next to it means that the Route is in conflict with at least one other Route. The
list is displayed in the order of descending conflicts. i.e. the Route at the top of the list has the
most conflicts.
To resolve the conflicts, simply uncheck the checkbox against one or more Routes which have
conflicts, so those Routes will not be unstored, until no conflicts remain. When this happens
the asterisks disappear, and the information in the top of the window changes. For example in
the situation above, if the first Route is unchecked the result is as follows
Page 66 15 November 2004 Train Store
There are no conflicts remaining, and the 2. button is enabled, so you can go ahead and the
remaining 4 Routes will be unstored with no conflicts. The TSECTION.DAT file to be used
will be the file from the 3rd Route in the picture.
The conflicts can be resolved in any way that you prefer, for example, in the above pictures, if
you really wanted to retain the first Route in the window, you would need to uncheck the
second and third Routes which are conflicting. The result would be as follows
Notice in this case that a different TSECTION.DAT has been selected, which is compatible
with the remaining Routes.
When you are satisfied with the settings, click on the 2. button, and the unstore processing
will go ahead, unstoring all of the routes which were still selected to be unstored.
Ty nesmyslné znaky jsou obrázky.
Kdo by měl chuť, mohl by prosím vypracovat návod.
milo
án Šemora ohľadne Letohradu (mám na mysli koľaje) je to tam už nafest?