Safetran signal reflection missing.

nicky9499

SSoTW Bot
Currently its like this:

e094d0073a624171b047a29642877d77


Which if I don't remember wrongly, should be like this:

Screen_064.jpg



?
 
It's the angle of view. These are hooded signals, which restricts the angle of view.
Also, I find that if the signal is pushed too far into the gantry, such that the rails of the gantry are in front of (actually going through) the signal, the aspect will look somewhat off.

FW
 
Last edited:
Okay, just to show that it's not the angle:

Screen_004-1.jpg



Strangely though, this only occurs in dense regions. In the high speed sections the reflections show up just fine...strange.

Screen_005-1.jpg


Screen_006-1.jpg



Any ideas why?

Cheerio,
Nicholas.
 
Nick,

This could be a function of your video card. With lots of things going on, this could be one of the many details that are being dropped because of the higher CPU and GPU level neeeded to display the reflections as well as keep trains moving, water reflecting, etc.

Given the high amount of different things that need to be calculated, drawn and executed by the software and your computer system, we're pretty lucky that this works at any decent speed at all. If the reflections, and probably some other details weren't dropped, the performance could become choppy like it was in TRS2004 and TRS2006.

John
 
Never thought of that before, it could possibly be so. At any rate, it's nothing showstopping, so I guess I'll close one eye and let it pass. ;)

Cheerio,
Nicholas.
 
I have the same signals, and set up pretty much the same conditions.
There are angles where you do not see the full aspect, but this is because the viewing angle is not straight.
Either you are above / below the signal, or to one side or another.
Because these signals have hoods, this is to be expected.

If you don't like the way they look, try using the ones without hoods, but remember that railroad signals are not designed to be viewed at much of an angle, so as to prevent drivers from becoming confused as to which signal is his.

af-01.jpg

Looking straight on.


sf-2.jpg

Note the upper left signal is partially obscured.
I am looking at it from an angle from the right.

sf-3.jpg

Viewing from above.


sf-5.jpg

Looking from the left.

As far as I can tell, this is exactly the way these signals would look in prototype.

FW
 
no it probably because you are in surveyor and are manually changing the time. the signals do not check what time it is all the time in order to save cpu. once the state of the signal changes it will be correct. if you were playing a route and it got dark, everything would be okay, if you started a session in the dark, it would also be ok, but changing the time in surveyor happens faster than the signal is checking the time of day.
 
You're right Justin, never thought of that before. Went back to the signal in the first pic, switched to 0000 hours, replaced it. Presto! There are the reflections. For that matter, I've never tested my route in Driver (save for taking screenshots and even so, never at night) before simply because it's not finished. Of course, I will when creating sessions.

Thanks for the help. :)

Cheerio,
Nicholas.
 
i've never had the 'reflections' in either 04 or 06...

Well, it seems 'Liar Liar, pants on fire....'

Following Justin's explanation above I loaded up a night-time session in TRS06 and...

corona.jpg


... a train is approaching the signal on the far track, so the aspects on that signal have reloaded and sure enough, there be reflections me hearties. The closer signal has no reflection, but the session has just started, so the script has presumably not yet consulted the clock.

Seriously though, I have never noticed this effect before, but it is a very neat touch that enhances an already wonderful asset. Thanks Justin!

Andy ;)
 
Last edited:
Back
Top