Log File Questions...

[fchrist16]

COLLECTIVE HIVE MIND: This is going to be a simple thread but also a weird one. IN my log file with a route I'm working on, I get warning lines like what is below...WOULD it be horrible/break anything if I went into the sigcfg and other data files and cleaned up these items? I'd like to see a lot less errors/warnings in troubleshooting things...

Warning: 3 missing SignalType(s) in C:\Train Simulator\ROUTES\WP3\sigcfg.dat:line 7498

Warning: Skipped duplicate SignalShape JJHSIG6NSGANTRY3L.S in C:\Train Simulator\ROUTES\WP3\sigcfg.dat:line 45086

Gurus advice ONLY!!

Regards,

-Frank C.

[R. Steele]

Hope you get a knowledgeable answer Frank, I'd like to eliminate these warnings also.

[ebnertra000]

The first one is most likely a miscount of signal types. Try reducing it by 3 to see what happens.

The second one is exactly what it sounds like. Find that duplicate shape and remove it, and then adjust the signal shapes count.

Obviously, make a backup first, but those are pretty straightforward errors, so it should be relatively simple to fix.

45086?!

[rdayt]

Does the new Error tool in TSRE give any insight?
Might help with locating the duplicate shape.

Not a guru, just a tinkerer.

Randy

[ebnertra000]

If there were a duplicate shape in the route, TSRE might find it. The duplicate referenced in the log here, though, is a shapename used twice in the sigcfg, which is not allowed

[fchrist16]

Randy: There is a new error tool in TSRE? Where is that located?

Travis: I know of a few signals that the shapename is reused in the sigcfg...Is that bad? Yes I have a lot of cleanup in the SIGCFG to do...45086 lines is I think halfway through the file!

Regards,

-Frank C.

[ebnertra000]

Travis: I know of a few signals that the shapename is reused in the sigcfg...Is that bad?...

Yes. Shape names can only be used once, as that's how different signals are differentiated in OR. i.e. If the same shape name was used for both an absolute and an automatic, the system won't know what set of signal features to use

[rdayt]

Frank,

The Error and Messages tool is in the tools drop down.
It gives you the option to jump to the locations of errors that can be repaired with TSRE.
It's available in the new version 0.698.
It's turned out to be quite handy.

Randy

[fchrist16]

Frank,

The Error and Messages tool is in the tools drop down.
It gives you the option to jump to the locations of errors that can be repaired with TSRE.
It's available in the new version 0.698.
It's turned out to be quite handy.

Randy

Randy, That's why I didn't see it...I'm one version behind, still on .697!

Regards,

-Frank C.

[fchrist16]

Yes. Shape names can only be used once, as that's how different signals are differentiated in OR. i.e. If the same shape name was used for both an absolute and an automatic, the system won't know what set of signal features to use

Travis, check your PM's.

Regards,

-Frank C.

[R. Steele]

Yes. Shape names can only be used once, as that's how different signals are differentiated in OR. i.e. If the same shape name was used for both an absolute and an automatic, the system won't know what set of signal features to use

Question from zero knowledge about signalling and route building...if the shape name was used for "both an absolute and an automatic" --- how does one know which to eliminate? Wouldn't one signal be left without a shapename?

[ebnertra000]

If a shape name is used twice in the sigcfg, there are basically two options:

Remove one shape entry - all of it, not just the shape name line - from the sigcfg and adjust the total shapes count (do not delete the shape file itself), or...

Change one shape's name to something else, and make a copy of the original shape using the new name.

In no case should any signal using the offending shape name be in use in the route when this change is made. Any already placed must be deleted prior to making the change, under penalty of database corruption

[R. Steele]

If a shape name is used twice in the sigcfg, there are basically two options:

Remove one shape entry - all of it, not just the shape name line - from the sigcfg and adjust the total shapes count (do not delete the shape file itself), or...

Change one shape's name to something else, and make a copy of the original shape using the new name.

In no case should any signal using the offending shape name be in use in the route when this change is made. Any already placed must be deleted prior to making the change, under penalty of database corruption

I get it, should have realized...same protocol as with models...changing names of shapes, ace files and such are okay as long as all other logical instances are also changed. ( does that explanation make sense? ) I make default copies of all dat and other significant files before any changes are made. I have multiple backup copies of routes in case something goes awry.
Thanks for taking the time to provide some education.