Problems With Trainsimulations BNSF Scenic Subdivision Demo Route

[derekmorton]

Without modification, I get derailment with 8 and 27, both empties, modified and running again.

[meeshu]

Meeshu,

What did you do with the10 wag files?

The 10 modified *.wag files were copied to the SLI_BNSF_FREIGHT subdirectory and overwriting the existing 10 *.wag files.

Just to be certain of my results in post # 45, I ran the What Goes Up activity again just a few hours ago. Ran the activity until just past the signal near MP1726.

The results of this most recent test run were almost the same as for those results in my post # 45. That is, the following cars derailed (listed in numerical order) -

0-11 derailed three times
0-31 derailed three times
0-32 derailed two times
0-41 derailed three times.

[derekmorton]

With what version of OR?

[meeshu]

Open Rails New Year MonoGame 159.

[derekmorton]

There must be something different in our settings, can you post a log from 159 please so I can see your settings.

[niknak]

Derek my experience now with derailments is exactly the same as Meeshu's.. I ran the act after amending the wag files with your downloaded files. I was in notch 7 at approx 17mph. OR log attached.

[meeshu]

There must be something different in our settings, can you post a log from 159 please so I can see your settings.

As requested -

OpenRailsLog_What_Goes_Up.txt

[derekmorton]

Meeshu,

Can you run the 64 bit ORNYMG?

The missing files at the end of your log would indicate corruption in your install, please reinstall the route.

[meeshu]

OK. Deleted the existing installation of Trainsimulations folder which includes the BNSF Scenic Subdivision Demo route.

Re-installed Trainsimulations from the installer which I downloaded directly from Trainsimulations website a couple of weeks ago.

Then applied the ten *.wag file fix within the SLI_BNSF_FREIGHT sub directory.

Ran the activity What Goes Up again using the default consist (with the ten modified *.wag files now applied) and ran under Open Rails New Year Mono Game 159 via the 64 bit executable (OpenRails64.exe).

But again continue to receive car derailments almost exactly as before for cars 0-11, 0-31, 0-32, and 0-41.

Another log file enclosed.

OpenRailsLog_what_goes_up_rev1.txt

[geepster775]

I went through and replaced the numwheels with ORTSNumberAxles, and got the same result at the first problem curve as seen on the video. At the Foss River bridge location, also derailed the B platform of the first loaded well car (0-6) as well as the usual (0-4) loaded A platform of first well car. Testing version 1417. OpenRailsLog1.zip

[derekmorton]

Meeshu,

RunAt32bit = True You are still running 32 bit

AdhesionFactor = 130 this is a leftover of MSTS, needs to be 100% for realism

Why are you running such a small resolution? 1024 x 768?

I don't understand why you have so many missing sound files?

[derekmorton]

Geepster,

I also replaced numwheels with ORTSnumberaxles and get the same result for me.

Gents,

We have 3 very different systems, running the latest code on one and ORNYMG 159 on the other 2, we still are getting different results. I have run out of ideas.

I need to have a rest and look at it again later.

Thank you for your time.

[niknak]

In order to rule it out I've just tried the act again with 'curve dependent resistance' UNticked - but it makes no difference.

[geepster775]

The sound errors come from the fact that a fresh, clean install of the current starter route does not deposit a SOUND folder in what should be a new installation. It only creates GLOBAL, ROUTES and TRAINS.

[derekmorton]

One of the things that stands out for me, is that loaded stack trains will NEVER have an empty platform at the front ( ish ) of a train.
With older versions of OR, you could run this consist without errors.
Today however with code getting updated, we can no longer do it.
This is a good thing as we are getting more realistic.

I remember some time back I could run the world record train from Australia, and it ran fine.
As versions changed, I began to break couplers.
As I delved further into the problem, I discovered that I was exceeding the coupler strength by a very wide margin.
This is the price of realism.

To that end, I am going to make up a consist with all full platforms and see how it runs.
I will post the consist here if anybody wishes to try.