Interactive, linked specialty mileposts

[landnrailroader]

Colleagues,

Does anyone know how to create a milepost, to be linked, and which has the capability of
entering the mileage value. Someone did this with Southern Rwy. mileposts a long time ago
and I have permission to use them on my routes, but I also need mileposts of the
L&N standard.

Currently I create the required "dummy" milepost and place it as a marker. Then when I
put in signals etc., I place the real milepost (default item) and bury it under grade. This
one, for example, is on the west side the railroad yard at Corbin, KY.

I use TSM for object creation.

J. H. Sullivan

[commec61]

Hi Jerry,

You'll have to add it to your speedpost.dat file. This is where speed and mile posts come from.

[rick]

Hmmm, Can you make Burma Shave signs? 8-)




https://en.wikipedia.org/wiki/Burma-Shave

[Rick-MONON]

The MONON-2 has Burma shave signs and the Hook_Eye-2 route has the L&N speed posts and speedpost.dat you need.

[landnrailroader]

I'm not as concerned about speed posts as I am about mileposts. The Hook_Eye-2 uses the same mileposts (dummy)
and buried BN mileposts that I used. The NS route I mentioned uses the correct Southern milepost shapes and when
you place them, with the indicator on the track, you then key in the milepost number & other data, same as with the
BN default items. My questions was how can you create mileposts that would replace default mileposts, especially
with TSM. Currently I am working between Corbin & Knoxville, and that will require roughly 120 mileposts which I
can easily create as dummys as use the defaults buried.

I will say that Rick's modifications to the Hook & Eye did considerably improve it. I would put him in the arena of
"super detailers". If you ever piddled in model railroading, you know what a super detailer is.

J. H. Sullivan

[Rick-MONON]

Jerry

I could use the SRR mileposts and speedpost files for a maybe project.
Could you send them to me.

I will try to convert your static mileposts into a working milepost.

[Rick-MONON]

Here you go Jerry

PM me your email address, not sure the one I have is still good.

[landnrailroader]

Here you go Jerry

PM me your email address, not sure the one I have is still good.

I'll PM the email, but you may have the route those NS/SRR mileposts are in. It is a well done route
of the Charlotte to Raleigh line. I guess he selected that because he was interested in the NC
sponsored passenger trains. The route is in the library.

I am guessing that it is the contents of the speedpost.dat file, i.e. the individual entry groups,
that actually place the text. He used a .ace file that contains the numbers, and there appear to
be coordinate values in the .dat file.

ncrr_v2

Jerry

[eolesen]

I created a set of mileposts for my CNW routes which meet different needs, e.g. a post on the side of the tracks, or a line pole mounted plate.

Creating the shape is no different from anything else, and you'll need to write up each type in SpeedPost.dat similar to how you would make a custom signal. Here's the Speedpost.Dat for my shapes:

[email protected]@@@@@@@@@JINX0t1t______

Speed_Warning_Sign_Shape ( Us2TmpRedSpd.s )
End_Restricted_Shape ( us2ResSpeed.s )


Speedpost_Set
(
  Name ( MP-CNW-Pole )
	Speed_Sign_Shape ( US2PerSpeedL.s 1 -0.124 1.738 -0.185 0)
	Speed_Warning_Sign_Shape ( US2AdSpeedL.s 1 -0.006 2.046 -0.185 0)
	Speed_Resume_Sign_Shape ( us2ResSpeed.s 1 0 0 0 0)
	Speed_Digit_Tex ( signnumbers.ace )
	Speed_Text_Size ( 0.25 0.25 0)
  Milepost_Shape ( cnw-milepost.s 2
	  -0.5 5.6 -0.02 0
	  -0.5 5.6  0.02 180 )
  Milepost_Digit_Tex ( signnumbers.ace )
  Milepost_Text_Size ( 0.2 0.2 0.0)
)

Speedpost_Set
(
  	Name ( MP-UP-Stick )
 	Speed_Sign_Shape
		( up-milepost.S  1 
		0 2.2 -0.06 0 )
	Speed_Digit_Tex ( signnum.ace )
  	Speed_Text_Size ( 0.35 0 -0.35 )
	Milepost_Shape ( up-milepost.S 2
	  0.0 2.2 -0.06 0
	  0.0 2.2  0.06 180 )
	  Milepost_Digit_Tex ( signnum.ace )
	  Milepost_Text_Size ( 0.35 0 -0.35 )
)

Speedpost_Set
(
  	Name ( MP-UP-1T-Offset )
 	Speed_Sign_Shape
		( UP-Milepost-1tOffset.s  1 
		0 2.2 -0.06 0 )
	Speed_Digit_Tex ( signnum.ace )
  	Speed_Text_Size ( 0.35 0 -0.35 )
	Milepost_Shape ( UP-Milepost-1tOffset.s 2
	  -2.0 2.2 -0.06 0
	  -2.0 2.2  0.06 180 )
	  Milepost_Digit_Tex ( signnum.ace )
	  Milepost_Text_Size ( 0.35 0 -0.35 )
)

Speedpost_Set
(
  	Name ( MP-UP-2T-Offset )
 	Speed_Sign_Shape
		( UP-Milepost-2tOffset.s  1 
		-2.0 2.2 -0.06 0 )
	Speed_Digit_Tex ( signnum.ace )
  	Speed_Text_Size ( 0.35 0 -0.35 )
	Milepost_Shape ( UP-Milepost-2tOffset.s 4
	  -2.0 2.2 -0.06 0
	  -2.0 2.2 0.06 180
	  7.0 2.2  0.06 180 
	  7.0 2.2  -0.06 0 )
	  Milepost_Digit_Tex ( signnum.ace )
	  Milepost_Text_Size ( 0.35 0 -0.35 )
)

Speedpost_Set
(
  	Name ( MP-UP-2Y-Offset )
 	Speed_Sign_Shape
		( UP-Milepost-2YOffset.s  1 
		0 -2.2 -0.06 0 )
	Speed_Digit_Tex ( signnum.ace )
  	Speed_Text_Size ( 0.35 0 -0.35 )
	Milepost_Shape ( UP-Milepost-2YOffset.s 4
	  -2.0 2.2 -0.06 0
	  -2.0 2.2 0.06 180
	  6.0 2.2  0.06 180 
	  6.0 2.2  -0.06 0 )
	  Milepost_Digit_Tex ( signnum.ace )
	  Milepost_Text_Size ( 0.35 0 -0.35 )
)

Speedpost_Set
(
  	Name ( MP-UP-3T-Offset )
 	Speed_Sign_Shape
		( UP-Milepost-3tOffset.s  1 
		0 -2.2 -0.06 0 )
	Speed_Digit_Tex ( signnum.ace )
  	Speed_Text_Size ( 0.35 0 -0.35 )
	Milepost_Shape ( UP-Milepost-3tOffset.s 4
	  -2.0 2.2 -0.06 0
	  -2.0 2.2 0.06 180
	  12.0 2.2  0.06 180 
	  12.0 2.2  -0.06 0 )
	  Milepost_Digit_Tex ( signnum.ace )
	  Milepost_Text_Size ( 0.35 0 -0.35 )
)

Speedpost_Set
(
  	Name ( MP-UP-3Y-Offset )
 	Speed_Sign_Shape
		( UP-Milepost-3yOffset.s  1 
		0 -2.2 -0.06 0 )
	Speed_Digit_Tex ( signnum.ace )
  	Speed_Text_Size ( 0.35 0 -0.35 )
	Milepost_Shape ( UP-Milepost-3yOffset.s 4
	  -2.0 2.2 -0.06 0
	  -2.0 2.2 0.06 180
	  10.0 2.2  0.06 180 
	  10.0 2.2  -0.06 0 )
	  Milepost_Digit_Tex ( signnum.ace )
	  Milepost_Text_Size ( 0.35 0 -0.35 )
)

Disclaimer: I've done nothing with speeds. Only mileposts.

The number after the Milepost_Shape indicates how many faces get numbers. If you see 2 sides, it's a shape that only shows up on one side of the tracks but with numbers on both sides of the post. 4 sides means two mileposts within the shape and both get numbers on both sides.

The next two rows are the X Y Z positioning, and the last number is the rotation of the text. My signs are flat, so 0 and 180 are appropriate. For a square post, you might want 90 and 270 to get numbers, or perhaps you have an angled piece that you'd have to figure out the projection angle for...

capture__200463.jpg

Once the Speedpost.dat is done, the mileposts appear in the Track Objects list for the RE. Can't say what it does in TSRE...

capture__200453.jpg