[Tony]

Hello Guys
Here is a bug I'm running into. This is 3DTS Cajon Pass, Open rails version 0.9.0.1684, DW activity U.P. Intermodal to W.C part 1. The AI train is supposed to be on the siding, so that My train has the can go straight through. I have looked in AE to verify this. I have also kept the train as close to track speed as per the brief in the activity. The siding is between m.p. 4318 and m.p. 4382. of the Mojave sub.



Cheers Tony B)

[Csantucci]

Your OR version is very outdated. Pls. try the last version, that you can download from here http://james-ross.co...jects/or/builds and check if you still get the problem.

[Tony]

Well that was a huge improvement now I'm stuck at Lancaster siding at red with no AI train showing up. B)



This is only 20 minutes into the activity and I can't tab past the signal. In version 0.9.0.1684 all I had to do was stop and proceed, the A1 train took to the siding and I was able to proceed. :D Oh and I found the other train using Alt+9, it's on the other side of Lancaster stuck at red. :oldstry:


Cheers Tony B)

[roeter]

If you press Shift-F5 a couple of times, the Dispatcher Hud information will be displayed. This can give a clue of what is stopping you from proceding.
Can you make a screenshot including that information?

Regards,
Rob Roeterdink

[Tony]

Here You go.

My Train.


The other AI train.


Cheers Tony :oldstry:

[roeter]

You're in trouble with train 13 ("NBinter").
I don't know the layout of the route further ahead, but it seems this train is started at such a position that a deadlock is unavoidable, i.e. neither train has any alternative path available. The distance travelled indicates that this train has only just started.
You could have a look in the dispatcher window (CTRL-9) to see where this train 13 is. An earlier start of this train could well sort this problem.

Regards,
Rob Roeterdink

[Sid P.]

Is this situation occurring at the start of the activity ? (I don't have the activity to test it).
If so, it may be related to the way that OR handles AI trains started within the first few seconds ( 20 seconds or less) of the start of the activity.
See the bug report that I submitted -: "[Bug 1249872] Re: AI Train created at incorrect time - collides with player" in Launchpad.
It appears that AI trains in OR should be started at least 20 seconds or more before the player train, or they may appear out of place.

Cheers,
Sid