[cr-stagg]

When there is an OpenRails folder used for a complete engine file with different parameters for ORTS,
the TSRE-CE shows a different Name for the ENG than the ORTS menu shows.

Example.
A:\MSTS\TRAINS\TRAINSET\BNSFC337\C33-7.eng
Name line: Name ( "BNSF C33-7 @ 5132 POR" )

A:\MSTS\TRAINS\TRAINSET\BNSFC337\OpenRails\C33-7.eng
Name line: Name ("#OR BNSF C33-7 5132")

ORTS Menu display:
https://dl.dropboxusercontent.com/s/7ijrtm7kcea9hu8/C33-ORTS.JPG?dl=0

TSRE-CE Display:
https://dl.dropboxusercontent.com/s/xej7my8i4ys6cty/C33-TSRE.JPG?dl=0

Note that OTRS displays the Name line from the ENG file in the root folder not the one from the ENG file in the Sub-folder.
Where as the TSRE-CE displays the Name line fron the ENG file in the Sub-folder.


From the OTRS Manual. Note the last sentence which I have bolded:

Quote

8.14.1 Modifications to .eng and .wag Files
In the preceding paragraphs many references have been made to OR-specific parameters and tables to be
included in .eng and .wag files. MSTS is in general quite tolerant if it finds unknown parameters and even
blocks within .eng and .wag files, and continues running normally. However this way of operating is not
encouraged by the OR team. Instead, a cleaner approach, as described here, has been implemented.
Within the trainset folder containing the .eng and .wag files to be upgraded, create a subfolder named
OpenRails. Only OR will read files from this folder. Within this subfolder a text file named xxxx.eng or
xxxx.wag, where xxxx.eng or xxxx.wag is the name of the original file, must be created.

This new file may contain either:
• all of the information included in the original file (using (modified parts where desired) plus the ORspecific parts if any, or:
• at its beginning only an include reference to the original file, followed by the modified parts and the
OR-specific parts. This does not apply to the Name() statement and the Loco Description Information,
where in any case the data in the base .eng file is retained.

[Goku]

And I think OR behavior it is stupid.
If loco creator decided to change the name, it should be this way. If he wanted to have the same name, it should stay the same in OR ENG.

[cr-stagg]

Goku, on 19 July 2018 - 08:59 AM, said:

And I think OR behavior it is stupid.
If loco creator decided to change the name, it should be this way. If he wanted to have the same name, it should stay the same in OR ENG.

I don't agree with your term of "stupid" but I do think it is "short sighted". By displaying the "changed" Name the user has information that he can use to identify a made for OR ENG.

Be that as it may be. Your implementation hinders the user from finding the ENG after creating the Consist in the TSRE-CE.

[Goku]

I will wait for expatiation why it is done this way in OR.