ORTS Version of TrainSimulations Seligman Sub 2.0

[woodfyr]

OR Seligman installed with no problems. Runs on OR 4334 Mono.

Ran the Southwest Chief last night from Winslow to Flagstaff with no problem, except --- There were three A1 trains backed up at Williams for no apparent reason. 49 had a green signal but did not move until I took control and started it moving. Then all three got under way.

[TrainSimulations]

Hi Russ,

During testing, we encountered a strange anomaly, whereby the AI trains would just stop somewhere, for no apparent reason. Often times they would clear themselves and move along, but other times they didn't. Honestly, I am stumped as to why they even did that to begin with.

Cheers,
Jason

[woodfyr]

Open Rails 2019-01-29 01-51-13.jpgDispatcher, this is 4160 Pheunix, Westbound. We have a broken coupler(s) between 3rd and 4th car. Will be delayed while we get them moved. OUT!

Happens with this consist whenever it is used.

[woodfyr]

AHH HAA ! Figured that one out. New physics.

[woodfyr]

Jason,

Yes, some strange things happening. On the "Pheonix 4160" I ran into a problem following A1 at Diablo Canyon. The a1 was routed on to the track where Consist 32842 was sitting. Tried to reroute to the right track and Behold, it worked, BUT a strange A146 appered heading in the opposite direction for a meet wit the Player.

One hell of a way to run a Railroad

[seagoon]

The alerter doesn't sound right away. If you are running in the cab view, the alerter will flash for about 10-20 seconds, before the ear piercing racket. This is consistent with how alerters work on the prototype.

Cheers,
Jason

That's what I thought too, Jason, but it got to the point where the alerter timed out and the train went into emergency braking.

Anyway....that doesn't detract from the fact that the route is great.

[demando]

Jason, is there a way to change the directory path, say if it was placed in the wrong folder? I have a BNSF folder for my ORTS system, but after discovering that the exe creates a standalone folder, I am unable to move it without mucking something up.

[R. Steele]

Hi Russ,

During testing, we encountered a strange anomaly, whereby the AI trains would just stop somewhere, for no apparent reason. Often times they would clear themselves and move along, but other times they didn't. Honestly, I am stumped as to why they even did that to begin with.

Cheers,
Jason

Jason, wonderful work on the route, and much appreciated discount for people who have purchased earlier versions, generous, thanks.

Pertaining to some strange behavior by AI's, did you guys use the OR log to spot potential problems with activities, route, shapes, or other issues.
I'm getting warnings - no fatal errors - so that is good.

Here's a sample that may show why the AI behavior is strange, from the log: ( I have all the recommended option boxes, checked)

Information: Invalid passing path defined for train 39 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 39 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 39 at section 416 : overlaps with other passing path

Information: Invalid passing path defined for train 40 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 40 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 40 at section 416 : overlaps with other passing path

Information: Invalid passing path defined for train 42 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 42 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 42 at section 416 : overlaps with other....and so forth, quite a few

Would be good if everyone that got the new route, and found problems - whatever they are - checked their logs, could prove enlightening.
The OR log ( found on the desktop, by default ) is a valuable troubleshooting tool.

Again, this route is a step up, thanks. Best Regards, Gerry

[R. Steele]

Jason,

Yes, some strange things happening. On the "Pheonix 4160" I ran into a problem following A1 at Diablo Canyon. The a1 was routed on to the track where Consist 32842 was sitting. Tried to reroute to the right track and Behold, it worked, BUT a strange A146 appered heading in the opposite direction for a meet wit the Player.

One hell of a way to run a Railroad

The loose consist was placed on the AI path, moving the AI won't solve the problem, probably just make further complications ( as you experienced) - the loose consist has to be moved. At least that's my impression...you will need to use the Activity editor part of TSRE to make the correction.

bandicam 2019-01-29 13-23-43-431.jpg

[geepster775]

Easier to just delete the loose consist for now from the ACT file.

Also, the timings between the ACT and TRF are out of sync for the bottom 6 or so AI entries for the Phoenix act. I simply changed the time values in the TRF to match the ACT for now, haven't run it to see what the impact is

[TrainSimulations]

You guys are getting strange results. I ran that activity just yesterday, the first hour of it anyway, and the westbound train was moved around the stationary consist at Diablo Canyon. In fact, there is a passing path established for it to do so. I don't understand why you are getting deadlocked at that location, as a result.

[woodfyr]

I ran the Pheonix again today and the A1 diverted through the passing siding at Diablo just fine as did the Player. I believe the problem lies in the way that OR processes the situation of the Player train running behind the A1. It may be associated with the "Location-linked passing path processing" in the Experimental options. If the Player is following the A1 too closely (running the yellows@ 30) OR attempts to place the A1 in the siding (presently occupied with the loose consist). Seems to be a possibility.

[TrainSimulations]

That may be true, and i guess it depends on your ORTS settings. If you have advanced adhesion enabled, along with curve resistance, there is no way on Gods green earth you'll be caught up to the AI westbound ahead of you by the time you get to Diablo Canyon. With those settings, the only way you can catch up is using the autopilot, since it doesn't follow the rules of physics.

[R. Steele]

That may be true, and i guess it depends on your ORTS settings. If you have advanced adhesion enabled, along with curve resistance, there is no way on Gods green earth you'll be caught up to the AI westbound ahead of you by the time you get to Diablo Canyon. With those settings, the only way you can catch up is using the autopilot, since it doesn't follow the rules of physics.

Very true Jason, concerning autopilot.

I ran the activity again, I still believe the problem lies in the path of the AI manifest and also the passing paths. I'm still getting log warnings like this:

Information: Invalid passing path defined for train 43 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 43 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 43 at section 416 : overlaps with other passing path

Information: Invalid passing path defined for train 44 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 44 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 44 at section 416 : overlaps with other passing path

Information: Invalid passing path defined for train 45 at section 440 : overlaps with other passing path

Information: Invalid passing path defined for train 45 at section 436 : overlaps with other passing path

Information: Invalid passing path defined for train 45 at section 416 : overlaps with other passing path


Run AI : 20 07:00

Warning: Train Westbound Grain Train AI (42) passing signal 1055 at 41831.4 at danger at 0.28

08:00

Warning: Train Westbound Priority Z AI 1 (43) passing signal 1055 at 42235.7 at danger at 0.47

09:00 10:00

Warning: Train Westbound Ocean Intermodal AI 2 (44) passing signal 1055 at 41821.8 at danger at 0.47

11:00 12:00 13:00 14:00

Warning: Train Westbound Ocean Intermodal AI 1 (45) passing signal 1055 at 41613.9 at danger at 0.47

I also switched trains and this is what it looks like from the AI Manifest at east diablo

bandicam 2019-01-29 16-44-46-506.jpg and some seconds later bandicam 2019-01-29 16-44-47-316.jpg

Signal continually flashing.

You mentioned establishing a passing path around the loose consist ( in post #41) - passing paths will only work for active trains, not loose consists and active trains, AFAIK. The manifest needs a path around the loose consist, not a path "marked" as a passing path. Maybe this all is an OR bug.

Anyway, I've been around the route...very nice job indeed, and I'm sure the little glitches with the activities will be solved. Took a lot of work, appreciated.

[woodfyr]

The OR settings were set as per the recommendations in the BNSF Seligman Reference (pdf file). I was running a bit (5-7 mph) over the posted limit until I got the first yellow about 20 minutes west of Winslow. Ran at 30 or below until I got a w/r for 20. I'll give it a rest until tomorrow.