I've been working with an activity (060-Lumber-03) for the Feather River. The MSTS version does not work in OR. I reworked the activity,
fixing player path, AI start times & paths - until it ran correctly in OR.
I kept running the activity using other available trains (Train List Window - Alt-F9) and letting the player train simply run its' path and finish.
Last thing I did was to choose a static train in the Portola yard and join in the AI traffic down to Oroville. The traffic directly in front
of me (literally ) was the westbound Zephyr. As you can see from the pics I was going way too fast and way too close to the passenger train.
The object was NOT to crash into the rear but pace it down the canyon. I suppose I was a little bored and looking for trouble at this point.
Anyway, some strange things happened.
Sometimes OR would not resume from a save - see 1st picture and log for more information, it usually happened when I was following too closely (under a tenth of a mile) or too fast.
I had to keep trying earlier saves until one would work.
Switches would automatically throw when I approached within 200 yards of the switch and the "G" key would not work, the switch could be thrown for the mainline, but would immediately switch back to the spur (in the 1st case shown).
This happened twice - first instance is shown below with screenshot containing the dispatch viewer. This is a spur that the static train (now the player train) was switched onto, too fast for me to react. The train just stopped when arriving at the end of the spur, program kept running.
The 2nd time I was switched onto a siding at Keddie just before the wye, that time I was able to easily rejoin the main and keep following the Zephyr. - no screenshot attached
I'm posting this information just as a curiosity. I do not consider these events bugs because I was completely screwing with the program.
It was fun, especially following the Zephyr all the way down the canyon.
01.jpg 02.jpg
03.jpg 04.jpg
OR_Log.zip
fixing player path, AI start times & paths - until it ran correctly in OR.
I kept running the activity using other available trains (Train List Window - Alt-F9) and letting the player train simply run its' path and finish.
Last thing I did was to choose a static train in the Portola yard and join in the AI traffic down to Oroville. The traffic directly in front
of me (literally ) was the westbound Zephyr. As you can see from the pics I was going way too fast and way too close to the passenger train.
The object was NOT to crash into the rear but pace it down the canyon. I suppose I was a little bored and looking for trouble at this point.
Anyway, some strange things happened.
Sometimes OR would not resume from a save - see 1st picture and log for more information, it usually happened when I was following too closely (under a tenth of a mile) or too fast.
I had to keep trying earlier saves until one would work.
Switches would automatically throw when I approached within 200 yards of the switch and the "G" key would not work, the switch could be thrown for the mainline, but would immediately switch back to the spur (in the 1st case shown).
This happened twice - first instance is shown below with screenshot containing the dispatch viewer. This is a spur that the static train (now the player train) was switched onto, too fast for me to react. The train just stopped when arriving at the end of the spur, program kept running.
The 2nd time I was switched onto a siding at Keddie just before the wye, that time I was able to easily rejoin the main and keep following the Zephyr. - no screenshot attached
I'm posting this information just as a curiosity. I do not consider these events bugs because I was completely screwing with the program.
It was fun, especially following the Zephyr all the way down the canyon.
01.jpg 02.jpg
03.jpg 04.jpg
OR_Log.zip
Comment