Norfolksouthern37 Searchlights and 2010

[GP30Fan]

I'm having an issue with norfolksoutherns' searchlight signals and 2010.

On the same route in 2006, I did not have this problem.

The issure appears in both surveyor and driver but is most distracting
in driver.

The issure is a corona, or a red laser aimed at the driver,
at the base of mast mounted signals and on the road bed under gantry
mounted signals.

It's not always there under the gantry signals but is
always there at the base of the mast on mast mounted signals.

It's visible from quite a distance. At greater distances, it appears
as a red signal and is indistinguishable from the signal indication itself.

Since it does not always appear, is Trainz trying to tell me something?
Or, is this just the way it is.

I've checked the mesh files and textures. It isn't there. The config
shows no corona's attached at these locations.

Is there an answer? Many thanks all!

Examples below...

They appear much brighter real time. The picture does not do the intensity
of the red dot justice.

A little hard to see, but look closely, and you'll see them.

 

[norfolksouthern37]

it took me a while to find the cause for this too, its apparently a bug in TS2009 and 10 (developers know about it). the config should define some coronas, you could remove those or... the only other fix i have for it is to give the signals LoD, meaning they have to be referenced in the config.txt as a.lm file, and then a .lm file must be made for the signal, then the coronas will appear in the correct place.

 

[GP30Fan]

The signals in question don't appear to have
a misplaced corona, they appear to have an
extra corona.

The signals function fine. Well as fine as AI will
allow.

Its the "Extra" corona that's bothersome.

Is it referenced in the config?

I'm not that familiar with LoD files. In face I usually
redo the config back to IM file reference. Guess
I'll have to get up to speed on the LoD method in
this case just to eliminate that pesky corona.

Note to norfolksouthern37. Sent you an email, couple
weeks ago, reminder on the Emit Train Now upload.
Any progress?

Thanks for the reply and the explaination.

 

[norfolksouthern37]

well its def a misplaced corona. there should be a lit mesh part and a corona to allow for distant viewing, but all you see in the correct location if the mesh lens, the coronas are always at the origin of the signal. since they are for distant viewing, this is also why you cant see them when close to the signal, because i have them set to appear at a certain distance. i had to do this because its impossible to see the mesh lenses from far away.

 

[GP30Fan]

I agree with the distant viewing problem. I have that
on a regular basis. The mu setting in the config helps
but doesn't solve the problem completely.

I would guess a brighter corona would help, but
thats certainly not in the cards.

As long as I know it's been reported as a bug,
I'll live with it till a solution rears it's head,
maybe TRS2011.... lol

Thanks

 

[norfolksouthern37]

lol, no you misunderstand. you dont get the effect of the coronas because they are in the ground, this is the bug, and is whats shown in your screenshot. there is no other corona but those and they are in the wrong place. they work great when they are in the right place on the models.

 

[sniper297]

I get odd effects in 2010 with default signals and other coronas, like tail lights showing thru the body of a car at certain angles.

Also does that type of thing with default searchlights, three color, and dwarf signals on freight car bodies that don't have alphas.

 

[GP30Fan]

Ah ok... well now the question becomes...

How the heck to you fix it. If this is inherit in 2010,
is there a work around to the problem.

Sometimes yea, sometimes nay.

I know I have re-looked at the mesh in PEVs'
mesh viewer and all looks OK. Trainz doesn't
quite see it that way from what I'm looking at.

Is there some way to show what it's supposed to
look like as opposed to what it does look like?

 

[norfolksouthern37]

the corona goes where the light is. the only way i know to fix it is to make the signal into a lod type.