FRED (EOT device)

I have download the FRED (EOT device) but don't know how to get it working and be able to see it on wagons, it's a mesh file and I don't know how to use them, help please?
 
Could you supply a kuid number? There are several assets on the DLS that have the name FRED (flashing rear end device) and are EOTs (end of train devices), some of them are of type mesh and others are are of type rolling stock - I have no idea what the distinction is. Have you tried one of the rolling stock versions by bnsf50? I have used a rolling stock FRED in the past (pre TS12) and it worked like a normal rolling stock item - you added it to a consist like you would add a wagon.
 
Last edited:
Could you supply a kuid number? There are several assets on the DLS that have the name FRED (flashing rear end device) and are EOTs (end of train devices), some of them are of type mesh and others are are of type rolling stock. Have you tried one of the rolling stock versions by bnsf50? I have used a rolling stock FRED in the past (pre TS12) and it worked like a normal rolling stock item - you added it to a consist like you would add a wagon.

Yes I was just using the rolling stock one, I don't mind it but if my train changes direction then it's stuck on the other end and it floats in mid air, there is one on jointedrail.com but I don't know how to get it working.
 
The FREDs' or EOTs' are available as both rolling stock and mesh files
depending on the authors preference.

All of them will work in one fashion or another.

The mesh type freds require an attachment point on the traincar to work.
And that's the problem. Most train vehicles do not have the proper
attachment points.

Then another problem arises. If the mesh is not script controlled, the
FRED will always be visible, even if the traincar is mid train, which will
place the FRED between two traincars.

I have hundreds of traincars with automatic FREDs' attached, all
script controlled, with no problems.

If you want to get into it deeper, I can help. All the tools to accomplish
the task are available. All you need is time to get it done.

-AL
 
How do I do this and what do I need to do?

Copy the config file from a JR rail car that has this feature:

mesh-table
{
default
{
mesh "mesh_body/arn.im"
auto-create 1
}

body
{
mesh "mesh_body/Skeleton_Log_Car_DES.im"
auto-create 1
}

shadow
{
mesh "mesh_shadow/Shadow.im"
}

eot_f
{
mesh-asset <kuid2:45324:25503:1>
mesh "atx_att0/eot_f.im"
auto-create 0
att "a.limfront"
att-parent "body"

effects
{
blink
{
kind "corona"
att "a.light"
texture-kuid <kuid2:45324:10101:1>
object-size 0.15
frequency 1.1
wave-shift 0.5
max-distance 2000
mul-distance 150
max-size-mul 10
}
}
}

eot_r
{
mesh-asset <kuid2:45324:25503:1>
mesh "atx_att0/eot_r.im"
auto-create 0
att "a.limback"
att-parent "body"

effects
{
blink
{
kind "corona"
att "a.light"
texture-kuid <kuid2:45324:10101:1>
object-size 0.15
frequency 1.1
wave-shift 0.5
max-distance 2000
mul-distance 150
max-size-mul 10
}
}
}
}

Add these kuids in to the kuid table:
eot_lib <kuid2:45324:25503:1>
red <kuid2:45324:10101:1>


If after committing and the EOT is either too low or high on the coupler, then you need to change the mesh which is found in the eot_lib <kuid2:45324:25503:1>. These are the blue entries in the example above.

John
 
I'm sorry I've had multiple attempts at this and can't get it to work, are you able to do it for me and email the working one to me if that's alright?

Copy the config file from a JR rail car that has this feature:

mesh-table
{
default
{
mesh "mesh_body/arn.im"
auto-create 1
}

body
{
mesh "mesh_body/Skeleton_Log_Car_DES.im"
auto-create 1
}

shadow
{
mesh "mesh_shadow/Shadow.im"
}

eot_f
{
mesh-asset <kuid2:45324:25503:1>
mesh "atx_att0/eot_f.im"
auto-create 0
att "a.limfront"
att-parent "body"

effects
{
blink
{
kind "corona"
att "a.light"
texture-kuid <kuid2:45324:10101:1>
object-size 0.15
frequency 1.1
wave-shift 0.5
max-distance 2000
mul-distance 150
max-size-mul 10
}
}
}

eot_r
{
mesh-asset <kuid2:45324:25503:1>
mesh "atx_att0/eot_r.im"
auto-create 0
att "a.limback"
att-parent "body"

effects
{
blink
{
kind "corona"
att "a.light"
texture-kuid <kuid2:45324:10101:1>
object-size 0.15
frequency 1.1
wave-shift 0.5
max-distance 2000
mul-distance 150
max-size-mul 10
}
}
}
}

Add these kuids in to the kuid table:
eot_lib <kuid2:45324:25503:1>
red <kuid2:45324:10101:1>


If after committing and the EOT is either too low or high on the coupler, then you need to change the mesh which is found in the eot_lib <kuid2:45324:25503:1>. These are the blue entries in the example above.

John
 
I hear that the JR one only attaches to certain JR railcars

The ones on the DLS work fine on any car

They will work on any railcar, the user needs to alter the config file, and experiment with the height.

John

They can work on any car using the JR Train Effects Library - which could be any car but may not be the car he is trying to place the EOT on. There are differences in the DLS ones that are essentially just traincars to what I chose to do with TFX EOT. I wanted something that could be added or removed via a dialog box or even driver command rather than be yet another car on the train for various reasons ranging from scripts that I use that report on trains (Train List) to not being able to remove the fake traincar one at will - like what to do with it when I need the EOT gone.
 
Back
Top