[Weter]

How could be instead?
Else, they say, MSTS (don't know about MSTS) reads files from their end.
So bottom coupler block will be applied to front coupler, the upper-to rear coupler.
It has sense to investigate that all and describe in manual, for avoiding such experiments in future.

[R H Steele]

 Elmo313, on 29 July 2021 - 09:22 AM, said:

Absolutely Ram. I've started rearranging things in the ORTS .eng file and everything now works. It seems position of statements makes a difference. In the ORTS file, the include statements work if they are in the same order as the (MSTS?) .eng file statements, from my experience.

Douglas

You've learned from experience, and you are correct. Although, it does say this in the manual...not to clearly, but it is there. Also, any MSTS parameters that are contained in blocks...within open and closing brackets must also be within open and closing brackets in OR include files. Follow the order of data in the MSTS eng or wag file and you seldom will go wrong.

[DirtyRam]

 R H Steele, on 29 July 2021 - 10:40 AM, said:

You've learned from experience, and you are correct. Although, it does say this in the manual...not to clearly, but it is there. Also, any MSTS parameters that are contained in blocks...within open and closing brackets must also be within open and closing brackets in OR include files. Follow the order of data in the MSTS eng or wag file and you seldom will go wrong.

For sure, Engine Wagon file Layout. In case you don't know Doug, and others
https://www.coalston...mat/#top-diesel
This is what we go by, excellant Open Rails resource. There are 2 different ways of doing these, with and without the Open Rails folder. I personally have never used that folder. If you still want to run MSTS etc. then you use the folder. I use the Open Rails folder in the routes, root folder of course. Heres an example of my .ENG file,

Wagon ( F40PH-6401Ren
WagonShape ( F40PH-6401Ren.s )

Include ( "..\\Common.ORPower\\Pass\\Mesh\\MeshCTSLIVIAF40PH2DRebuild.inc" )
Include ( "..\\Common.ORPower\\Pass\\Couplers\\CouplerPassengerAARTypeF.inc" )
Include ( "..\\Common.ORPower\\Pass\\Brakes\\BrakesCompIndependentSmallSinglePipe110PSI.inc" )
Include ( "..\\Common.ORPower\\Pass\\BrakePipeVolume\\BrakePipeVolume56ft.inc" )
Include ( "..\\Common.ORPower\\Pass\\BrakeForceComp\\BrakeForceComp134t.inc" )
Include ( "..\\Common.ORPower\\Pass\\ResistanceSE\\ResistanceVIAF40PH2DRebuild95MPH.inc" )
Include ( "..\\Common.ORPower\\Pass\\Lights\\LightsVIAF40PH2SLI.inc" )
FreightAnim ( 6401FA.s 1 1 1 )
Include ( "..\\Common.ORPower\\Pass\\Sound\\SoundVIAF40PH2EngK3LHEP.inc" )
)

Engine ( F40PH-6401Ren
Wagon ( F40PH-6401Ren )

Include ( "..\\Common.ORPower\\Pass\\Exhaust\\ExhaustVIAF40PH2SLI.inc" )
Include ( "..\\Common.ORPower\\Pass\\EngineInfo\\EngineInfoVIAF40PH2D.inc" )
Include ( "..\\Common.ORPower\\Pass\\Traction\\TractiveEMDF40PH2DHEP95MPH.inc" )
Include ( "..\\Common.ORPower\\Pass\\PrimeMovers\\EngineEMDF40PH2DHEP.inc" )
Include ( "..\\Common.ORPower\\Pass\\AirCompressors\\AirCompressorVIAF40PH2.inc" )
Include ( "..\\Common.ORPower\\Pass\\BrakesPass26LSinglePipe110psi.inc" )
Include ( "..\\Common.ORPower\\Pass\\Brakes\\BrakesDynVIAF40PH2Blended.inc" )
Include ( "..\\Common.ORPower\\Pass\\AntiSlipThrottlePowerDown.inc" )
Include ( "..\\Common.ORPower\\Pass\\EngineMonitors.inc" )
Include ( "..\\Common.ORPower\\Pass\\Controllers\\BrakeCompContBlendedEMD645Pass110psi.inc" )
Include ( "..\\Common.ORPower\\Pass\\Fuel\\FuelLevel1500.inc" )
Include ( "..\\Common.ORPower\\Pass\\Cabs\\CabVIAF40PH2SLI.inc" )
Include ( "..\\Common.ORPower\\Pass\\Sound\\SoundVIAF40PH2CabK3LHEP.inc" )
Name ( "VIA 6401 F40PH-2D Rebuilt Renaissance" )
Include ( "..\\Common.ORPower\\Pass\\UnitText\\TextCTVIAF40PH2DrebuildsSLI.inc" )
)

It's in a constant state of WIP,
Mike

See, just noticed an error or 2. Haa

[Weter]

Excellent.
This IS, what I would learn and advice for you, Douglas, to search.
I will practice with this example soon.

[Elmo313]

 DirtyRam, on 29 July 2021 - 12:48 PM, said:

For sure, Engine Wagon file Layout. In case you don't know Doug, and others
https://www.coalston...mat/#top-diesel
This is what we go by, excellant Open Rails resource. There are 2 different ways of doing these, with and without the Open Rails folder. I personally have never used that folder. If you still want to run MSTS etc. then you use the folder. I use the Open Rails folder in the routes, root folder of course. Heres an example of my .ENG file,

I'm quickly learning some important things; order matters and a lot of questions can be answered by careful reading on Coals to Newcastle, which is where I found the answer to this little conundrum.

I usually use an OpenRails folder while I'm setting up an engine or wagon for ORTS. When I've finished entering data and have everything tested and working, then I keep the commented file as a backup, and move the ORTS file in to the main file folder. Helps me keep track of what I'm doing and what is/is not working.

Dougas

[Elmo313]

 R H Steele, on 29 July 2021 - 10:40 AM, said:

You've learned from experience, and you are correct. Although, it does say this in the manual...not to clearly, but it is there. Also, any MSTS parameters that are contained in blocks...within open and closing brackets must also be within open and closing brackets in OR include files. Follow the order of data in the MSTS eng or wag file and you seldom will go wrong.

As frustrating as learning from experience can be, it is rewarding. And as corny as this may sound, the more I learn the more I want to learn. Thanks to searching through posts, I've learned about ConTEXT and the MSTS highlighter, which makes life so much easier. I'm enjoying researching railroadiana (is that a word?). I've found some good sources of dimensional data, mainly for CN steam and diesels, and hope to start modeling soon. Been an interesting ride.

Douglas

[Weter]

Theoretic base is good start.
Further, you will fill the gaps of that mesh with concrete knowledges.
But understanding principal things is essential.