Continuation of TRS19 SP1+ASB (Post #268 on "TRS19 SP1 Now LIVE") Jan 16 2020
Hi Boat,
Deleted the :5 controller, did a database rebuild, added :5 again, and no difference. Deleted & rebuilt the cache folder & no difference. Also used the ASB prefix in the search. The list comes up blank very quickly, does not appear to be waiting on anything, it makes up its mind in the blink of an eye there are no signals. I see there is a new library added in SP1 called "asyncobjectsearch.gsl" which somehow sounds applicable to searching for objects, like signals. The regular object find finds these signals no problem.
Also can you think about why the pre-existing signal assignments made from an earlier TRS19 build disappeared. And what Trainz resource supplies the signal list.
The system has not changed since the ASB's were assigned and working.
I went to open a session with a couple of <kuid2:76656:70001:5> ASB Crossover Controllers (latest version) only to find in SP1, trains are blowing the diamonds passing through each other (aka colliding) as if the controllers were not there. Opening the controller properties revealed the controller forgot its assigned signals.
Not only that, ASB Controllers can no longer retrieve the signal list for the route (see graphic). Tried getting a signal list in Kickstarter County 2 and Lake Sebino, and same result: no signals. Adding a new named signal to the route or typing in an existing signal name had no effect. (p.s.My ASB signals are on the same layer as the controllers)
Hi Boat,
Deleted the :5 controller, did a database rebuild, added :5 again, and no difference. Deleted & rebuilt the cache folder & no difference. Also used the ASB prefix in the search. The list comes up blank very quickly, does not appear to be waiting on anything, it makes up its mind in the blink of an eye there are no signals. I see there is a new library added in SP1 called "asyncobjectsearch.gsl" which somehow sounds applicable to searching for objects, like signals. The regular object find finds these signals no problem.
Also can you think about why the pre-existing signal assignments made from an earlier TRS19 build disappeared. And what Trainz resource supplies the signal list.
The system has not changed since the ASB's were assigned and working.
Surprised you are getting this. It tests OK on Sabino Lake with my SP1.
Signals not showing has usually been down to a Trainz Timeout. When you assign a signal it looks at all the signals on the route. In some cases this can take too long and Trainz will shut the search down. The result is a blank return. The workaround is to use the 'Signal Search Filter'. Type in part of the name of signal you want. This reduces the amount of signals it searches and speeds it up.
You could try that and see. Maybe it depends on the speed of your system?
Oddly though SP1 seems less prone to this by my tests. It could be my new computer but even the ECML is returning all signals without the need for a filter.
Try re-installing ASB Crossover and doing a database repair?
Boat
I went to open a session with a couple of <kuid2:76656:70001:5> ASB Crossover Controllers (latest version) only to find in SP1, trains are blowing the diamonds passing through each other (aka colliding) as if the controllers were not there. Opening the controller properties revealed the controller forgot its assigned signals.
Not only that, ASB Controllers can no longer retrieve the signal list for the route (see graphic). Tried getting a signal list in Kickstarter County 2 and Lake Sebino, and same result: no signals. Adding a new named signal to the route or typing in an existing signal name had no effect. (p.s.My ASB signals are on the same layer as the controllers)
Last edited: