Page 1 of 1
Exits to fringes logged for use at a later time 07/01/2021 at 18:29 #136072 | |
trolleybus
150 posts |
I'm currently working my way through every single sim and something occurred to me. I have an idea of what effect my late trains have on fringe boxes but it would be nice to actually have to handle them. I could, f course, simply run two or more sims chained, but that can become a bit much for a single operator. What I'd like is the ability to record a session and have that session read later when running a fringe box. So it acts as if chained but the trains are entering not from another instance of a sim but from a past session. Log in to reply |
Exits to fringes logged for use at a later time 07/01/2021 at 19:28 #136075 | |
AlexRail575
136 posts |
That becomes problematic when you have a train which goes from (or through) sim A to fringe sim B and terminates somewhere in sim B, with its next working being in the other direction: I don't there is any mechanism (timetable rules are the solution for timetable writing, but they obviously only work with the unchained sim...) which could help cope with, say, you making up time on a train which entered significantly late/got delayed at a station... (which would then alter the time it got into sim B, which would alter the time it gets back in sim A...)
Log in to reply |
Exits to fringes logged for use at a later time 08/01/2021 at 01:03 #136079 | |
JWNoctis
58 posts |
AlexRail575 in post 136075 said:That becomes problematic when you have a train which goes from (or through) sim A to fringe sim B and terminates somewhere in sim B, with its next working being in the other direction: I don't there is any mechanism (timetable rules are the solution for timetable writing, but they obviously only work with the unchained sim...) which could help cope with, say, you making up time on a train which entered significantly late/got delayed at a station... (which would then alter the time it got into sim B, which would alter the time it gets back in sim A...)That could be handled by timetable rules in sim A, with nothing else to work with - this sounds like chaining, but only in one direction. And a good way to really feel the effects (and consequences) of any endeavour at regulation, too. Last edited: 08/01/2021 at 10:26 by JWNoctis Reason: None given Log in to reply |
Exits to fringes logged for use at a later time 08/01/2021 at 08:11 #136080 | |
clive
2789 posts |
Mantis 32747 raised so this isn't forgotten. That doesn't mean it will ever happen, though.
Log in to reply The following users said thank you: trolleybus, JWNoctis, BarryM |
Exits to fringes logged for use at a later time 08/01/2021 at 09:43 #136081 | |
trolleybus
150 posts |
Is it that problematic? When chaining, sim 1 writes to sim 2 informing it of the approach of a train (I assume). My suggestion is a mechanism to write that information to a file instead of a TCP packet. Similarly sim 2 can be configured to read from a file instead of a port. I acknowledge that ensuring events are handled at the right time isn't trivial but the concept is. Log in to reply |
Exits to fringes logged for use at a later time 08/01/2021 at 11:19 #136085 | |
clive
2789 posts |
trolleybus in post 136081 said:It's not that simple. Various bits of the core code behave differently when a sim is chained and when it isn't (simple example: some track circuits at the border take their state from the chained sim rather than internally). All that stuff needs to be in "non-chained" mode to work whereas the train entry stuff needs to be in "chained" mode. I can think of a whole slew of things that would have to be checked and possibly altered for a marginal feature. (I do have a vague idea for a completely different way of doing it. But that's significant work as well and would introduce some new user concepts No, I'm not going to explain it until or unless this reaches the top of my work pile.) trolleybus in post 136081 said: Actually, that's the only bit that is trivial. Log in to reply The following user said thank you: trolleybus |