Conrail

[geepster775]

I coulda swore that was a desktop console era thing, that these locos definitely pre-dated....

But as they say, "It's your world, boss"

[CSRX]

I coulda swore that was a desktop console era thing, that these locos definitely pre-dated....

But as they say, "It's your world, boss"

Some of the B40-8's I ran, when you blew the horn, the bell rang, and those were the control stand B40's, rather than the desktop controls... So, not sure exactly when it started with this feature.

[Curt C]

Look in the eng file for the line: DoesHornTriggerBell( 0 )

Then simply change to: DoesHornTriggerBell( 1 )

Hope that helps Curt

I usually change it the other way around as I dislike the auto bell.

Yeah, that's the issue - I've always changed the bell out that way, but the layout on these eng files are different from what I've ever seen. There is no DoesHornTriggerBell line that I can see.

[brama]

TrainSimulations has just released a pack of locos in Conrail livery.

Which Open Rails routes are appropriate for the use of these 1980s/1990s locos?
From the little general knowledge I have of of Conrail I am assuming that they didn't operate in the California/Arizona region, which would rule out using any of TrainSim's routes?

During periods in the 80s and 90s Canadian Pacific was power short (as usual) and leased everything they could get their hands on. Conrail units were a familiar sight, judging from photo's of that era. So the MacTier sub would also be an appropriate route. And the Conn River Route (CP interchange).

And you can always use them as interchange units paying back horsepower hours

[niknak]

Yeah, that's the issue - I've always changed the bell out that way, but the layout on these eng files are different from what I've ever seen. There is no DoesHornTriggerBell line that I can see.

I'm pretty sure you can just add that line Curt.

[R. Steele]

Yeah, that's the issue - I've always changed the bell out that way, but the layout on these eng files are different from what I've ever seen. There is no DoesHornTriggerBell line that I can see.

They are just an example of one of the different types of OR engine file configurations that use include files. Actually, once you learn how to use them, they are much more flexible and easy to use --- and make changes to -- then the legacy style MSTS eng files.

As Nick posted, just add the line to eng file --- here's an example, should work fine...

CabView ( GP38-2.cvf )
	HeadOut ( 1.85 3.432 5.014 )
	DoesHornTriggerBell ( 1 )
	include ( "..\\TS_COMMON_INC_V2\\Locomotives\\EMD_GP38_2\\EMD_GP38_2_ENG_Brakes_BF.inc" )

	include ( "..\\TS_COMMON_INC_V2\\Locomotives\\EMD_GP38_2\\EMD_GP38_2_Motive_250k_62_15.inc" )
	
	include ( "..\\TS_COMMON_INC_V2\\Locomotives\\Generic\\EMD_2ndGen_Monitors_Alerter.inc" )

	include ( "..\\TS_COMMON_INC_V2\\Locomotives\\Generic\\8_Notch_Throttle_Continuous_DB.inc" )
	
  Sound ( "EMD645_cab.sms" )

Here's an example of what I'm currently using...different - it requires the legacy MSTS eng file to be present in the parent folder one level above. IF you have a large trainset of MSTS engine files, this might be the way to go, instead of remaking all the files...this way simply adds OR parameters and physcis, OR parses the eng include file in the "OpenRail" folder and uses those parameters in place of the ones in the msts eng file one level above.

include ( "..\\UP_C45ACCTE_7964.eng" )
Wagon (
        Mass ( 186.8t )
	include ( "..\\..\\..\\..\\..\\Common.inc\\Locomotives\\Couplers\\Std_TypeF_TIGHT_Coupler.inc" )
	include ( "..\\..\\..\\..\\..\\Common.inc\\Locomotives\\Brakes\\Std_Loco_Brakes.inc" )
	ORTSAdhesion ( ORTSCurtius_Kniffler ( 6.454 21.351 0.161 0.7 ) )
	ORTSAdhesion ( ORTSSlipWarningThreshold ( 62 ) )
	include ( "..\\..\\..\\..\\..\\Common.inc\\Locomotives\\CarBody\\GE_ES44AC.inc" )
	ORTSBearingType ( Low )
	ORTSDavis_A ( 1804.57 )
	ORTSDavis_B ( 40.9783 )
	ORTSDavis_C ( 8.165142 )
	Comment( == Assumptions -Locomotive diesel/electric - speed - 65mph (105km/h), Low Torque Bearing, 6 axles, frontal area - 14.2m2, WagonWeight - 186.8 ton (metric), Drag 1.0 == )
)
Engine (
	Effects (
		DieselSpecialEffects (
			Exhaust1 (
			0 4.83 -2.801
			0 1 0
			0.23
			)
		)
	)
	ORTSDriveWheelWeight ( 186.8t )
	ORTSNumberDriveAxles ( 6 )
	include ( "..\\..\\..\\..\\..\\Common.inc\\Locomotives\\Std_Eng_C45ACCTE.inc" )
	include ( "..\\..\\..\\..\\..\\Common.inc\\Locomotives\\Brakes\\Dynamic\\C45ACCTE_186-8t_DynBrakes.inc" )
)

bandicam 2022-02-21 13-06-10-719.jpg

[R. Steele]

This nice set ( with good weathering variations ) points out a flaw in the TSRE- Consist Editor...it cannot parse include files...all the engines display 0kW power in the editor.

The TS team is really doing the community a service by making the effort to provide all the OR parameters, Diesel Engine Definitions, tractive curves, carbody and derail data...this set should run very nicely using the advanced adhesion/physics options in OR. Believe me, it's gotta be no easy task to model all these AND keep up with the code developments in physics!!!

ThumbsUp_Big.jpg

[Curt C]

Thanks to everyone for the help with the horn/bell setting.

[CSRX]

Upon further inspection of the CR set, I realized the GP38-2 fleet would also come in very handy, as most of the lease units on the VRS are former PC/CR GP38-2's, except the couple that are former PC/CR GP40's converted to GP38-2's, and the three that oddly have BNSF spec horn placement, ditch lights, etc, which I am sure I could manage to make up in TSM.

So I guess this means my lease unit set, gets placed on hold from release yet again.. Sadly that pack is growing too.. haha

[seagoon]

Can the original MSTS Activity Editor be used to create consists?

[charland]

For OR? I still create everything in MSTS, routes, activities, and yes, consists. They all work in OR.

Paul :-)

[R. Steele]

Can the original MSTS Activity Editor be used to create consists?

Ahh, probably not with these type of engine files. I'm just guessing, since I don't run MSTS or the editors. I think the editors would probably crash with these files or worse --- erase something, like the MSTS Activity editor does with ORTS parameters.

They are missing many MSTS lines/parameters that OR does not use -- derail for instance -- and -- the coupler, brakes and other data...much of what is required is found the in the TS_COMMON_INC_V2 folder using include statements, and MSTS would not parse those.

[seagoon]

Ahh, probably not with these type of engine files.....

Okay, thanks, Gerry.
I wouldn't risk stuffing-up the files by taking them into the MSTS editor.

However, as I don't use TSRE, that leaves me out in the cold unless someone creates and uploads consists to the library.

[R. Steele]

Okay, thanks, Gerry.
I wouldn't risk stuffing-up the files by taking them into the MSTS editor.

However, as I don't use TSRE, that leaves me out in the cold unless someone creates and uploads consists to the library.

You're welcome, you could create consists manually with an editor...just choose an existing consist file...make it a template and copy paste what you want.

[slipperman]

Hi seagoon,
You could always try Route_Riter or the freeware ConBuilder available from the library here to create consists.

Then again, there's the consist editor supplied with TSRE5 - it's a separate batch file within the TSRE5 folder.

Cheers,
Ged