ATSF Seligman Sub 2.0 - SouthWest Chief for ORTS

[R. Steele]

Okay, just uploaded finished ( hopefully) activity.
Thanks to plethaus21 for testing and bringing some glitches to my attention and also to grncherry1 for posting that the eastbound Chief did not work in OR.

Here's the special notes section that should be read:
1. The player consist has been modified to contain three Amtrak Locomotives (SLI_AMTRAK_ENGINES)
SLI AMTRAK F40PHR408
SLI AMTRAK F40PHR398
SLI AMTRAK F40PHR398HEP
I am not sure if this is prototypical for the era (1993) but the extra power allows player to adhere closer to the schedule and makes the timing work in OR.
------------------- Number Two [TrainListWindow Alt-F9] is not available in any Open Rails Version prior to X3214 -------------
2. ALL AI Traffic consists now have driveable locomotives. This modification was made to take advantage of the ability to "Jump Trains" - Player Train Switching while in the game.

A new control implemented with OR X3214 Train control switch available through TrainListWindow (Alt-F9). Blueprint: https://blueprints.launchpad.net/or/...-train-control Forum discussion: http://www.elvastower.com/forums/ind...train-control/
For more information on Player Train Switching using the Train List Window ( Alt-F9 ) please read revised manual published with version X3217.

3. The activity uses the ORTSContinue ( 15 ) statement after activity messages. This allows the message to be shown for 15 seconds without stopping the activity as happens in MSTS.
Opening the activity using the MSTS Activity Editor will erase this message. It must be manually placed in the activity using an editing program such as ConText, or the tool of your choice.

Any issues after running, just post here. Hint: Do Not dog it (no speeding either) from Needles to Yucca.
Have Fun!

bandicam 2015-08-31 14-22-49-611.jpg

[grncherry1]

Okay, just uploaded finished ( hopefully) activity.
Thanks to plethaus21 for testing and bringing some glitches to my attention and also to grncherry1 for posting that the eastbound Chief did not work in OR.

Here's the special notes section that should be read:
1. The player consist has been modified to contain three Amtrak Locomotives (SLI_AMTRAK_ENGINES)
SLI AMTRAK F40PHR408
SLI AMTRAK F40PHR398
SLI AMTRAK F40PHR398HEP
I am not sure if this is prototypical for the era (1993) but the extra power allows player to adhere closer to the schedule and makes the timing work in OR.
------------------- Number Two [TrainListWindow Alt-F9] is not available in any Open Rails Version prior to X3214 -------------
2. ALL AI Traffic consists now have driveable locomotives. This modification was made to take advantage of the ability to "Jump Trains" - Player Train Switching while in the game.

A new control implemented with OR X3214 Train control switch available through TrainListWindow (Alt-F9). Blueprint: https://blueprints.launchpad.net/or/...-train-control Forum discussion: http://www.elvastower.com/forums/ind...train-control/
For more information on Player Train Switching using the Train List Window ( Alt-F9 ) please read revised manual published with version X3217.

3. The activity uses the ORTSContinue ( 15 ) statement after activity messages. This allows the message to be shown for 15 seconds without stopping the activity as happens in MSTS.
Opening the activity using the MSTS Activity Editor will erase this message. It must be manually placed in the activity using an editing program such as ConText, or the tool of your choice.

Any issues after running, just post here. Hint: Do Not dog it (no speeding either) from Needles to Yucca.
Have Fun!

[ATTACH=CONFIG]67638[/ATTACH]

I haven't been able to find the file you uploaded, maybe I'm missing it.

[R. Steele]

I haven't been able to find the file you uploaded, maybe I'm missing it.

That's because once you upload the file to TS it usually takes a day or so for review to complete and the file to official appear in the library for downloading. I just wanted to let people know I had completed it and it was uploaded....be patient, it will appear within 24 to 48hours - usually.

[grncherry1]

That's because once you upload the file to TS it usually takes a day or so for review to complete and the file to official appear in the library for downloading. I just wanted to let people know I had completed it and it was uploaded....be patient, it will appear within 24 to 48hours - usually.

Thanks for the info and thanks for the activity.

[R. Steele]

It's in the library - look under subheading Open Rails Misc.

[grncherry1]

Okay, just uploaded finished ( hopefully) activity.
Thanks to plethaus21 for testing and bringing some glitches to my attention and also to grncherry1 for posting that the eastbound Chief did not work in OR.

Here's the special notes section that should be read:
1. The player consist has been modified to contain three Amtrak Locomotives (SLI_AMTRAK_ENGINES)
SLI AMTRAK F40PHR408
SLI AMTRAK F40PHR398
SLI AMTRAK F40PHR398HEP
I am not sure if this is prototypical for the era (1993) but the extra power allows player to adhere closer to the schedule and makes the timing work in OR.
-

Any issues after running, just post here. Hint: Do Not dog it (no speeding either) from Needles to Yucca.
Have Fun!

[ATTACH=CONFIG]67638[/ATTACH]

I had the pleasure of running all the way across this morning and I must say Mr. R. Steele you made me a happy foamer. The run was flawless.
I have ridden this schedule many times and this is close to the real thing. As far as power, Amtrak did and still on occasion use 3 or more locomotives depending on load counts and the movement of equipment. For a while they were forced to use more power to maintain their schedule with the F40's that had to struggle on that long grade from Needles all the way to nearly Flagstaff eastbound. ATSF didn't appreciate them slowing their freight.
Modern day Southwest Chief doesn't stop at Seligman but does make a brief stop at Williams Jct for passengers bussed from Phoenix.
Thanks again for the effort to sort this out for us.

[Don6218]

I am running this Act now, so far it is great to show that activities made for MSTS can be remodeled for OR without losing anything and gaining everything OR has to offer!

Thank You!!!

[R. Steele]

It's gratifying to know that the activity works well and people are enjoying it. Also, I think we can all agree that Open Rails is a fine simulator, constantly being evaluated and improved upon. We all should give a round of thanks to the Open Rails Development Team and of course to the far sighted individuals (and one fellow in particular, Wayne Campbell) for proposing this wonderful project.

I believe most, if not all, MSTS activities that have become favorites can be adapted to run well in Open Rails.
I think I overstated the case above, found about the activities that some Virtual RR's used in MSTS that were complicated multi-part activities. However, it certainly does not hurt to take apart any activity to see if it can be revised to work in OR.