Version 1.2.1 issues

General comment: not everything reported is fixed by the next release, especially with this WIP. If you've already reported it then it probably does not need reporting again.

Here's a couple of issues that I reported just before version 1.2.1 was released and which haven't been fixed, so thought I'd start a new thread for version 1.2.1 of the sim.

1) Trains from Unanderra which have a scheduled stop at Moss Vale Jct and need to be routed via the North Fork, call Wrong Route even when NF is chosen as the Moss Vale Jct platform. If the route is set via the Branch, then the route is accepted and the train makes its scheduled stop at signal MV35, which doesn't make sense. Train TM71 is an example.

2) Trains approaching Stockinbingal from Milvale call in with the message "Driver of [none] to Junee Control. We're approaching Stockinbingal.", but they do this as they are passing through Stockinbingal. Train 1PS6 is an example.

For info, I'm running v1.2.1 of the sim/timetable and v4.8.2 of the Loader.

Here's another issue I've come across:

Trains routed from Signal MV26 and MV24 to signal 34.6 (Moss Vale North Fork & Branch towards Unanderra) always stop at the Branch LOS board and ask for permission to pass it.

This one's a query, but it may be an issue: Why do trains departing Cootamundra P1 towards Junee always ask for permission to depart from signal CA69, which is a main aspect signal?

First of all, thank you for your feedback.

I just want to take this opportunity to support Geoff's statement that not all bugs identified will be fixed in the very next release or the one after (etc). Given this is "the new world" (for SimSig) and quite a departure from UK practice, much new code has had to be created and existing stuff modified. Some of those are still on the drawing board and let me say some issues have caused aspirin sales to skyrocket!! :-O. We're getting there.

There are some timetable issues which are being fixed as they are discovered. These are trains that travel via Moss Vale North Fork being incorrectly timetable at Moss Vale Jn (which only applies to traffic NOT traversing the fork). Most have been fixed. Could you please provide actual train ID's that are still doing this. Thank you.

Mattyq in post 111500 said:

First of all, thank you for your feedback.

I just want to take this opportunity to support Geoff's statement that not all bugs identified will be fixed in the very next release or the one after (etc). Given this is "the new world" (for SimSig) and quite a departure from UK practice, much new code has had to be created and existing stuff modified. Some of those are still on the drawing board and let me say some issues have caused aspirin sales to skyrocket!! :-O. We're getting there.

There are some timetable issues which are being fixed as they are discovered. These are trains that travel via Moss Vale North Fork being incorrectly timetable at Moss Vale Jn (which only applies to traffic NOT traversing the fork). Most have been fixed. Could you please provide actual train ID's that are still doing this. Thank you.

Working in this "new world" must involve a very steep learning curve, but you're certainly getting there. I obviously don't expect issues I report to be fixed immediately, but not having access to the Mantis system, I only know that a reported issue has been noted when I see a reply to my post. What I report may be a sim issue, a timetable issue or not even an issue at all, so it is important that a feedback reply is made, which is what you've done above. Thanks for that.

As requested, here's a list of trains using the North Fork that still reference Moss Vale Jct. in the timetable: TM71 (2 instances), TM72 and TM93.

I've found some issues with trains departing Medway Quarry and also with some trains at Berrima Jct. which I suspect are probably timetable issues. I'll get some more information regarding these and make a new post.

Hi Mattyq,

I've got more information regarding the problem where trains sometimes incorrectly stop at the Moss Vale Branch LOS Board. I've cobbled the standard timetable to start off with 3 seeded trains. One scheduled to use the North Fork (TM98), one to use the Branch (8926) and one that is already in the Calwalla area (8924). All 3 are scheduled to head away from Moss Vale. I believe it is the position of the latter train that causes the problem.

I've found that if 8924 is seeded at signal 34.6, given clear signals and TM98 immediately routed behind it, then TM98 always stops at the Branch LOS Board. However, if 8924 is seeded at signal 34.28 (Calwalla Loop) and the same procedure followed, then TM98 behaves correctly. I've run both these scenarios several times and always got the same results, which is good news. I've included some saves in the attached zip file.

When I cleared the signals for 8926 (and there's another issue with that, see later), then 8926 behaved correctly, but when it was routed behind the correctly behaved TM98, then it stopped at the LOS Board! It looks to me that it could be the position of the train in front that is critical.

One thing I have noticed is that for trains coming off the Fork, the TD steps to the LOS Board, but coming off the Branch it steps straight to the berth between signals 34.6 and 34.6Dist, which might be significant.

I've attached a zip file with 2 timetables and 4 saves for you to play with. The filenames should be self-explanatory.

Now for two issues that came to light during my "testing".

1) If I try and set a route from MV44 to MV24 I always get "No overlap available", even when I've set and locked the points. However, if I first set a route from MV24 to 34.6, I can then set the route from MV44 to MV24, and when I cancel the advance route, the overlap for MV44 appears in Yellow. Is this how it's supposed to work?

2) If I bring a long train from MV17 to MV26 and hold it there to allow a train to come off the Branch, then the overlap for MV17 never times out (even when I cancel the route from MV17) and I get "Points locked normal by another route" when I try to set a route from MV26. Is this correct behaviour?

I'll report on the Medway Jct and Berrima Jct timetable issues when I've got more details.

I hope the above info is useful to you.

With regards to Berrima Jn, a few issues have been identified here.
1. Trains heading south stopping across the main line points, similar to Medway Jn.
2. Some trains required to set back behind BJ82 then proceed to Picton don't fit between BJ82 and the LOS.

With regard to item 2, there are a number of considerations here. We are double-checking train lengths but it is highly likely they are correct. For trains that are overlength, you have two choices. Easiest option is to route the train onto the down line to reverse behind BJ84. The train will accept the road and reverse correctly.

If traffic movements on the Down line preclude reversing a train there, the second option is to employ "Yard Working" rules. For this specific scenario, this would mean routing the train onto the Up line to the LOS, locking and blocking between the LOS and signals MV60/62 to prevent a conflicting move then calling the train past the LOS. I have personally tested this method and the train will reverse once in clear of BJ82.

With absolutely NO disrespect to non-Australian players, I would imagine the "Yard Working" concept might take a little getting used to. There is a passage about Yard Working in the manual.

i think there's a timetable error with 2232, it is not tabled to reverse at BJ82/84/86 so it sits across the up main blocking SN20. Sorry if this has already been reported.

Thanks all for the excellent work on the sim so far. I imagine the work would be immense and of course realise it will be a work in progress for a while yet.

Few issues I've had along with the Berrima Junction and Medway Junction stopping issues;

1) up trains requiring a crew change at Moss Vale, if routed to the down refuge they do in reality pull down to MV44 to get in clear of MV67 at the back. Currently the sim stops them at MV54 (regardless of indication) which means they foul the down main. Not sure if it's possible in the sim to have them stop at both MV54 and MV44?

2) I had equipment failures with the level crossings at Mittagong and Burradoo. The first time I played from my last save point, 1295 stopped at all the protecting signals and I authorised it to check the line and pass at stop before it called. This happened for all 3 signals concerned. After making a few stuff ups at Coota, I replayed from the same save point and with the same crossing failures, 1295 called for one signal but didn't hear from it again despite the failures still being present. The second time, 1221 behind it did call from some signals or I granted it permission once it stopped at all 3 signals despite 1295 ahead not doing so. Have attached a save. I'm only a newby so maybe 1295 just passed the signals itself (which I know it can) but I don't even remember seeing it stop at them.

3) I've got a track circuit failure between CA05 and 263.4 signals at Jindalee on the up main, MB7 and MB9 were both given shunt signals on CA08 and they continued without calling, I thought they may call at the EYL to obtain permission. I know they don't really need to so may not be a bug but maybe all ok.

Thanks again,
Danny