anathoth71
Member
Greetings Trainzers, forgive me for spamming this forum like this, but yet another problem has come up that I would like to enquire of the community about, before I take a hatchet to it and break something really badly.
I recently brought my main route and it's associated basic setup session to TANE from TS2010. I am currently resurrecting it for use in TANE, and I have discovered that at least half of the Trackmarks on the route are failing to appear in the trackmark selection list when invoking the Navigate To, Navigate Via, Drive To or Drive Via driver commands. All trackmarks that start with the letters H - S are showing as normal. 0-G, and T-Z are not showing at all.
The funny thing is, the missing trackmarks are appearing in the CTRL-F find function, and are visible as normal in Surveyor, so it seems that the route itself knows they are there. Their text strings are also present in the route config.txt file. They are all in the route layer and always have been. Also, if I place a new trackmark with a name starting with H - S, it is immediately detected as normal. But a new trackmark name starting with 0-G and T-Z remains invisible to the driver commands.
Any insight offered as to why this potentially route-killing behaviour is occurring would be greatly appreciated indeed !
Why do the driver commands not recognise their presence in the route? Am I missing something obvious here?
I recently brought my main route and it's associated basic setup session to TANE from TS2010. I am currently resurrecting it for use in TANE, and I have discovered that at least half of the Trackmarks on the route are failing to appear in the trackmark selection list when invoking the Navigate To, Navigate Via, Drive To or Drive Via driver commands. All trackmarks that start with the letters H - S are showing as normal. 0-G, and T-Z are not showing at all.
The funny thing is, the missing trackmarks are appearing in the CTRL-F find function, and are visible as normal in Surveyor, so it seems that the route itself knows they are there. Their text strings are also present in the route config.txt file. They are all in the route layer and always have been. Also, if I place a new trackmark with a name starting with H - S, it is immediately detected as normal. But a new trackmark name starting with 0-G and T-Z remains invisible to the driver commands.
Any insight offered as to why this potentially route-killing behaviour is occurring would be greatly appreciated indeed !
Why do the driver commands not recognise their presence in the route? Am I missing something obvious here?