Recent content by justinroth

This is how I used to use them. I have a document that I made to tell me the trigger distance based upon track speed. Since then I haven't messed with TRC and now automatic is an option. Are you saying the automatic detection doesn't work properly?

From what I understand and it's been a bit since I've messed with EIT's is that more "towers" with less paths is the way to go. Also I think they're supposed to go in the session layer. It's been a while though.

I have just begun using TRC after years and just use one set to automatic. Is there a reason not to do it this way?

I personally would use enhanced interlocking towers and then mission codes. The switch/route will be set depending on the mission code assigned to the driver.

I believe in this case the issue was a two signals in succession set to limited. The 1st signal probably didn't "know" what to display. Limited approach limited is probably never a thing.

New versions still don't work. Replacing seems to be the solution.

Yes they save. The only issue I have encountered thus far is sometimes the limited aspect flashes fast and erratically but this could've been from improper set up of progressing aspects.

So I need to create new versions AND bulk replace/bulk replace?

Yeah it's time consuming for sure. I attempted to fix the current "fixed" script I'm using to work for both NW cpls and modern signals in NW territory but gave up. Perhaps the "ruleset" function is not necessary and a different script for each signal pack/rule set would be simpler....I dunno. A...

Perhaps I should do what I contemplated and convert them to use something stable...like the JR script. I would miss being able to set slow and restricting states though I guess the JR script allows an unbonded option. Oof. What a chore.

I am at best an F- scripter. I didn't write nor update "fix" it to work post tane sp2. Are you saying the original script still has something in the soup? Is my only solution to delete and replace each signal individually? Would backing them up, deleting and re-installing them help?

I've tried deleting all signals using the older script and a database rebuild but the problem still persists. The script properties on the right are for the old signal and they still contain original script settings (under "route" which appears for advanced settings). The old script wouldn't...

They are showing the new script, kind of. There are options missing and the default display of info is more like the old script. The new script is an updated version of the old script by a different author with a different kuid.

I've recently transferred a route from tane to 2022. The route had signals from pre tane sp3 and the script was broken. I updated the signals to a newer version of this (tested on a blank route) script however, the script properties don't show up correct. I can place a completely identical...

It won't unload, more specifically anthracite raw coal set to unload in motion. Out of curiosity I tried using the old MIN short, unload command but this results in it getting stuck on a Loco for some reason. Somethings fishy.