Page 1 of 1
| Issue chaining Kings Cross and Peterborough 19/02/2019 at 08:56 #115859 | |
ajax103
1120 posts |
I've got the August 2012 timetable in my collection and am trying to do a chain on my laptop to get the two sims together using the timetable mentioned. Now the first issue I had was that while it appeared for Kings Cross with all the other timetables, it wouldn't show up for Peterborough. So what I did was open up Peterborough with no timetable then load the 2012 one and save it as a separate timetable, all good... However while Kings Cross seems to be connected to Peterborough, it has again brought up a error which I don't understand which shows up on the Kings Cross built in message tool as "chaining arrangements inconsistent" and on the Peterborough sim it has a pop up error message as "Kings Cross Chaining Arrangements Inconsistent". I'm using Peterborough with the Bi Di active between Peterborough and Werrington Junction with the Modern Era for Kings Cross so can't see why there is a problem? I have also tried chaining the two using the old eras in both and the same error comes up so for now, it's impossible to have any session with the two chained up - does anyone know why there's a issue? Log in to reply |
| Issue chaining Kings Cross and Peterborough 19/02/2019 at 10:25 #115863 | |
headshot119
4869 posts |
Reported on Mantis 023582. As many people have hosted this chain over the years I suspect it works on the whole so why not give it a go?
"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 |
| Issue chaining Kings Cross and Peterborough 19/02/2019 at 10:31 #115864 | |
Edgemaster
332 posts |
I've hosted these two before (on a different timetable, I think), received the chaining details inconsistent warnings, clicked through them all, and it seemed to work fine.
Log in to reply |
| Issue chaining Kings Cross and Peterborough 19/02/2019 at 10:37 #115865 | |
|
ajax103
1120 posts |
It's the first I've ever seen any sim state that hence why I asked, didn't know it had been raised on Mantis 
Log in to reply |
| Issue chaining Kings Cross and Peterborough 19/02/2019 at 11:54 #115866 | |
|
Edgemaster
332 posts |
ajax103 in post 115865 said:It's the first I've ever seen any sim state that hence why I asked, didn't know it had been raised on Mantis :(No, headshot119 was saying that he'd just raised the issue on mantis, in response to your post. It does seem to have been reported on the forums before here, and it was reported that: headshot119 in post 96132 said: The two chain and pass trains and TDs correctly between them.The versions reported on that thread were King's Cross: 3.4 and Peterborough: 4.1 build 3. Current versions are King's Cross: 3.4 and Peterborough: 4.1 build 4. Did the planned King's Cross update stall? Log in to reply |
| Issue chaining Kings Cross and Peterborough 19/02/2019 at 12:58 #115867 | |
clive
2789 posts |
Let me summarize the situation (as the author of Peterborough). Firstly, this messages indicates that the two sims disagree on exactly what happens when during chaining. This could mean that chaining is completely broken or it could mean there's a minor cosmetic issue. (The core code isn't clever enough to know which.) In this case, it was supposed to be fixed in the next release. I tested this issue in 2017 against the latest development builds of King's Cross and Peterborough and it had gone away. The current Peterborough release is based on that data but, it seems, the current King's Cross is older. Once KX is re-released the problem will go away. As others have said, I think you'll find the chain will work in that trains pass across correctly, even if things don't always look quite right. Log in to reply The following user said thank you: ajax103 |
| Issue chaining Kings Cross and Peterborough 19/02/2019 at 15:18 #115868 | |
|
ajax103
1120 posts |
clive in post 115867 said:Let me summarize the situation (as the author of Peterborough). Firstly, this messages indicates that the two sims disagree on exactly what happens when during chaining. This could mean that chaining is completely broken or it could mean there's a minor cosmetic issue. (The core code isn't clever enough to know which.)I don't suppose there's any news on when Kings Cross will be re-released or what changes are being planned for it? Personally the one change I hope is coming is a crossover at Hertford to allow Down Hertford to Platform 1 moves without needing to shunt. Log in to reply |
| Issue chaining Kings Cross and Peterborough 26/03/2019 at 13:21 #116788 | |
|
ajax103
1120 posts |
Recursive bug report: Cross boundary T3731 not found Recursive bug report: Cross boundary T3533 not found Recursive bug report: Cross boundary T3631 not found Recursive bug report: Cross boundary T3721 not found Recursive bug report: Cross boundary T3621 not found Recursive bug report: Cross boundary T3523 not found Recursive bug report: Cross boundary T3533 not found Recursive bug report: Cross boundary T3721 not found Not sure if these bug reports have already been noted or not but it's what I get when I chain the two together. Sorry to be a pain
Log in to reply |
| Issue chaining Kings Cross and Peterborough 26/03/2019 at 14:35 #116791 | |
|
Edgemaster
332 posts |
Yes, these have been noted previously.
Log in to reply The following user said thank you: ajax103 |
| Issue chaining Kings Cross and Peterborough 27/03/2019 at 00:08 #116821 | |
|
DavidSplett
142 posts |
ajax103 in post 115868 said:clive in post 115867 said:I’m really hoping it’s going to be possible to introduce an up-to-date KX era, as soon it’s going to become harder to do up-to-date timetables, and if changes are made in the future then those timetables already written may need to be modified to make them work.Let me summarize the situation (as the author of Peterborough). Firstly, this messages indicates that the two sims disagree on exactly what happens when during chaining. This could mean that chaining is completely broken or it could mean there's a minor cosmetic issue. (The core code isn't clever enough to know which.)I don't suppose there's any news on when Kings Cross will be re-released or what changes are being planned for it? The Hertford changes, north end of Hornsey Depot and Canal Tunnels double junction are the main ones, and in the near future Stevenage fifth platform. A more authentic reception layout for Letchworth sidings would also be appreciated. For current timetables there would also been a benefit in having ACI at Baldock, Watton-at-Stone and Langley Junction reversing berth. Another couple of things, the down starter from Finsbury Park platform 8 I don’t believe is approach controlled in real life for the route to the down slow, and both Drayton Park starters appear to be approach controlled in real life (presumably to enforce trains stopping to make the changeover). Potters Bar DF junction signal also now has a flashing yellow for the diverging route as of a few years ago. Incidentally I’m testing a Summer 2019 KX timetable at the moment. Thusfar it’s working rather nicely, seems to run a bit more seamlessly than the last two, perhaps due to timing tweaks in real life which make everything fit together that little bit better. Log in to reply The following user said thank you: ajax103 |
| Issue chaining Kings Cross and Peterborough 27/03/2019 at 10:04 #116824 | |
|
clive
2789 posts |
DavidSplett in post 116821 said:According to sources, at present K393 (FP starter) is MAF (i.e. explicitly no approach control) to down slow 2 and no approach control to down slow 1; K360 and K361 at Drayton Park don't have approach control and do have auto buttons (though that doesn't mean the signallers use them). Log in to reply |
| Issue chaining Kings Cross and Peterborough 27/03/2019 at 13:13 #116830 | |
|
DavidSplett
142 posts |
clive in post 116824 said:DavidSplett in post 116821 said:The K393 notes would support my observations. Drayton Park I’m less sure about, I’ve never seen either starter clear until a train has come to a stand in the platform, might be worth some further investigation into this.According to sources, at present K393 (FP starter) is MAF (i.e. explicitly no approach control) to down slow 2 and no approach control to down slow 1; K360 and K361 at Drayton Park don't have approach control and do have auto buttons (though that doesn't mean the signallers use them). Another thing which would be useful on any updated sim is an option to select “DCF” as a line at Hitchin (as in Down Cambridge Flyover), and a timing point for Hitchin East Junction to denote anything booked to use the old route. A “Wood Green K451” timing point would also be useful. Log in to reply |