Hi folks.
I've been spending a little bit of time with Trainz 2019 (build 97556). and for the most part I'm very impressed (and looking forward to the final release). However, I've come across what may be user error, a bug, an installation/version issue, or a combination of all of those.
On one of my test routes, I have a single Interlocking Tower that has two paths. Both paths control the same set of signals and junctions, but simply in the reverse direction of one another (an eastbound path and a westbound path). What I'm observing is that once a train locks one of the two paths, the other path can no longer be activated for the remainder of the session. For example: A train locks the eastbound path and begins to navigate it. Immediately the Tower Manager (rule) reports >>> westbound "path not activable". That would make sense since the eastbound path is currently in use. The problem is that, even after the eastbound path has been released (and the train has long since cleared it), the westbound path remains "not activable". I've tried using the "ITCancelEnhancedPath" command, but that makes no difference. I've also tried various IT path settings (Automatic, Manual, etc...) but the problem persists. Independently, each path works fine on its own, but whichever one is locked first, the other becomes permanently inactivable.
For me, the issue is very easy to reproduce ... it happens even on a test route with just some empty baseboards and a length of single track (with some signals, of course). So I'm just wondering if anyone else has encountered this before, or perhaps if I'm implementing the IT incorrectly.
- Tom
PS: (I'm using the Enhanced TRC3 invisible Interlocking Tower ... SP2 and later. Aug 2018)
I've been spending a little bit of time with Trainz 2019 (build 97556). and for the most part I'm very impressed (and looking forward to the final release). However, I've come across what may be user error, a bug, an installation/version issue, or a combination of all of those.
On one of my test routes, I have a single Interlocking Tower that has two paths. Both paths control the same set of signals and junctions, but simply in the reverse direction of one another (an eastbound path and a westbound path). What I'm observing is that once a train locks one of the two paths, the other path can no longer be activated for the remainder of the session. For example: A train locks the eastbound path and begins to navigate it. Immediately the Tower Manager (rule) reports >>> westbound "path not activable". That would make sense since the eastbound path is currently in use. The problem is that, even after the eastbound path has been released (and the train has long since cleared it), the westbound path remains "not activable". I've tried using the "ITCancelEnhancedPath" command, but that makes no difference. I've also tried various IT path settings (Automatic, Manual, etc...) but the problem persists. Independently, each path works fine on its own, but whichever one is locked first, the other becomes permanently inactivable.
For me, the issue is very easy to reproduce ... it happens even on a test route with just some empty baseboards and a length of single track (with some signals, of course). So I'm just wondering if anyone else has encountered this before, or perhaps if I'm implementing the IT incorrectly.
- Tom
PS: (I'm using the Enhanced TRC3 invisible Interlocking Tower ... SP2 and later. Aug 2018)