Moss Vale Issues/Bugs

Thanks for keeping all the issues together and please keep them here in the one place, so much easier to keep track rather than searching for individual threads.

The TT is being worked on, and most of the issues mentioned are known, but may need a few more days before an update is released.

a few more that havent been mentioned:

trains from moss vale - picton call wrong route at MV60 complaining that they are not booked via berrima jct.

trains between Mittagong and barago call wrong route at all signals on the up complaining wrong route - not booked via mittagong.

trains looped onto the down loop at moss vale call wrong route at MV37 when routed onto the refuge. they do still accept the refuge as a platform at moss vale so presumably it should be an acceptable route (ive been looping early freights)

a general trend ive noticed (especially on the down between tahmoor and Moss Vale) is freights gaining loads of time. I'm up to 4am and I havent had a single freight not require looping at moss vale due to being really early. all have entered on time. it may be prototypical that the WTT has a lot of leeway but i recall a similar issue with train performance in carlisle so thought it was worth mentioning.

not really a bug but i cant find any reference in the manual as to what the little blue sub aspects are on some of the signals on the sim.

again more of a question than a bug. i had the overnight up XPT being closely followed by a late running freight. i chose to run the freight behind it from cootamundra instead of allowing it to pass however it kept time with the XPT. is there much of a difference in passenger and freight speeds?

final request - given how long some of those freights are, could the manual include the loop lengths for all the various loops, refuges and yard through lines to aid with regulating?

so far really loving these sims. a big jump from the UK. NSW signalling feels like UK MAS signalling had a kid with american practice.

1:26AM, Train ST22 complaining about wrong route set at CA74.... but ti's a simple mainline move with the route def. set right!

a new one. a phone call from train (none) advising me it is approaching SL22 signal but no train has entered the area to trigger a call, hence(none) not being populated with the ID.

save attached

With a route set from G58 to G78, G58 seems to step back to double-red if a train passes 220.6. I have a save from immediately after 3MB9 receiving an ACoA at G58.

I have a train standing at HN22 and occupying tracks as far back as THN28BT. Signal HN24 had not released its route, so I tried to cancel it by right-clicking. As expected I got the "120 seconds approach locking" message. However, 120 seconds later, the route did not release; the "120 seconds approach locking" message repeated, and keeps repeating every two minutes.

Edit: oops, spotted the same bug has been reported for a different signal on another thread.

Just had a Down train pass signal 178.7 and "disappear" - the train has gone off track T165_6AT and it has returned to white, but track T176_3ATS has remained at green and the signal has stayed clear. The description has not stepped. After a pause of about 20 seconds or so, T173_3ATS shows occupied and 178.7 goes to Danger.