Blue signals instead of green

[JPS2K5]

This has been bugging me for a while now. Ever since I switched from TRS19 to TRS22, on some routes I have blue ground signals instead of green. The luminance or whatever one calls it also seems very off, it's like a ball. I have this on crossing lights too.

How do I correct this?

Example here:

 

[JCitron]

On Some is the key. It's the signals the author used. If you have a signal you like, you can clone the route and replace the signals with blue lights with the ones with green lights using the Bulk Update utility.

 

[PWeiser]

The only solution I've found to the "ball" effect on light signals (large colored disk displayed at a distance) is to modify the signal so it has a distant LOD which specifies a much smaller radius for the corona. There may be other/recommended ways to address this, but my ability to analyze progeny assets is limited.

 

[JPS2K5]

But, I mean... we're talking Pro Train here for example. Surely if the signal is the problem, they must have seen it too? Surely they would not leave something like that for everyone to see?

I was kinda hoping for a setting to change, not editing routes

 

[bekaember]

It seems like the corona itself faces with the camera, and this beautiful "visual feature" exists since Trainz 1.0... Hopefully will be corrected in the next 20 yrs...
I confirm as well - link to pic - I cannot paste it here as an image (yes, the helpers are correctly placed): LevelCrossing_bug.png

 

[PWeiser]

It seems like the corona itself faces with the camera, and this beautiful "visual feature" exists since Trainz 1.0... Hopefully will be corrected in the next 20 yrs...
I confirm as well - link to pic - I cannot paste it here as an image (yes, the helpers are correctly placed): LevelCrossing_bug.png

"Directional" tag for coronas has been on-again-off-again through Trainz versions, sometimes between different builds of the same version. When it works, signal coronas appear only from the creator-designed direction; when it doesn't (i.e. the particular build ignores it) you can only hope the target board occludes it from the reverse direction. That *sometimes* happens. It's a little variable, too.