MSTS -what impact on OR?

[bavli]

MSTS vs. Real world

I was working on the Eng.files for a train which accelerates at 2kph/sec, which is equal to .556m/s^2. This requires 556N per tonne of train. Sure enough,this is what you get on the F5 HUD acceleration line when you apply full power-things are where they should be. However, when you look at the clock in going say, from say 20 to 80kph you see it took 24 sec. At the same time the distance recorded on the HUD odometer when going at a steady speed is absolutely consistent with recorded speed-120kph will get you 1000 meters every 30 seconds. On the NEC the distance between milepost 123 and MP23 is,from the odometer,( 125246-4379)=120,867meters for the 100 miles.
Welcome to the world of rubber rulers.

Why am I bitching about this? Because it makes comparing simulated performance to real world performance difficult. Could you go from x to y in the time engineman Z did on such and such a day?

Better yet, can the people at Open Rails do anything about this? This would be a step in the right direction.

By the way is there any comparable difficulty with RW or Trainz?

[GoGoran]

What ... ?!?

[longiron]

MSTS vs. Real world

Welcome to the world of rubber rulers.

Why am I bitching about this? Because it makes comparing simulated performance to real world performance. Could you go from x to y in the time did such and such a day?

Better yet, can the people at Open Rails do anything about this? This would be a step in the right direction.

By the way is there any comparable difficulty with RW or Trainz?

It's well known that MSTS incorrectly calculates the time/distance formula - you can see that in timetables for MSTS. The player distance calculation is based on the time step setting in MSTS. In addition, the way MSTS calculates curves on elevations is totally wrong resulting in a difference of up to 20% from the proper distance.

This does not impact OR as we fixed the distance/time calculations within the software. From a posting regarding an earlier release: " One thing with MSTS that really drove me to distraction was that train, speeds distance between stations and the times did not compute. It appeared MSTS calculated the distance the vehicle traveled incorrectly. This is certainly not the case with this current release. VERY GOOD, one can now run to a proper timetable. Timing between points a known distance apart shows an consistent accuracy of around 1.4%. A run on a route I have previously checked for accurate positioning of the track and stations taking great care to run at the correct speeds produced an arrival that was dead on time after 1 hour and 11 minutes, something MSTS was incapable of."

[bavli]

Thank-you for the info-this is good news. I have not used OR,but it looks to be the way to go.