I've been working on a complete overhaul of all my content, making copious use of include files and such. However, I have found that the consist editor in TSRE V0.698.1 has a significant problem interpreting include statements which is causing many parameters inside said include files (in my case, this means things like the size, mass, coupler type, etc.) to go missing in the editor:
tsre issue.JPG (22.49K)
Number of downloads: 1
If I look at the log, it's full of claims that every single include file I'm using does not exist, aside from the one include file which is being referenced by the engine file. It's completely lost the include files which are referenced by that include file!
[i] "e:/or content/miniroutes/allcommon/trains/trainset/mrl_emd_sd70ace/openrails/mrl_sd70ace_4300.eng" [i] converting to UTF16 [i] "e:/or content/miniroutes/allcommon/trains/trainset/mrl_emd_sd70ace/openrails/presets/mrl_sd70ace_4300_psc.inc" [i] converting to UTF16 [i] "e:/or content/miniroutes/allcommon/trains/trainset/mrl_emd_sd70ace/mrl_sd70ace_psc.inc" not exist [i] "e:/or content/miniroutes/allcommon/trains/trainset/mrl_emd_sd70ace/../../../common.psc/couplers/gradee_coupler_18cm_psc.inc" not exist [i] "e:/or content/miniroutes/allcommon/trains/trainset/mrl_emd_sd70ace/../../../common.psc/locomotives/wagon_settings/sd70ace_214t_wagon_settings_psc.inc" not exist
All these .inc files do exist, but TSRE is looking in the wrong folders; TSRE is not interpreting the folder navigation syntax in the same way that Open Rails interprets it. In Open Rails, an include file must reference other include files relative to its actual location on the disc, but in TSRE, an include file must use include statements relative to the location of the engine/wagon file which is using the include file. This inconsistency of interpretation is a major issue, which is making TSRE incompatible with my setup, even though Open Rails is compatible.
I have observed some configurations of files where this isn't an issue at all because all include statements are inside the .eng or .wag file, in which case Open Rails and TSRE will interpret the statement the same way. However, my setup has include statements inside of include files, which immediately causes TSRE to fail, while not causing any issue for Open Rails itself.
To explain how this affects my case of MRL #4300, MRL_SD70ACe_4300_psc.inc is in a subfolder of the OpenRails folder called "Presets" (which, as per the name, contains preset configurations of rail vehicles.) Thus, it's actual location is TRAINS\trainset\MRL_EMD_SD70ACe\OpenRails\Presets. However, it appears that TSRE is acting like it is located in TRAINS\trainset\MRL_EMD_SD70ACe\OpenRails, IE: the same folder where the engine file, MRL_SD70ACe_4300.eng, is located.
This causes problems when the interpreter gets to an include statement inside MRL_SD70ACe_4300_psc.inc. For example,
include ( "..\\..\\..\\Common.psc\\Locomotives\\Wagon_Settings\\SD70ACe_214t_Wagon_Settings_psc.inc" )
This is the file where the mass, adhesion, brakes, and more, are stored. It is actually located in the folder TRAINS\trainset\Common.psc\Locomotives\Wagon_Settings. However, because TSRE thinks MRL_SD70ACe_4300_psc.inc is one folder higher up than it actually is, TSRE believes SD70ACe_214t_Wagon_Settings_psc.inc should be located in TRAINS\Common.psc\Locomotives\Wagon_Settings.
I can demonstrate TSRE's mistake by editing MRL_SD70ACe_4300_psc.inc to only look two folders up, rather than three. (among other edits) This will make it look for the files as if it were in the same folder as the engine file is, even though it is not.
include ( "..\\..\\Common.psc\\Locomotives\\Wagon_Settings\\SD70ACe_214t_Wagon_Settings_psc.inc" )
Suddenly, TSRE will be able to find the files it was looking for, and more of the stats show up.
tsre issue kinda fixed.JPG (24.18K)
Number of downloads: 1
There's the expected weight (that's 214 us tons, but TSRE still shows "t" rather than "t-us"), size, and couplers.
Now, there's still no mention of the power, speed, nor tractive effort, but that's just because I'd need to edit some other files which I would rather not do at the moment.
Also, this "solution" doesn't work at all in the sim itself, due to the fact that Open Rails interprets these files differently than TSRE.
open rails issue.JPG (25.26K)
Number of downloads: 1
Thus, in my situation, I simply cannot use TSRE's consist editor effectively due to this one major flaw. I really appreciate what the TSRE consist editor lets you do, but it really should have file interpretation that works exactly the same as Open Rails.
For now, I'll have to reformat my files to match something that will work for both OpenRails and TSRE, which is not fun when there are over 100 files to work out.