Page 1 of 1
Marylebone Platform Berths not showing 13/06/2017 at 10:38 #95822 | |
slatteryc
254 posts |
Loader 4.6.3 Marylebone 3.6 Standard Timetable. Berth 5 should have 1h27 and 2h29 ( they are currently joining ) . No berth occupation before [ 1h27 was in there ] and no berth occupation after [ when 2H29 went in ] Save attached.. Imgur link to scene pic http://imgur.com/a/stJ1w Post has attachments. Log in to view them. Last edited: 13/06/2017 at 10:41 by slatteryc Reason: None given Log in to reply |
Marylebone Platform Berths not showing 14/06/2017 at 04:03 #95836 | |
BarryM
2158 posts |
slatteryc in post 95822 said:Loader 4.6.3I"m sorry, I do not follow your problem. F2 shows the two train joining in Platform 5. Clicking on 2H29's head code tells you the next service the joining trains will form, 2B21. If it is to do with headcodes we need a save before these trains arrived at Marylebone. You supplied 2 saves of the same name! Barry Barry, Sydney, New South Wales, Australia Last edited: 14/06/2017 at 04:08 by BarryM Reason: None given Log in to reply |
Marylebone Platform Berths not showing 15/06/2017 at 13:14 #95848 | |
slatteryc
254 posts |
Hi and thanks for responding. Yes I Posted 2 saves sorry. Agree ref F2 - trains are showing in the list OK. That is not the issue ; look at the Platform Berth Indicator at right for Marylebone - P5 shows as completely empty when it is not <- that is the actual issue. The trains themselves are behaving perfectly OK. Log in to reply |
Marylebone Platform Berths not showing 15/06/2017 at 13:35 #95849 | |
Danny252
1461 posts |
But the berth is empty - there's no train description displayed in the country end berth. Until you input the correct TD, it will stay empty. (Unless ACI should have put in the new TD, but that's not usually handled for joining trains) Log in to reply |
Marylebone Platform Berths not showing 15/06/2017 at 19:03 #95853 | |
slatteryc
254 posts |
but the berth isnt empty ? So far ACI has been handling it perfectly - and it does, for the most part. Its this one instance in P5 alone thats buggy AFAICS
Log in to reply |