[Csantucci]

I get following problems signalled:
Traffic file:
- if the Traffic_Definition () parameter contains blanks, TSRE5 does not insert double quotes at ben and end of string;
- before the list of Service_Definition the parameter Serial() is missing.
Activity file:
- parameter NextServiceUID () before Traffic_Definition is not incremented
- within the Traffic_Definition block lines Service_Definition (?) and UiD() are not created.

I haven't checked this assertions. Maybe not all of these parameters are needed for OR, but some are for sure, and maybe they are all needed for MSTS.

[Goku]

Thanks. I'll look at it.
But probably next month.

[Csantucci]

There is also another message: if writeTDB is set to true, when you save an activity the .tdb, .rdb, .tit, .rit files are modified and the route's tsection.dat is almost emptied.
I suggested to set writeTDB to false to work with activities and that's OK, but it's not comfortable to have to check the settings file and if needed edit it everytime you switch from activity editing to route editing and vice-versa.

[Goku]

1. There will be separate option to save only activity data and not route data.
2. The tsection.dat bug when saving route data is known and it requires implementing TDB conversion in TSRE like Horace.

[Csantucci]

Further issues found about MSTS compatibility of TSRE AE have been reported:
In Tr_Activity_Header of file .act:
1) RouteID must be equal to the value shown in the route's .trk file and not to the name of the route folder
2) CompleteActivity must be 1 and not 0
3) The PathId line is missing

In the .srv files generated with TSRE5 the upper cases in the consist names are not considered. MSTS is case sensitive.

[Goku]

Thanks for all the bug reports.

Quote

In the .srv files generated with TSRE5 the upper cases in the consist names are not considered. MSTS is case sensitive.

Since when? I had huge problems with linux support for TSRE, because MSTS is not case sensitive (in most places), so TSRE uses only lowercase letters to solve this issue. It will not be easy to "fix" it.

[slipperman]

Hi,
May I confirm that if the consist name entered in the Train_Config entry in a .srv file is not the same, case-wise, as the TrainCfg entry in the .con file, the loco is shown as UNKNOWN when selecting the activity from the MSTS Route & Activity selection screen. However, this does not prevent the activity from running when the START button is pressed. Incidentally, the case of these entries does NOT need to match that of the actual consist file name.

Cheers,
Ged

[Goku]

Quote

1) RouteID must be equal to the value shown in the route's .trk file and not to the name of the route folder

And RouteID in trk file can be different than route directory name?
What I think about values in .trk file:
- RouteID: is directory name.
- filename: is name of the route files.
- name: is the name displayed.

[James Ross]

Goku, on 10 January 2018 - 08:59 AM, said:

And RouteID in trk file can be different than route directory name?

It is common practice to use the directory name, and the MSTS route editor defaults to the directory name for both RouteID and FileName (despite the in-box routes not following this pattern).

However, as best as I can tell, MSTS does not care whether the RouteID matches the directory name. Even the activity editor happily uses whatever value is in the TRK when creating a new ACT.

If the TRK and ACT match (case sensitively), the activity will load, even if the value has no relationship to the route's directory or anything else. If they don't match, it'll crash loading the activity.

Goku, on 10 January 2018 - 08:59 AM, said:

What I think about values in .trk file:
- RouteID: is directory name.
- filename: is name of the route files.
- name: is the name displayed.

Apart from the point above about RouteID, this looks correct.

[Goku]

So, why people change the routeid value? Is it used elsewhere?
Or is it only the matter of case sensitive?

Anyway, the RouteId from TRK file can be used by TSRE.