Page 1 of 1
| Strange seeding behaviour - Exeter New Yard 05/02/2019 at 18:26 #115383 | |
WesternChampion
173 posts 
|
Last week I created a timetable for Sunday, 27th January using Real Time Trains data, amending a timetable previously uploaded for Sunday 11th November, created by AlexRail575. I've just started a first test on this and noticed something strange occurring. I had a train seeding at Sig E668 in Exeter New Yard. Shortly after launching, a message appears that the train is stopped at Sig E702 at Newton Abbot East Junction. I ran it a couple of times and the same thing happened, so I changed the seeding point to E645 (the other end of the siding) and all works fine. That has resolved the issue with this TT but just thought Peter should be aware in case a tweak is needed. Chris Log in to reply |
| Strange seeding behaviour - Exeter New Yard 05/02/2019 at 19:10 #115384 | |
headshot119
4869 posts |
Reported on Mantis as 23370 for Peter's attention.
"Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer Log in to reply |
| Strange seeding behaviour - Exeter New Yard 05/02/2019 at 20:54 #115389 | |
Peter Bennet
5402 posts |
Thanks, most of the shunt signals were wrongly numbered when the Sim was first built and I fixed that by using aliases (overriding the ID), unfortunately, it appears there is a glitch whereby the original ID is still used for seeding and not the alias. Peter I identify as half man half biscuit - crumbs! Log in to reply |
| Strange seeding behaviour - Exeter New Yard 05/02/2019 at 22:10 #115394 | |
9pN1SEAp
1180 posts |
Added a link to this thread on my earlier report: https://www.SimSig.co.uk/Forum/ThreadView/48923?postId=115393 so people know it's fixed 
Jamie S (JAMS) Log in to reply |
| Strange seeding behaviour - Exeter New Yard 05/02/2019 at 22:16 #115395 | |
|
headshot119
4869 posts |
There is no indication in this thread that the issue has been fixed.
"Passengers for New Lane, should be seated in the rear coach of the train " - Opinions are my own and not those of my employer Log in to reply |
| Strange seeding behaviour - Exeter New Yard 05/02/2019 at 23:59 #115397 | |
kaiwhara
587 posts |
This is an almost identical report to one I raised earlier relating to 669 Signal (which also caused trains to appear at Newton Abbot. Refer Mantis 15471). I have associated these tickets accordingly. I suggest a revisit of all signal ID's as there will likely be others. Sorry guys, I am in the business of making people wait! Last edited: 06/02/2019 at 00:01 by kaiwhara Reason: None given Log in to reply |
| Strange seeding behaviour - Exeter New Yard 06/02/2019 at 07:07 #115405 | |
|
Peter Bennet
5402 posts |
kaiwhara in post 115397 said:This is an almost identical report to one I raised earlier relating to 669 Signal (which also caused trains to appear at Newton Abbot. Refer Mantis 15471). I have associated these tickets accordingly.Virtually all shunt signals needed correction. Peter I identify as half man half biscuit - crumbs! Log in to reply |
| Strange seeding behaviour - Exeter New Yard 06/02/2019 at 10:43 #115408 | |
axmh
61 posts |
Does that mean all the wtts that are available in the Timetable section will have to be rewritten ??
Log in to reply |
| Strange seeding behaviour - Exeter New Yard 06/02/2019 at 10:59 #115409 | |
|
Peter Bennet
5402 posts |
If they seeded correctly before they should still seed at the same signal, it's just that the seed description will appear to be referring to the wrong signal. So train booked to seed at Signal with ID E123 will continue to seed at that signal albeit that the signal has since been given an alias of E456. If signal ID E100 has been given the alias E123 the train will not seed at that signal. Hopefully this can be fixed in the Core Code. Peter I identify as half man half biscuit - crumbs! Last edited: 06/02/2019 at 11:01 by Peter Bennet Reason: None given Log in to reply |
| Strange seeding behaviour - Exeter New Yard 06/02/2019 at 11:56 #115411 | |
|
clive
2789 posts |
Peter Bennet in post 115389 said:Thanks, most of the shunt signals were wrongly numbered when the Sim was first built and I fixed that by using aliases (overriding the ID), unfortunately, it appears there is a glitch whereby the original ID is still used for seeding and not the alias.Not a glitch. You can set the name in the seeding list separately from the alias (SIG-SDI versus SIG-NAM). This allows you to name a seeding point "Platform 2 south end" or suchlike if you want. Log in to reply |
| Strange seeding behaviour - Exeter New Yard 06/02/2019 at 12:09 #115413 | |
|
Peter Bennet
5402 posts |
clive in post 115411 said:Peter Bennet in post 115389 said:Indeed but that'd then requires every wrong signal to have both SID and NAM data rather than simply having NAM as being superior to the ID which seems the more logical. Anyway the point is on Mantis already.Thanks, most of the shunt signals were wrongly numbered when the Sim was first built and I fixed that by using aliases (overriding the ID), unfortunately, it appears there is a glitch whereby the original ID is still used for seeding and not the alias.Not a glitch. You can set the name in the seeding list separately from the alias (SIG-SDI versus SIG-NAM). This allows you to name a seeding point "Platform 2 south end" or suchlike if you want. Peter I identify as half man half biscuit - crumbs! Log in to reply |