[James Ross]

roeter, on 07 June 2017 - 01:46 PM, said:

Attached is the most extensive weather file I have used so far. It has all the different weather types - clear, fog and rain.
A full list of available settings is included in the blueprint.

File : mo_fog_mi_rain_ev_clear.zip

Thanks.

Incidentally, can we mark most/all of the relevant blueprints as Implementation = Implemented now?

[roeter]

James Ross, on 17 June 2017 - 02:15 PM, said:

Incidentally, can we mark most/all of the relevant blueprints as Implementation = Implemented now?

Yes - apart, ofcourse, from those I mentioned above which are yet to be done.

Regards,
Rob Roeterdink

[James Ross]

roeter, on 18 June 2017 - 11:53 PM, said:

Yes - apart, ofcourse, from those I mentioned above which are yet to be done.

I've updated the blueprints - thanks for all the new features and improvements!

[mareknowosad]

Timetable Test steam engine in Chabówka

https://youtu.be/1YYpubAaQ04

http://wstaw.org/m/2017/06/22/K-Z_21062017_jpg_300x300_q85.jpg

The Chabówka Rolling Stock Heritage Park "Skansen"

[eugenR]

The new Signalling-Function approach_control_distance_Forced(50) seams not to work correctly in the attached testroute "Distantsignal", activity Appr_faulty.
If there is a switch between the Train and the controlled signal, the signal will be opened, independent of the Distance of the train to the signal. In the Activity Appr_OK, without switch between, all is OK.
Please, would you have a look at the Testroute?

Regards
EugenR

Attached File(s)

•  Distantsignal.zip (4.62MB)
  Number of downloads: 776

[roeter]

Sorry for the slow response at the moment, but I'm very busy with various things and don't always get around to answer all mails or forum requests.
I have looked at this problem. It's complex, the incorrect behaviour is the result of the initiation sequence in which the signal is activated before all train data is properly initialized. I have worked out a solution but it needs some more testing which I haven't got round to yet.

Regards,
Rob Roeterdink

[eugenR]

roeter, on 09 July 2017 - 02:55 PM, said:

Sorry for the slow response at the moment, but I'm very busy with various things and don't always get around to answer all mails or forum requests.
I have looked at this problem. It's complex, the incorrect behaviour is the result of the initiation sequence in which the signal is activated before all train data is properly initialized. I have worked out a solution but it needs some more testing which I haven't got round to yet.

Regards,
Rob Roeterdink

I am really not in a hurry about this function, I was thinking, that the Testroute has not arrived.
Perhaps it is not only a initializing-Problem:
I have placed 3 CHLStreckenausfahrsignal (simply red/green signal) between the Train and the switch (SNCA 2).
When the train has opened the second signal it happens the same, the approach_controlled Signal is switching to green.
Switch to Manual and back doesn't help.
If the train has passed the third (last) signal, after switch to manual and back the CHLEinfahrsignal is showing correct red.

If I travel thru Tösstal (DVZO) a singletrack-route with sidings at the stations, the approach_control_distant_forced at the CHLEinfahrsignals is also not working correct.

I hope this information's are helping to localize the problem.
please take all time you need.

Regards
EugenR

Attached File(s)

•  Distantsignal (2).zip (4.63MB)
  Number of downloads: 775

[eugenR]

eugenR, on 09 July 2017 - 09:20 PM, said:

I hope this information's are helping to localize the problem.
please take all time you need.

Regards
EugenR

I have tested, it occurs the same problem if the route pass over the siding_side of the switch, and also if the route use the invers direction over the switch.

Regards
EugenR

[eugenR]

eugenR, on 11 July 2017 - 10:24 PM, said:

I have tested, it occurs the same problem if the route pass over the siding_side of the switch, and also if the route use the invers direction over the switch.

Regards
EugenR

New Findings about the Problem with approach_control_position_forced
The switch between has nothing to do with the problem, it depends on SNCA

If before the Signal with approach_control_position_forced(80) are placed signals with SignalNumClearAhead(2) or higher, this function doesn’t work correct. The controlled signal is opening already if the train has passed the second signal before the controlled signal. Try in the testroute “app_con_pos_forced” the activity NSCA_2

If there are Signals with SNCA(1) placed before the controlled signal is working correct, try the activity SNCA1
Regards
EugenR

Attached File(s)

•  app_con_pos_forced.zip (4.69MB)
  Number of downloads: 747

[markyisri]

Can I use the weather file in the current version of OR?

[septf]

experimental version. if it works at home, you can tell me how you do.

[eugenR]

Problem with Dense Traffic on a singe-track impasse:

I have tried to drive against dense Traffic on a single-track-Route.
But if I stay in a siding and there are many Trains from the opposite direction I have to wait until the last train has passed.
OR prefer always trains from the same direction.

Does somebody know what I can do (modify the signal-files?) so, that OR alternate the train-diractions at singletrack-impasses? I have tried also the function "approach_control_lock_claim()" (see post #1), Additional signal script functions) but I don't know exactly how it is to use?

Does somebody know more?

Regards
EugenR

[mareknowosad]

Hello. I use commands $ hold $ nowaitsignal $ nohold on a single-track-Route. It can help.
Timetable with Consists OR and Paths http://forum.trainsi...php?topic=239.0 for Route 202_80s http://www.linia202....de/download.htm

https://kunifuchs.co.../2548-linia202/




http://wstaw.org/m/2017/12/23/Open_Rails_2017-12-18_08-26-06_png_300x300_q85.jpg

http://wstaw.org/m/2017/12/23/Open_Rails_2017-12-18_08-55-35_png_300x300_q85.jpg

http://wstaw.org/m/2017/12/23/Open_Rails_2017-12-18_09-08-23_png_300x300_q85.jpg

http://wstaw.org/m/2017/12/23/Open_Rails_2017-12-18_09-10-02_png_300x300_q85.jpg

http://wstaw.org/m/2017/12/23/Open_Rails_2017-12-19_05-59-31_png_300x300_q85.jpg

http://wstaw.org/m/2017/12/23/Open_Rails_2017-12-23_01-33-56_png_300x300_q85.jpg

[eugenR]

m61, on 30 December 2017 - 07:46 AM, said:

Hello. I use commands $ hold $ nowaitsignal $ nohold on a single-track-Route. It can help.

Hello m61,
Thank You for the information's.
But its not exactly what I am searching for.
I would like to drive forward, not with a hard timetable, and would like to meet dense traffic with different Trains in backward direction.

Now I Have recognised, that it is not the Problem of OR when at single-track sections trains from one direction are preferred.
I had on the single-track section placed a signal. If I remove this Signal, so that the single-track section is only one block-section, OR let pass also by dense traffic alternatively trains from both directions.

regards
EugenR

[shadowmane]

roeter, on 12 June 2017 - 02:04 PM, said:

It's allready possible to run beyond 24 hours - trains can be started after midnight by adding '$next' to the start-time.
I suppose it would be possible to add a '$next2' etc., to add even further days.
A 'restart' of the timetable after 24 hours is far more difficult. Not only would it require some kind of link between trains which finished there run and are stored as 'static', and what service they would form the next day. But the main problem is that when the timetable starts, all trains are processed and kept in 'memory' - allowing quick access when a train forms into another train.
At the end of the day, that stack of trains has been processed and is empty. To start again, it would be required to reform this database.
The value of having multiple days of running is limited - one will regularly have to save and restart a session, and there is little difference in restarting a saved session at, say, 02:00, or starting a new session at that time.
As said, using '$next' you can run trains after midnight, and by starting overnight trains at about 01:00 or 02:00, but terminating them later (about 03:00 or 04:00), you can simulate a real full day's work including full traffic around midnight.

Regards,
Rob Roeterdink

Is there a '$before' command as well? If you want a train to start the day before and be running in the early hours of the morning, you would need something like this, wouldn't you?