Page 1 of 1
| Incorrect seeding on LULVictoria Line bundled timetable - Saturday Engineering v4.1 10/01/2021 at 10:03 #136175 | |
rfw
177 posts |
Hello, I was just playing through a game on LUL Victoria Line with sim version: v4.2 build 2 Loader version: 5.13 and Timetable: Victoria Line 2009 - Saturday Engineering v4.1 The problem I ran into upon loading the Sim up is V243-0 and V245-0 which are seeded at platforms 1&2 of Brixton have the wrong timetable or the wrong trains are seeded. Both trains immediately report in the messages window waiting at a red signal and then telephone about it, if these signals are cleared the trains proceed off of the planned path and down the line 30 minutes before they (or the next programmed service) should. They don't wait at intermediate stations due to having the set down only (d) flag set. This is caused by the -0s being seeded at brixton platforms in the down direction, with their first location being Brixton sidings - which is up of Brixton and already occupied with another train. Because of the mismatch between the location seeded and the timetable locations, so the sim just tries to run the trains forward until they reach their next location, which the never do. If it is a an incorrect timetable, then V243-0 and V245-0 should not have Brixton sidings in their locations, just Brixton with the new train tag. If it is the wrong train seeded then it should be V243-1 and V245-1 seeding at the same locations in place of V243-0 and V245-0 A third possible fix, which is less likely to happen, is for a core code developer to change how SimSig handles trains running to be more self aware of where they are in relation to the timetable, like ARS can realise when a train leaves the timetabled route. Such that when a train is seeded in the incorrect timetable step, which may in turn break many other timetables that make use of seed points that aren't quite in the right location for the intended action - I know I've done some weird stuff with seeding. But this won't happen as the error is not with the core code, but with the timetable and I don't foresee time being taken to rewrite a core element of how the programs operates to allow for some error correction for people that made mistakes when making TTs and possibly break some quirky timetables over more important features. Please could someone fix as it is a timetable bundled with the simulation -RW The train now standing on platform 2, should be on the rails Log in to reply |
| Incorrect seeding on LULVictoria Line bundled timetable - Saturday Engineering v4.1 10/01/2021 at 10:59 #136178 | |
Peter Bennet
5402 posts 
|
I'll have a look into the point though strangely I can't even get the Sim to run as there are keys code in the data that appear to have been made redundant in September. Peter I identify as half man half biscuit - crumbs! Log in to reply |
| Incorrect seeding on LULVictoria Line bundled timetable - Saturday Engineering v4.1 10/01/2021 at 13:33 #136184 | |
bill_gensheet
1413 posts
|
rfw in post 136175 said:Hello,What looks the most likely to me is a hang over from how seeding was done early on. Then you needed an extra train with a preceding call, but do not now. Delete V243-0 Edit V243-1 to seed at sig VE2 Delete V245-0 Edit V245-1 to seed at sig VE4 Bill Log in to reply |
| Incorrect seeding on LULVictoria Line bundled timetable - Saturday Engineering v4.1 10/01/2021 at 17:02 #136197 | |
|
Peter Bennet
5402 posts
|
Stephen Fulcher in post 136192 said:
Yeah - I have a build 12, that's where my problem was. Anyway, Bill seems to have identified the problem. Bill, can you submit the fix to the tester upload page please and Karl or Geoff can take it from there all being well. Thanks. Peter I identify as half man half biscuit - crumbs! Last edited: 10/01/2021 at 19:26 by GeoffM Reason: Quote removed Log in to reply |
| Incorrect seeding on LULVictoria Line bundled timetable - Saturday Engineering v4.1 10/01/2021 at 17:28 #136204 | |
|
bill_gensheet
1413 posts
|
Ok will do. I'd better check the other TT's too. Added a foot note in the description and set the version to 4.2. Bill Log in to reply |