When it comes to railroad signals in TRS22 strange things can sometimes happen. As an example, here is a screenshot showing a right diverging siding being protected by my <kuid:439337:119134> SAP_Signal_3_RH_RD_PBR railroad signal.
As you can see the lights do not display correctly. The reason for this is that the next junction where the siding reconnects to the mainline is not protected by railroad signals, so Trainz gets confused and does not display the lights correctly. How do you correct that?
If you add railroad signals such as my <kuid:439337:119134> SAP_Signal_3_RH_RD_PBR dwarf signal to protect both tracks, then Trainz will than display the signals correctly. The below screenshot shows what happens when I did this:
and
BTW if you don’t want those signals at the next junction to not be seen for some reason, than just add invisible signals such as my <kuid:439337:118758> SAP_Invisible_Signal_Dwarf_1_PBR. In either case this will fix this issue and make the railroad signal display lights correctly.
Another issue is when you have a siding or spur that does not reconnect back to the mainline. The following screenshot shows that Trainz is once again confused by this and does not display the lights correctly.
A simple way to fix this is to add an invisible signal, such as my <kuid:439337:118758> SAP_Invisible_Signal_Dwarf_1_PBR to the end of that track. When you do that, the issue will be resolved as shown below in the screenshot which now displays the lights correctly.
These are the solutions I have adopted for my line of railroad signals that fixes these Trainz railroad signaling quirks, and they work well if you do as I indicated above. BTW other authors have taken a somewhat different approach and used a Trainz script to deal with these issues with their railroad signals.
Bob

As you can see the lights do not display correctly. The reason for this is that the next junction where the siding reconnects to the mainline is not protected by railroad signals, so Trainz gets confused and does not display the lights correctly. How do you correct that?
If you add railroad signals such as my <kuid:439337:119134> SAP_Signal_3_RH_RD_PBR dwarf signal to protect both tracks, then Trainz will than display the signals correctly. The below screenshot shows what happens when I did this:

and

BTW if you don’t want those signals at the next junction to not be seen for some reason, than just add invisible signals such as my <kuid:439337:118758> SAP_Invisible_Signal_Dwarf_1_PBR. In either case this will fix this issue and make the railroad signal display lights correctly.
Another issue is when you have a siding or spur that does not reconnect back to the mainline. The following screenshot shows that Trainz is once again confused by this and does not display the lights correctly.

A simple way to fix this is to add an invisible signal, such as my <kuid:439337:118758> SAP_Invisible_Signal_Dwarf_1_PBR to the end of that track. When you do that, the issue will be resolved as shown below in the screenshot which now displays the lights correctly.

These are the solutions I have adopted for my line of railroad signals that fixes these Trainz railroad signaling quirks, and they work well if you do as I indicated above. BTW other authors have taken a somewhat different approach and used a Trainz script to deal with these issues with their railroad signals.
Bob