Difference's in Activities for MSTS and ORTS

[poochwilly]

When I play an activity in MSTS all seems to work okay. I run the same activity in ORTS and things seem to change like Mexican stand offs. Running windows 7 64 bit. Newest ORTS version x.2091. One in particular is in the CP Mactier route. The Obico Exodus act. Any reasons or suggestions on why this is happening?

Thanks Poochwilly

[apco25]

This happens because the screwy signaling logic employed by MSTS is being replaced be real life signal logic in OR. All the crazy work arounds created to make signals function in MSTS aren't needed now in OR.

[kevhead]

Is there a way to make the activities work in OR?

[seagoon]

I have many more Activities work fine in OR than those that don't.....probably a ratio or 80/20.

On those odd occasions where I've had a glitch (usually involving a meet) I have simply dropped to manual over-ride of switch alignments and then continued without any hassles.

[baldwin]

There is another reason for the differences as well. Unlike MSTS, OR applies the same train physics to the AI as it does to the player train, and where possible the AI will run at full track speed after running through a restricted speed block. If you haven't already done so, go to the experimental tab in Options and tick the box for location linked passing path processing. That should cure most if not all standoffs. For those it does not cure do as seagoon says, use the dispatcher window.

[kevhead]

Thanks guys I will try these suggestions. I do have to say OR has come a long way.