Page 1 of 1
| Core Code Timetable Editing Bug(s)? 04/09/2011 at 13:41 #20571 | |
Danny252
1461 posts |
Since the new core code came out, I've been noticing some odd behaviour when editing timetables of trains already in the sim. I've had locations mysteriously moving from the bottom of the list to the top, trains incorrectly picking up on new locations, and so forth. The examples below are NLL, but I've had both bugs appear on the newly released SwinDid, which I believe is meant to be built on the latest core code? A couple of examples: Set "Gunnersbury" as next location for a train at Richmond on the NLL, and the train drives to the signal at the end of the Richmond platform. It stops, claims it is "stopped at Gunnersbury", and then reverses and promptly hits the buffers. -- A train is given the timetable: Richmond Gunnersbury South Acton Acton Central Acton Wells Jn Willesden High Level Kensal RIse Brondesbury Park. Upon finishing editing of the TT, the last two mysteriously jump to the top of the list. Log in to reply |
| Re: Core Code Timetable Editing Bug(s)? 04/09/2011 at 13:43 #20573 | |
|
Sam Tugwell
494 posts |
I have had a similar issue when testing an early version of my Brighton timetable. Tugz "Signalman Exeter" Log in to reply |
| Re: Core Code Timetable Editing Bug(s)? 04/09/2011 at 14:08 #20575 | |
Peter Bennet
5402 posts |
It possibly means the internal locations are numbered out of sequence in the Sim data. It normally shows up when you use 00.00 times and non-key locations. The Core Code used to be less picky about these things in the past. If you can give me a specific sequence within SwinDid I can have a look and see if that's the problem. Peter I identify as half man half biscuit - crumbs! Log in to reply |
| Re: Core Code Timetable Editing Bug(s)? 04/09/2011 at 14:15 #20577 | |
|
Danny252
1461 posts |
Attached Swindid save. To get the bug to appear: Edit 1M181's Timetable. Add "Didcot E (Rev) Sig SB6404...", Path DR, Line DR, Time 00:00. Edit Didcot North Jn Path from CL to AL. Accept changes, close TT Editor, open Editor/View TT. The 4 Locations between Moreton Cutting Jn and Didcot E (Rev) have now jumped to the top of the list. Post has attachments. Log in to view them. Last edited: 04/09/2011 at 14:16 by Danny252 Log in to reply |
| Re: Core Code Timetable Editing Bug(s)? 04/09/2011 at 14:21 #20578 | |
|
Danny252
1461 posts |
And for the incorrect stopping bug, another Swindid. Change 1B841's "Next Location" to Bourton. It will stop at Swindon P3, report "Stopped at Bourton" at location "Bourton", followed by "Stopped at Highworth Jn", followed by "Stopped at Swindon". This makes it impossible to reverse a train, as it will just roll through the locations until it reaches its current one. Post has attachments. Log in to view them. Log in to reply |
| Re: Core Code Timetable Editing Bug(s)? 04/09/2011 at 14:58 #20579 | |
|
Peter Bennet
5402 posts |
" said:Attached Swindid save.Well it will if you put in 00.00 but leave the stops at these other stations at a later time. The only reason it does not re-order the other stations as that they are KEY locations and are mapped internally in a specified order. Stick a time in for SB6404 and all will be well. If the numbering was out and the 4 non-key stations had 00.00 times then they would be re-ordered into the number sequence. Peter I identify as half man half biscuit - crumbs! Log in to reply |
| Re: Core Code Timetable Editing Bug(s)? 04/09/2011 at 15:03 #20580 | |
|
Peter Bennet
5402 posts |
" said:And for the incorrect stopping bug, another Swindid.I'm a little perplexed as to why you would do what you have done, if you tell it the next stop is Bourton after it has passed Bourton (by a long way) then no wonder it gets confused- though it does seem to sort itself out at Swindon. Peter I identify as half man half biscuit - crumbs! Log in to reply |
| Re: Core Code Timetable Editing Bug(s)? 04/09/2011 at 15:30 #20581 | |
|
Danny252
1461 posts |
" said:" said:I'm rather sure that previously you could set a train to a previous stop, and then reverse it or similar - whether due to wrong routing or some failure cropping up.And for the incorrect stopping bug, another Swindid.I'm a little perplexed as to why you would do what you have done, if you tell it the next stop is Bourton after it has passed Bourton (by a long way) then no wonder it gets confused- though it does seem to sort itself out at Swindon. Log in to reply |