MSTS Static Engine lights - flashing vegetation - and a DPU utility question

[qballbandit]

Tom,
Any engine I have created with Route Riter to be a static engine (ex: $TPW_GP38_2_3830.wag), the lights don't display in OR, but work fine in MSTS.

Here is the entire .wag file from the above example Toledo, Peoria, & Western engine:

SIMISA@@@@@@@@@@JINX0D0t______

Wagon ( $TPW_GP38_2_3830
Type ( Carriage )
WagonShape ( TPW_GP38_2_3830.s )
Size ( 3.22m 4.8m 17.9m )
comment( 255500lbs US )
Mass ( 115.9t )
WheelRadius ( 20in )
InertiaTensor ( Box (3.22m 4.8m 17.9m ) )

Lights ( 4
Light (
comment( Head light top dim )
Type ( 0 )
Conditions (
Headlight ( 0 )
Unit ( 2 )
)
FadeIn ( 0.5 )
FadeOut ( 0.5 )
Cycle ( 0 )
States ( 1
State (
Duration ( 0.0 )
LightColour ( ffffef8f )
Position ( 0.0 4.365 6.43 )
Transition ( 0 )
Radius ( 0.5 )
)
)
)
Light (
comment( Head light bottom dim )
Type ( 0 )
Conditions (
Headlight ( 0 )
Unit ( 2 )
)
FadeIn ( 0.5 )
FadeOut ( 0.5 )
Cycle ( 0 )
States ( 1
State (
Duration ( 0.0 )
LightColour ( ffffef8f )
Position ( 0.0 4.13 6.41 )
Transition ( 0 )
Radius ( 0.5 )
)
)
)
Light (
comment( Rear light Left dim )
Type ( 0 )
Conditions (
Headlight ( 0 )
Unit ( 3 )
)
FadeIn ( 0.5 )
FadeOut ( 0.5 )
Cycle ( 0 )
States ( 1
State (
Duration ( 0.0 )
LightColour ( ffffef8f )
Position ( 0.12 3.98 -8.18 )
Azimuth ( -180 -180 -180 )
Transition ( 0 )
Radius ( 0.5 )
)
)
)
Light (
comment( Rear light Right dim )
Type ( 0 )
Conditions (
Headlight ( 0 )
Unit ( 3 )
)
FadeIn ( 0.5 )
FadeOut ( 0.5 )
Cycle ( 0 )
States ( 1
State (
Duration ( 0.0 )
LightColour ( ffffef8f )
Position ( -0.12 3.98 -8.18 )
Azimuth ( -180 -180 -180 )
Transition ( 0 )
Radius ( 0.5 )
)
)
)
)

comment ( MSTS Bin Rigid Large Road Engine Coupler values contributed by Otto Wipfel, Joe Morris and Bill Prieger )
Coupling (
Type ( Automatic )
Spring (
Stiffness ( 4e2N/m 6e6N/m )
Damping ( 5e6N/m/s 5e6N/m/s )
Break ( 5.1e7N 5.1e7N )
r0 ( 12cm 15cm )
)
CouplingHasRigidConnection ( 1 )
Velocity ( 0.2m/s )
)
Coupling (
Type ( Automatic )
Spring (
Stiffness ( 4e2N/m 6e6N/m )
Damping ( 5e6N/m/s 5e6N/m/s )
Break ( 5.1e7N 5.1e7N )
r0 ( 12cm 15cm )
)
Comment ( CouplingHasRigidConnection ( 1 ) )
Velocity ( -0.2m/s )
)
Buffers (
Spring (
Stiffness ( 1e6N/m 5e6N/m )
Damping ( 1e6N/m/s 1e6N/m/s )
r0 ( 0m 1e9 )
)
Centre ( 0.5 )
Radius ( 1 )
Angle ( 0.5deg )
)
Adheasion ( 0.29 0.53 2.0 0 )
DerailRailHeight ( 5cm )
DerailRailForce ( 2.5*115.9t )
DerailBufferForce ( 287kN )
NumWheels ( 8 )

Friction (
1254.7N/m/s -0.10 1.3mph 14.244N/m/s 1.823
5.1N/rad/s 1 -1rad/s 0 1
)
BrakeEquipmentType ( "Triple_valve, Auxilary_reservoir, Emergency_brake_reservoir" )

BrakeSystemType ( "Air_single_pipe" )
MaxBrakeForce ( 65.4kN )

EmergencyBrakeResMaxPressure( 90 )
TripleValveRatio( 2.5 )
EmergencyResVolumeMultiplier ( 1.461 )
MaxReleaseRate( 0.49 )
MaxApplicationRate( 0.93 )
MaxAuxilaryChargingRate( 0.28 )
EmergencyResCapacity( 2.064 )
EmergencyResChargingRate( 0.24 )
BrakeCylinderPressureForMaxBrakeBrakeForce( 64 )

IntakePoint ( -3.33 0.4 FuelDiesel )
IntakePoint ( 3.33 0.4 FuelDiesel )

Sound ( "..//..//common.snd//GNR_EMD645//CPK3L645_ext.sms" )
)

[crstagg]

Tom,
Any engine I have created with Route Riter to be a static engine (ex: $TPW_GP38_2_3830.wag), the lights don't display in OR, but work fine in MSTS.,,,,,,,,,,,,,,,,,,,
,

Possibly because the Lights section is in the wrong place. Lights go after the Coupler section not before.

[TGM]

Hi Neil,

I didn't realise that you had created your static engine through RR. Now I see, it is classed as a carriage & not an engine. I made mine straight from the engine files so they are classed as engines.

All you have to do is change the unit numbers from two & three to zero & you should be good to go.
I just made one up using RR & it worked fine.

regards Tom

[markus1996]

Hi Markus,

In my copy of DPU it looked like you had two executables - one was labeled single - one multiple - something like that - I don't have it in front of me at the moment... The way I've been using it - is when processing a single file - I would drop it on the DPU I thought was for single files - when I did a bunch at the same time - I rdropped them on the one I thought was for multiple files... In all fairness to you - I probably didn't read the instructions and therefore I could have a gross conceptual error in its use... [...]

Ah, sorry - my bad, I read something totally different into your words.

Yes, there are two EXEs in the DPU pack, one that only processes one file at a time, and one that SEEMS to process multiple files at a time. However, what the latter one actually does is receive multiple files for processing by DPU and pass one after another to the other DPU exe (which processes them one at a time).

Thus, the error is probably independent of the process you use - in both cases, it´s the same program that does the work, it only gets its info what to work with from different sources. This shouldn´t cause a difference actually, but I will look into it when reworking and updating this part of the program.

[...] It seemed to work though - I even figured out how to turn the alerter off and the horn triggers bell options... It's a fantastic utility - I have plans to modify it so I can set all my steam locomotive controls the same with the same drag and drop ease...

Regards,
Scott

You can modify the data profiles in a way to include steam locomotive tokens, but be prepared DPU will not work on ENG files for any other loco type than Diesel, currently. This limitation has been carried over from the initial release, when data profiles were not yet available, but was left in place since in this current experimental release, DPU was only tested on Diesels.


Cheers, Markus

[qballbandit]

Ok Tom, I'll give it a shot. Thanks much!

Charles - so that makes a difference in OR, because it sure doesn't in MSTS??