VADER signals - still a problem

[neilsmith749]

I thought the problem of the signals not holding their settings upon re-opening a session was solved, but I'm still having the same issues, as well as the fact that, now, when opening the properties window of a signal, only the parameter titles show up, and nothing beneath.

Has anyone else noticed this? Or does anyone know if this issue has been addressed? Or, will be addressed in a future SP?

And....does anyone who knows scripting (or whatever it's called) know whether it's possible to have the signal settings saved to the route as opposed to the session? That way, once they're set, they will always be good to go. I've found that industry settings seem to be able to be saved to the route, so I'm hoping it's possible for the signal settings to be as well.

Really hope this can get sorted out - working on TS19 version of UMR, and need to get signals working properly.

 

[JCitron]

Neil,

Have you updated to the latest JR signal library? You can download that from their website. I think that should take care of the problem you are having.

 

[neilsmith749]

Neil,

Have you updated to the latest JR signal library? You can download that from their website. I think that should take care of the problem you are having.

Ahhh - I could see how that would help. I don't suppose you know whether they'd be put on the dls at all, huh? I've done my best to not use 3rd party content, to make downloading the route as simple as possible. But this may have to be an exception.
Thanks for the reply John - I'll definitely investigate.

 

[Jayco-man]

If I'm not mistaken it is on the DLS.

 

[danddhud]

Is that library meant for those signals?
Dean

 

[neilsmith749]

Downloaded the newest library from JR, and the problem persists. When looking at the properties box, and setting it to advanced-interlocking, only the titles come up now, with no lines beneath to enter next signals, or aspects etc.

edit - just noticed something else that's a little strange. If I select a signal that's placed in the route, I can pull up the properties box, and everything looks normal. But if I place that exact same signal, then the properties box of the newly placed signal has the error stated above.

 

[Hemler]

Neil,
The JMR signals seem to be working for me now with Beta 98149.

 

[neilsmith749]

Ok - I'll see if I can update to that one. Thanks Hemler!

 

[neilsmith749]

Nope - still not working. Not sure if the problem is on my end somewhere. The problem seems to be only when I add new signals, and then try to configure them. I've tried deleting them all, and using the earlier versions, which didn't seem to work either. I did extended database repairs, upgraded to the latest Beta, and still nada. ughhh