Problems With Trainsimulations BNSF Scenic Subdivision Demo Route

[tlowe]

Hi Guys, I have been playing around with the NumWheels values. I found that when I changed the values as shown below in the articulated sets, I didn't have any warnings at all in the Whatgoesup activity.

3 car sets

car 1 = "NumWheels ( 3 )"
car 2 = "NumWhees ( 2 )"
car 3 = "NumWheels ( 3 )"

5 car sets

car 1 = "NumWheels ( 3 )"
car 2 = "NumWheels ( 2 )"
car 3 = "NumWheels ( 2 )"
car 4 = "NumWheels ( 2 )"
car 5 = "NumWheels ( 3 )"

I am using the latest stable version of OR 1.5.1 with windows 11. That's all I changed. Let me know if it works for you.

Thanks, Tim

[meeshu]

Changed the NumWheels () statement value for each consist car to the equivalent to the number of axles for each car in the consist.

Ran the What Goes Up activity again under Open Rails New Year Mono Game 159.

Continue to get derailments for car 0-11, 0-31, 0-32, and 0-41 as before. Particularly in the vicinity of MP 1728, and also around and after MP 1726.

Note that the car *.wag files do NOT include the ORTS statements ORTSnumberaxles () and ORTSnumberbogies () with appropriate values entered for each statement.

Will run one more time using the ORTS statements and see what happens.

Maybe coincidence, or of no concern. But while viewing the rear of the activity train (3 key), I notice that the rear car occasionally jiggles rapidly side to side a bit. This possibly suggests a (slight) misalignment of track sections? Would track (slight) misalignment contribute to or even cause the car derailments?

EDIT:

Added ORTSnumberaxles () and ORTSnumber bogies () statements with appropriate values for each of the cars within the consist.

Re-ran the activity. But again got car derailments for cars 0-11, 0-31, 0-32, and 0-41.In fact the derailments may have been slightly worse with cars 0-11 and 0-41 derailing an extra time around MP 1730.

[R. Steele]

Maybe coincidence, or of no concern. But while viewing the rear of the activity train (3 key), I notice that the rear car occasionally jiggles rapidly side to side a bit. This possibly suggests a (slight) misalignment of track sections? Would track (slight) misalignment contribute to or even cause the car derailments?

Rapid -- jiggling - #3 camera movement when focused on the rear of the train has been observed in OR for sometime ( I can remember posts going back 5 or more years ) --- simply use Alt+PgUp to re-focus the camera on the actual wagon and the rapid movement will stop.

Use of the OR coded EOT device ( in the manual Section 8-18 --- Ctrl+F9 brings up the EOT list window ) will prevent this....perhaps someone with solid knowledge of how the #3 camera functions can explain this....I cannot.

[derekmorton]

I just delete the EOT to get rid of that problem.

[meeshu]

Comments noted. Thank you.

[peterman]

I just delete the EOT to get rid of that problem.

Hi Derek,

It's a lot easier to move the camera up one car. You'll still see the end of your train, including the EOT.

Peter

[oper190]

Just a point of information, I experienced the same, problem when using EOTs/FREDs in MSTS also. As posted, I also simply move back my 3 view one car.

When making my own FREDs I made them weight something in the 100lb range being that they have to be man-handled into place, and found that they would literally fly off the train. Had to make them 1ton to stay put. So I believe it is a combination of weight and size that causes that, as with a larger and heavier car it is not noticeable. Having just gotten off the AutoTrain earlier today, I know well how much shake and roll a car actually has when in motion. Me inner ears are still telling me I'm on the rails.

[derekmorton]

I decided to test the consist with all loaded cars.

No derailments.

[R. Steele]

Everyone reading this discussion should at least try out setting up the OR EOT that I mentioned in my post #97. It is coded as a special wagon.... NOT EOT.wag --- but EOT.eot and is placed in a special folder. All the problems in using MSTS EOT.wag files are gone.

Usually EOTs were provided as a very short wagon for simulation with MSTS or OR. To upgrade it to a functioning EOT for OR following simple steps are needed:

- Create the ``Trains\ORTS_EOT`` folder
- copy the EOT subfolder present in the ``Trains\Trainset`` folder into the ``Trains\ORTS_EOT`` folder
- change the extension of the .wag file(s) to .eot
- add at the end of the .eot file the ORTSEOT block.

For Open Rails the EOT is a special type (a subclass) of wagon, with specific features. As such it appears at the end of the train in the Train Operations window.

Section 8.18 in the manual --- link to browser manual in a sticky at beginning of Open Rails Discussion Forum.

[geepster775]

I decided to test the consist with all loaded cars.

No derailments.

Same here.

I then took the original consist, replaced the 5 unit spine with the middle empty with 3 89-footers, one load, middle empty, and third load. Made it around the first trouble curve, but the empty 89 footer derailed at the bridge curve.

Was thinking of trying this consist on Mullan. 2x0 power, 63 loaded wells (probably empty containers mostly), and 60 empty wells.

https://www.youtube.com/watch?v=qq7EqLd_JGE

[CSRX]

I can confirm in reality, a EOT doesn't weigh more than 20-25 pounds, and that's the old school junk battery operated ones. The newer lightweight ones aka lunch boxes, are roughly 10-15 pounds.

But every time I've always made them that weight in ORTS, I always get the "wheel skid" notification. The bouncing around varies and I haven't deciphered what actually causes it, as sometimes it does it, and sometimes it doesn't.

[peterman]

Everyone reading this discussion should at least try out setting up the OR EOT that I mentioned in my post #97. It is coded as a special wagon.... NOT EOT.wag --- but EOT.eot and is placed in a special folder. All the problems in using MSTS EOT.wag files are gone.



Section 8.18 in the manual --- link to browser manual in a sticky at beginning of Open Rails Discussion Forum.

Hi Gerry,

I have that installed and use it when I can, however, when starting an activity where your train is running on the mainline at speed, you are unable to attach an EOT. Thusly, you do need to use the old MSTS EOT's and add them in your consist file.

Peter

[R. Steele]

Agreed --- however, you have to use either a CE or text editor to add the MSTS EOT, you could instead add the OR EOT using a text editor to the end of the consist file:

)
Wagon (
WagonData ( RTTX_253632 SLI_BNSF_FREIGHT )
UiD ( 66 )
)
ORTSEot (
EOTData ( BNSF_EOT EOTD1 )
UiD ( 67 )
)
)
)​

With the added advantage that it will then show up in the sim and could be removed using EOT window.

Once you add the MSTS EOT --- you're stuck with it ---- it cannot be removed in the sim.

Please see manual section >>> 8.18.3. How to attach and detach an EOT at the end of a train.

EDIT: In either of our choices --- one first has to determine if the player train is running at speed at the beginning of the activity.

[derekmorton]

Gerry,

I will try your example, thanks.

[derekmorton]

I could not find either example of the eot's mentioned above, so I have erick's eot's installed.
Set up an eot as indicated.

First curve I went around I got a derail message for the eot!!
The jitter is definitely gone. ( thanks Gerry )

Now to work out how to stop the derail message for the eot.