Page 1 of 1
Decision failed to activate train 07/10/2023 at 18:55 #153552 | |
9pN1SEAp
![]() 1140 posts ![]() |
Hi, Another weird one, not sure if this is sim-specific. Decision SUDL choice BB is already selected and this correctly caused the seed for 0T50. However the scheduler has decided to mark 6H50/H034396 as non-running, even though the choice is "[any] BA | BB | BC". Save attached from 1 minute before scheduled entry. Thanks Jamie Post has attachments. Log in to view them. Jamie S (JAMS) Log in to reply |
Decision failed to activate train 07/10/2023 at 19:11 #153554 | |
postal
![]() 5216 posts ![]() |
9pN1SEAp in post 153552 said:Hi,Run the save on and the train enters. I can't remember the exact timings (is it 1 minute or 30 seconds?) but IIRC the TT does mark a train as running or not running a short time before due entry so in this case 6H50/H034396 would be greyed out in the TT for a short period before entry. Edit: I have just been given a nudge that there is also a rule marking the two 6H50 versions as alternatives. As this pair are also covered by different decision choices this may well cause the sim indigestion. There should either be a rule or a decision but not both. “In life, there is always someone out there, who won’t like you, for whatever reason, don’t let the insecurities in their lives affect yours.” – Rashida Rowe Last edited: 07/10/2023 at 19:53 by postal Reason: None given Log in to reply |
Decision failed to activate train 07/10/2023 at 20:26 #153557 | |
9pN1SEAp
![]() 1140 posts ![]() |
Ah! Forgot I’d left that Alts rule in. Thanks!! Jamie S (JAMS) Log in to reply |
Decision failed to activate train 08/10/2023 at 11:45 #153559 | |
clive
![]() 2766 posts |
postal in post 153554 said:It defaults to 60 seconds, but can be configured on a per-entry-point basis. Developers see ENT-ECT and ENT-EDT. Basically, the ID turns grey at the point when the sim makes a decision that the train is going to enter or not. The 60 seconds (or configured value) represent the time between the train being committed (when it passed the last opportunity to be reversed or sent another way) and it actually reaching the entry point. If the entry point was in a long length of automatic signals, it might be configured to several minutes rather than 60 seconds. postal in post 153554 said: Not so much indigestion as having confusing results. I *think* the core code first checks applicable rules, which will cause one or the other train to be selected, and then applies decisions. It can make sense to have both (e.g. when they're alternatives on the same day of the week or if a special decision has been used because the trains only run if a specific option has been chosen). But you need to be careful and know what you're doing AND have tested it in a simple timetable before using it for real. Log in to reply The following user said thank you: postal |