Persistent Red Signals Signals stay red and no "permission" audible
#1
Posted 02 February 2021 - 02:42 PM
#2
Posted 02 February 2021 - 03:21 PM
#3
Posted 02 February 2021 - 04:14 PM
Attached File(s)
-
OpenRailsLog.txt (28.87K)
Number of downloads: 369
#4
Posted 02 February 2021 - 07:33 PM
Any reason why you're not using the newer version?
Steve
#5
Posted 02 February 2021 - 08:41 PM
Also follow Steve's advice and upgrade to Ver.17of the Monon.
#6
Posted 03 February 2021 - 07:22 AM
#7
Posted 03 February 2021 - 07:50 AM
#8
Posted 27 March 2022 - 02:21 PM
R H Steele, on 02 February 2021 - 08:41 PM, said:
Also follow Steve's advice and upgrade to Ver.17of the Monon.
I wonder if this fix would cure my problems with all the weird signaling I see in OR........such as multiple false advance approach indications, where the following signal is green. This occurs in most, if not all, of my MSTS routes. Don't know if Raildriver use affects this, but I do use RD.
Don't know if this is related, but, compared to running in MSTS, running an activity in OR results in changed behavior......for example, I've seen several instances of AI traffic, which in MSTS took the siding, now, in OR, holds the main, causing the player consist to go off path.
If I were to create this file arrangement, then I'd need to do it for each route individually? Would this fix address either of the issues I presented?
AA
#9
Posted 27 March 2022 - 02:36 PM
#10
Posted 27 March 2022 - 03:58 PM
agentatascadero, on 27 March 2022 - 02:21 PM, said:
Don't know if this is related, but, compared to running in MSTS, running an activity in OR results in changed behavior......for example, I've seen several instances of AI traffic, which in MSTS took the siding, now, in OR, holds the main, causing the player consist to go off path.
If I were to create this file arrangement, then I'd need to do it for each route individually? Would this fix address either of the issues I presented?
AA
There's a conflation of two problems going on here.
First: the signal problem could be solved by using the OpenRails folder approach, I would recommend it...it will not do any harm...put both the sigcfg.dat and sigscr.dat files in the folder.
And the second -- not related:
agentatascadero, on 27 March 2022 - 02:21 PM, said:
AA
I agree with Weter, probably the Option/Simulation Tab/Activity Options >> Location-linked passing path processing. I always keep the box checked, and make adjustments to activities, if necessary.
Quote
When this option is NOT selected, ORTS acts similarly to MSTS. That is, if two trains meet whose paths
share some track section in a station, but are both provided with passing paths as dened with the MSTS
Activity Editor, one of them will run through the passing path, therefore allowing the meet. Passing paths
in this case are only available to the trains whose path has passing paths.
When this option is selected, ORTS makes available to all trains the main and the passing path of the
player train. Moreover, it takes into account the train length in selecting which path to assign to a train in
case of a meet.
For content developers
A more detailed description of this feature can be found under Location-Linked Passing Path Processing in
the chapter Open Rails Train Operation.
Most Recent OR Manual