Double head signal aspects?

sniper297

Coconut God
Thought I understood a little about prototype signals, but noticed something odd recently. I'm still using default USA or USA2 signals, on a facing point switch I usually stick a double head USA2 02 (or L if it's a left diverge). Through route set, clear all the way to Ecuador, got green over red. Throw switch curved, diverge route is clear all the way to Morocco (aside from the occasional fishing boat off the Azores), got red over green. Problem comes in when a route is not clear all the way - I would expect yellow over red for straight, red over yellow for diverge, but instead I'm getting yellow over green for either route. Makes it impossible to tell which way the switch is thrown, anyone know what prototype practice on double heads at facing point switches is for something like BNSF?
 
that is a very open question and it could take a while to explain the answer. just sounds like the signals are configured shall we say differently... you wont get much out of the default signals they are very basic.
 
Yeah I know, I'm still waiting to see a complete set of color light signals (regular, gantries and dwarfs) on the DLS compatible with TS12 multiplayer, until then I'm stuck with defaults. Reason I asked is because I couldn't find my old BNSF rulebook (gotta clean out that closet one of these days) and couldn't remember for sure. While hunting for BNSF I found Union Pacific, which uses similar signals;

66414111.jpg


According to that I SHOULD be seeing yellow over red or red over yellow, the yellow over green is for some other type of signal or a distant signal or something. Thought I remembered seeing yellow over green in the BNSF rulebook, if I could lay my hands on the little culprit I could check that.
 
According to Californian Regional timetable by Altamont Press, Indication 9.1.2 Yellow over Green is Approach Limited if green is flashing, "Proceed prepared to pass next signal not exceeding 60mph with or without number plate." If all aspects are steady Yellow over Green Advanced Approach, Indication 9.1.3 "Proceed prepared to pass next signal not exceeding 50mph or prescribed speed with or without number plate." Or Indication 9.1.11 Reproach Restricting, "Proceed prepared to pass next signal at restricted speed, with or without number plate." Also Rule 9.1.11 aspect can be yellow over green over red.

John
 
I haven't been able to find a complete set, but it has been a while since I looked. I did spend a week or so last year hunting when TS12 first came out, here's a single head gantry and a left diverge double head gantry but no right diverge in the set. Here's a linkable signal, but it's for 2004 and won't work except in 2010 compatibility mode, here's another one that will work without errors in 12 but the yellow corona has to be downloaded from a 3rd party website which would make the route unusable for multiplayer. And so on, you get the idea. Same thing with fixed switches, even if everything is on the DLS it's a 16 megabyte download for each switch and using 10 of them tanks the framerates.

On another topic, since you make signals, ever given any thought to LOD coronas? I was looking into the idea of using something like a reverse LOD - far away low LOD is the same mesh but with huge coronas, medium same mesh but with smaller coronas, close up same mesh with normal size coronas. That way the signals would be visible from a much farther distance without getting a huge corona up close. Tried it but near as I can tell the corona size is defined outside the mesh table and no way to get 3 different effects into 3 different LODs.
 
there is no need to LoD a corona they automatically get larger at a distance. my current signals can be seen well beyond the trainz draw distance, so i dont plan on making any changes there. i worked out that scheme a few years ago.

i have one set of NS color lights on the DLS and there is absolutely no shortage of searchlights made by me. heck i put 144 of them in TS12. my set with the snow hoods will go up 'soon' - i recently converted them to mesh library use.
 
Okay, I'll take a squint. Haven't looked at what's in 12 since I was trying to make routes compatible with 2009, 2010 and 12, altho I might give up on 2009 to focus on just 2010 and 12.
 
Back
Top