[VAPOR3D]

Hi! I know this is an old thread, but I don't believe anyone else has had any problems with signals and TSRE5 since 2017, so I guess this is the right thread.

I'll try to explain myself. I was trying to incorporate the location of a sound in an Activity to sound when a train passes by. For many tests I have done, going through all the documentation and threads on the subject, but it has been impossible. Then I remembered that TSRE v 8.004 incorporates an Event Editor so I tried to do it with it. That seems to incorporate a location at the specific track location, with the name "New Event". Well, I tried it this way and it didn't work either, but the worst thing is that it erased all the signaling of the Route when saving.

Well, I don't know what the problem is with some needle indicator elements that have been erased at some points and not at others. If it is necessary to put it all back again, then it is put back.

The specific problem is that now it does not show me the elements that are part of the signaling in "Signals" in TSRE5. The sigcfg and sigscr files are exactly the same, and their definitions are supposed to be there. The .s and .sd files, as well as their textures, too, and they are still where they should be. I don't understand what the heck is going on, if anyone can offer me any hints, I would be very grateful.....

[VAPOR3D]

Good. I think I have already solved it by removing these lines from the sigcfg.dat file that should not be compatible with TSRE5, by removing them the traffic lights and turnout indicators have returned:

               SigFlashDuration ( 0.5 0.5 )
                ORTSOnOffTime ( 1.0 ) // in seconds

I leave it here in writing, in case someone encounters the same problem. I don't know if there is a warning about this in the Manual, but it would be interesting if it were there, so as not to waste too much time for the Route builders.

Now I am going to see if they can be put after having put everything back in place. Fortunately the Route I am making is not very long, otherwise....

[hehl]

I assume that such a comment is not permitted in the sigcfg.dat file.

 
         .....      // in seconds

A comment must be included in
Skip ( <comment> )

I don't know if such a comment is allowed within a SignalType ( ... ) definition.

The interpreters of the sigcfg.dat and sigscr.dat files are different. The comment you use can be placed anywhere in the sigscr.dat file.