[thegrindre]

Hi all,
If this is the speed limit (F5) for the route you are running on then it's never correct for me. I can load the same route 7 times in a row and get 5 different LIMIT readings and it's never the route limit. What is this LIMIT?
Why doesn't this work? It has never worked correctly for me for the past two years. I keep waiting for it to be fixed but it never does.
Can this be fixed before the next release?

Oh, BTW, I'm running the most latest ORTS beta as of yesterday.

http://www.elvastower.com/forums/public/style_emoticons/default/sign_thank_you.gif

http://www.elvastower.com/forums/public/style_emoticons/default/oldstry.gif

[vince]

Hi Rick,
Are you starting each time at the same location and the same engine?

Quote

What is this LIMIT?

It's the track or signal speed limit for the location you are. For instance, I open one of the activities on the LIRR in the Fresh Pond East Yard running track. Limit = 25. If I start a different activity in the same yard but in the actual yard tracks Limit=15.
Limit is the lower of either track or signal speed for a particular location.'
The maximum allowed speed (MAS) in a route is defined in the routes routename.trk file.

regards,
vince

[thegrindre]

No. Engines and consists are different most of the time. Starting points are the same most of the time. Time is the same most of the time at 10am.

http://www.elvastower.com/forums/public/style_emoticons/default/oldstry.gif

[Hobo]

Rick , I've noticed the same thing as you . I think it might be the velocity setting of the engine that you're running at the time because the speed limit given doesn't match the one that is on the track and switch info . Not real sure though .

[thegrindre]

I have no signals nor any speed limits on the routes I run. 30 MPH is the limit for the whole route.
Last time the LIMIT read 11. When I exceeded that the monitor turned red. I don't like that.

I have a constantly color changing monitor. http://www.elvastower.com/forums/public/style_emoticons/default/thumbdown3.gif

http://www.elvastower.com/forums/public/style_emoticons/default/oldstry.gif

[steamer_ctn]

From memory the Max Route speed limit is set by the speed in the relevant consist (CON) file.

Hence why it seems to be different if you are running different trains.

[roeter]

The speed limit is the lowest value out of the following set of values :

• Overall route speed limit
  
• Max speed set by speedpost or signal
  
• Max speed defined in consist definition
  
• Lowest value of max speed as defined for all vehicles which make up the train

So, starting with different trains each time could indeed well lead to different limit values.
You need to check all .eng and .wag files as well as the .con files to check for speed limit values.

Regards,
Rob Roeterdink

[Hobo]

Rick - I tried a 4-8-4 on a route and the limit was 50 . I restarted with a shay , same spot , same route , everything the same - limit was 20 . I gather the limit is what route specifies for that area unless the selected engine won't go that fast it then gives the limit for that unit . Makes sense - doesn't matter what the speed limit is on a highway if you're on a bicycle .

[timothyskinner]

 roeter, on 15 December 2016 - 01:24 AM, said:

The speed limit is the lowest value out of the following set of values :

• Overall route speed limit
  
• Max speed set by speedpost or signal
  
• Max speed defined in consist definition
  
• Lowest value of max speed as defined for all vehicles which make up the train

So, starting with different trains each time could indeed well lead to different limit values.
You need to check all .eng and .wag files as well as the .con files to check for speed limit values.

Regards,
Rob Roeterdink

Yes.
If you have a lot of consists to check then Context will do the job, but it does change all....
This tutorial is helpful for metres/second (in MSTS) to mph speed setting:
http://msts.steam4me...s/ai_speed.html

.

[charland]

Hi Rick,

Are you starting the activity in a siding somewhere where there is no speed limit set at the end of the siding? Just "exploring" maybe?

Paul :-)

[thegrindre]

 charland, on 15 December 2016 - 07:36 AM, said:

Hi Rick,

Are you starting the activity in a siding somewhere where there is no speed limit set at the end of the siding? Just "exploring" maybe?

Paul :-)

Hi Paul,
Yup. You 'guys' told me to to set my Start Point ending in a dead end so you don't run over your own green route line. Doing this has solved all my route running issues I was having.

http://www.elvastower.com/forums/public/style_emoticons/default/oldstry.gif

[atsf37l]

Lemme add a few scoops of coal to this fire.

Route: Rio Grande Southern

Max speed limit for the route: 25mph

Restricted speed limit for the route: 15mph

Installed speed limit restrictions: Zero

Signals on the route: Zero

Path: Telluride (on the main headed for the end of the branch at Pandora)

Locomotive: RGS T-19 20 of 1941, MaxVelocity: 30mph

Limit displayed in F4: 12mph

Second Scenario, all of the above except,

Locomotive: RGS T-19 25, MaxVelocity 30mph

Limit displayed in F4: 25mph

The only difference in the engine and wag files for these two locomotives are the names of the files. Unless there is something in the shape files that limit velocity, which I have uncompressed and viewed over thousands of lines of code with no reference to speed or velocity, then I can't for the life of me figure out why these two locomotives should receive different limits from the software. All of the above tests were in Explore mode.

In MSTS, running the exact same scenarios, both locomotives have a posted F4 Limit of 25mph, so this issue is strictly an OR issue. These are only two of my engines that experience these differences. One of them, C-19 No. 41 will have a different speed limit after a save when out on the road than when the save was made. It'll be at 12 mph with a yellow F4, quit the program and come back in later with a restored save and it'll be 25 mph and green.

Sumpthins not right here lads.

:bigboss:

[thegrindre]

It would be nice if these coders would change it back like MSTS uses the LIMIT tag. It shouldn't have anything to do with engine or wagon speeds. It's supposed to display the section of track's speed limit you're running on.
And, MSTS does it very well.

Can this be fixed before the 1.2 release?

http://www.elvastower.com/forums/public/style_emoticons/default/sign_thank_you.gif very much.

http://www.elvastower.com/forums/public/style_emoticons/default/oldstry.gif

[atsf37l]

Most diesels I own have limiters that squawk at you when you exceed their geared limitations. And most steam engines will thrash themselves into oblivion if you go too fast - when the exhaust is a "whoosh" you've probably exceeded your limits. So you're right Rick. It should be track speed limit and not governed by equipment limitations. In my above example I want it to say Limit: 25mph from Ridgway to Durango and all points in between! :bigboss:

[Csantucci]

OR takes into account also the MaxVelocityA parameter (which is in meters per second) of the .con file to define the max allowable speed for the train. Check this.