Page 1 of 1
| KX chain headcode bug 23/12/2012 at 17:12 #39567 | |
Hawk777
386 posts |
When trains are heading for King's Cross in a chained multiplayer game, as the train passes Ashwell and Mordon, the headcode spontaneously changes to **** on both sims.
Log in to reply |
| KX chain headcode bug 25/12/2012 at 00:18 #39644 | |
|
Lardybiker
771 posts |
What versions of each sim are you running?
Log in to reply |
| KX chain headcode bug 25/12/2012 at 01:13 #39646 | |
|
Hawk777
386 posts |
I can’t speak for the host, but I was running the latest of both—Royston 2.5 and KX doesn’t show a version number at startup but I only downloaded it a few days ago. I would guess the host was running the latest of both as well, since otherwise the client wouldn’t connect. We actually had that exact problem earlier in the session where nobody could connect to Royston because the host was running an old version, but (s)he updated and then it worked.
Log in to reply |
| KX chain headcode bug 25/12/2012 at 01:25 #39647 | |
|
Lardybiker
771 posts |
This ones for Clive I think as Royston And Cambridge are built from the same basic code. If you chain the latest available Cambridge and Kings Cross, do you get the same problem?
Last edited: 25/12/2012 at 01:26 by Lardybiker Log in to reply |
| KX chain headcode bug 25/12/2012 at 07:28 #39649 | |
|
Hawk777
386 posts |
Chaining with Cambridge does not have the same the problem. Possibly of note is that KX has, on the up line, two thin grey lines right up until signal 970 (just in rear of Ashwell and Morden), then solid grey lines for track through the station and beyond. Cambridge has the exact inverse, solid grey lines up until signal K970 followed by two thin grey lines through the station and beyond. Royston, on the other hand, has solid grey lines all the way until K960, just in rear of Baldock. I have no idea if this is purely stylistic or if it reflects something in the underlying code (perhaps a difference in the location where the sims believe they own a particular headcode). Signal 970 is exactly where the problem happens: the headcode changes to **** as the train passes that signal. Another data point: Royston can interpose a headcode at K968 (the berth at Ashwell and Morden itself) or K966 (the berth just in advance of the station). If it does so, then **** appears in KX in the corresponding berth, and when the train steps forward, the **** (in KX) steps normally and the interposed headcode at Royston vanishes and is replaced with ****. On the other hand, if Royston interposes in those berths with no train approaching, there is nothing visible at KX: not even ****. Finally, both KX and Royston believe K964 to be external berths which cannot be interposed. Interposing into 962 can be done at KX and not Royston, and the interposed headcode appears properly on Royston as well. It doesn’t matter which sim is the master and which is the slave in the chain; the problem happens either way. Log in to reply |