Tyneside Q&A and issues

" said:

I agree, timetable rules and Google suggest that platform should be much longer than 188m (the current length of the two TCs). Mantis 15667 applies.

2016 Rules of the Plan gives:

Darlington P1 354m. Up direction
Darlington P1 347m. Down direction to T887 signal
Darlington P2 181m.
Darlington P3 200m.
Darlington P4 458m. Both directions
Darlington P4 238m. Up direction to T888 signal
Darlington P4a 134m. Down direction to T895 signal
Darlington P4b 251m. Down direction clear of 1080B points

When chained to York, up trains transferring from Tyneside don't appear to pick up their Current/Next location - trains due to stop at Northallerton are whizzing through non-stop as the York sim thinks the train is still at "Up Main (Darlington)". If the train gets as far as York it sits at a red signal and then calls in to say it's waiting. Down trains transferring from York to Tyneside are fine.

Not sure whether this is a send (Tyneside) or receive (York) problem or a combination of both, so have reported it here. I've got both sims open on the same PC with server enabled, Tyneside using the preset primary port and York using the preset secondary port.

I've worked around this by manually updating the Current/Next location via Edit Timetable. On one occasion I was late editing a TPX due to stop at Northallerton and the edit was accepted on approach to Northallerton - the train managed to go from 100mph to 88mph within five seconds and then dropped to 0mph in less than a second! Seems the brakes are decent on 185's but I wouldn't have wanted to be on board.... ;)

When I chained up york and tyne trains passing Darlington and south JN do not show in york F2 even tho it does when NOT chained at this point, it will be a signal or 2 before northallerton before york sees it as being on the sim and announce it's entry.

" said:

" said:

I agree, timetable rules and Google suggest that platform should be much longer than 188m (the current length of the two TCs). Mantis 15667 applies.

2016 Rules of the Plan gives:

Darlington P1 354m. Up direction
Darlington P1 347m. Down direction to T887 signal
Darlington P2 181m.
Darlington P3 200m.
Darlington P4 458m. Both directions
Darlington P4 238m. Up direction to T888 signal
Darlington P4a 134m. Down direction to T895 signal
Darlington P4b 251m. Down direction clear of 1080B points

Same as what SimSig wiki shows Here

Just wondering if this sim should be coded such that fringe signallers call ahead to request early trains to keep coming or be held until time?

I have 6E01 sitting at Metro Centre 19" early waiting crew relief. 2N06 behind and will cop about a 20" delay.

" said:

Just wondering if this sim should be coded such that fringe signallers call ahead to request early trains to keep coming or be held until time?

I have 6E01 sitting at Metro Centre 19" early waiting crew relief. 2N06 behind and will cop about a 20" delay.

Given that once you've left Carlisle there's nowhere to loop anything they probably shouldn't appear out of order from this entry point. Calling in to let you know is possible but if you hold the freight then everything behind it gets held too.

Just wondering if this sim should be coded such that fringe signallers call ahead to request early trains to keep coming or be held until time?

I have 6E01 sitting at Metro Centre 19" early waiting crew relief. 2N06 behind and will cop about a 20" delay.

Given that once you've left Carlisle there's nowhere to loop anything they probably shouldn't appear out of order from this entry point. Calling in to let you know is possible but if you hold the freight then everything behind it gets held too.

2N06 must be running late. Timed to enter at 08:00½. 6E01 is timed to enter at 08:12. A rule is needed?

Barry

Strange happenings with East Bolden CCTV. Some trains activate the lowering of the barriers. Has anybody noted this?

Any explanation?

Barry

I'm currently playing the default timetable with a start time of 00:00 and I think somehow SimSig has invented time travel!

But before anyone gets excited, it's only because the sim doesn't yet differentia between services that use the same headcode but different timings for example 0N05 is seeded in the Newcastle station area and every time I've played this so far, the driver askes to leave around 8hrs early yet it's return working shares the same headcode so once the first train is activated in the sim, it assumes that the return working has also run....

I think this is a bug in the sim because I've recently completed a good many hours on the 1982 TT for the Victoria Central sim which shares the same headcode for a number of different services but it doesn't have the same issue as Tyneside does.

I know there's a easy fix in adding a number to the headcode of every service to separate them but I still feel this is a bug on the sim.

" said:

I'm currently playing the default timetable with a start time of 00:00 and I think somehow SimSig has invented time travel!

But before anyone gets excited, it's only because the sim doesn't yet differentia between services that use the same headcode but different timings for example 0N05 is seeded in the Newcastle station area and every time I've played this so far, the driver askes to leave around 8hrs early yet it's return working shares the same headcode so once the first train is activated in the sim, it assumes that the return working has also run....

I think this is a bug in the sim because I've recently completed a good many hours on the 1982 TT for the Victoria Central sim which shares the same headcode for a number of different services but it doesn't have the same issue as Tyneside does.

I know there's a easy fix in adding a number to the headcode of every service to separate them but I still feel this is a bug on the sim.

I don't quite understand what the problem is that you are having. Are you saying that 0N05 is asking to leave 8 hours early and you're given the option to tell him to wait for booked time? If so that's fairly standard behavior across all sims.

I've not had any issues with the return half of 0N05 entering the simulation, even though it's marked as having entered because a train with that UID has already run. (Which isn't in itself a bug if you look at the real schedule it's actually one schedule, split for SimSig purposes)

Issues with 0N05 seeding have been reported here. But at the same time I don't get told 0N07 or 0N05 have been seeded if they haven't.

A train being marked as grey in the timetable doesn't necessarily mean a train has run, or entered. 0N05 and 0N07 are mutually exclusive, so if 0N05 seeds, 0N07 also gets marked as grey, as it won't be entering. Because 0N05 shares a UID, the second (or third, fourth etc) are also marked as grey as far as the sim is concerned that schedule has entered. Again I've had no problem with the second portion entering (nor have I had problems in other simulations with similar situations in the timetable.)

" said:

Issues with 0N05 seeding have been reported here. But at the same time I don't get told 0N07 or 0N05 have been seeded if they haven't.

A train being marked as grey in the timetable doesn't necessarily mean a train has run, or entered. 0N05 and 0N07 are mutually exclusive, so if 0N05 seeds, 0N07 also gets marked as grey, as it won't be entering. Because 0N05 shares a UID, the second (or third, fourth etc) are also marked as grey as far as the sim is concerned that schedule has entered. Again I've had no problem with the second portion entering (nor have I had problems in other simulations with similar situations in the timetable.)

Then why can't the services be shown as 0N07-1 for the first part of the schedule and 0N07-2 for the second part, I can't see why services have to share a UID - I'm not being difficult I just can't see why they ought to.

Surely that is what the rules tool is for so if 0N05 enters then 0N07 won't be grayed out because it won't have entered.

" said:

" said:

Issues with 0N05 seeding have been reported here. But at the same time I don't get told 0N07 or 0N05 have been seeded if they haven't.

A train being marked as grey in the timetable doesn't necessarily mean a train has run, or entered. 0N05 and 0N07 are mutually exclusive, so if 0N05 seeds, 0N07 also gets marked as grey, as it won't be entering. Because 0N05 shares a UID, the second (or third, fourth etc) are also marked as grey as far as the sim is concerned that schedule has entered. Again I've had no problem with the second portion entering (nor have I had problems in other simulations with similar situations in the timetable.)

Then why can't the services be shown as 0N07-1 for the first part of the schedule and 0N07-2 for the second part, I can't see why services have to share a UID - I'm not being difficult I just can't see why they ought to.

Surely that is what the rules tool is for so if 0N05 enters then 0N07 won't be grayed out because it won't have entered.

Unique IDs are a Network Rail invention in effect. Each schedule on the network has an ID, and SimSig uses these as the Unique ID. Trains like RHTTs, light loco moves for crew training, sandite trains, test trains, are all one large schedule. SimSig splits these down where required, like 0N05 where it leaves the simulation, and comes back later, but they share the same UID as it's the same train, both portions can't be in the simulation at the same time!

" said:

" said:

" said:

0N05 and 0N07 are mutually exclusive, so if 0N05 seeds, 0N07 also gets marked as grey, as it won't be entering.

Then there should be rules put in so if 0N05 appears then 0N07 must appear/must not appear, simples :)