| 2016-02-25 06:59:23 |
James Bradley, Jr. |
description |
While playing an activity on the Tehachapi Pass route by 3DTrains, I encountered the following problem (see screenshot).
Notice the track monitor does not indicate the presence of a train, nor do the signals indicate that a train is present (next signal should be red, not green). The signal just prior to this shot was a flashing yellow, or "Advance Approach". I assumed the next signal would either be yellow "Approach" or red "Stop", and that I would hold the main while the AI train took the siding.
The game was in "Auto" mode, so all switches and signals were being handled by the game. Could this be a possible OR issue, with the signals improperly protecting against AI trains, or is this an activity issue? I'm wondering if the AI train generated itself as I was entering the block (not likely, since I was given an "Advance Approach" entering the block), or if the OR auto-dispatcher somehow allowed for conflicting paths to occupy the same track. I have seen this happen once before, on a completely different route and activity, where the signal and track monitor did not match actual conditions in the game.
I have attached a screenshot and OR report to this bug report for reference. Comments or suggestions are welcome. |
While playing an activity on the Tehachapi Pass route by 3DTrainStuff, I encountered the following problem (see screenshot).
Notice the track monitor does not indicate the presence of a train, nor do the signals indicate that a train is present (next signal should be red, not green). The signal just prior to this shot was a flashing yellow, or "Advance Approach". I assumed the next signal would either be yellow "Approach" or red "Stop", and that I would hold the main while the AI train took the siding.
The game was in "Auto" mode, so all switches and signals were being handled by the game. Could this be a possible OR issue, with the signals improperly protecting against AI trains, or is this an activity issue? I'm wondering if the AI train generated itself as I was entering the block (not likely, since I was given an "Advance Approach" entering the block), or if the OR auto-dispatcher somehow allowed for conflicting paths to occupy the same track. I have seen this happen once before, on a completely different route and activity, where the signal and track monitor did not match actual conditions in the game.
I have attached a screenshot and OR report to this bug report for reference. Comments or suggestions are welcome. |
|
