NEC mileposts in wrong locations

Train-Sim

"NEC mileposts in wrong locations..."

Email this topic to a friend
Printer-friendly version of this topic
Bookmark this topic (Registered users only)
Previous Topic | Next Topic Conferences MSTS Activity Design (Protected) Original message
cruzjohnm (2 posts)
Jun-13-01, 09:28 PM (EST) "NEC mileposts in wrong locations..." Forgive me if someone has already posted regarding this problem...When I first ran MSTS using the Philadelphia-Washington route, I noticed that the speed limits, especially in urban areas, did not seem to correspond to the real-world speed limits as reflected in a 1999 Amtrak Northeast Corridor employee timetable.

After a few hours, I realized that the speed limits were basically correct for the mileposts, but that the mileposts were offset about four miles north of their real-world locations! As one of several examples, Baltimore is located at about real-world MP 95. But, it is located a few miles south in MSTS. This results in an unrealistic speed limit through Baltimore station of 75 MPH, which is correct for a location four miles south thereof. The correct speed limit of 30 MPH for real-world MP 95 and Baltimore station appears in MSTS in a rural area few miles north of the city.

Some might disagree, but I think that this seriously compromises the realistic playability of at least the Northeast Corridor route. We are left with the extremely unrealistic result of barrelling through urban areas at high speeds, and crawling along on high-speed tracks in the middle of nowhere. Anyone know of a way to fix this, perhaps with the tools contained in MSTS? Thanks in advance.

JMCIII
Alert Edit | Reply | Reply With Quote | Top
Table of Contents

Subject Author Message Date ID RE: NEC mileposts in wrong location... MTABusRunner Jun-16-01 1

Lobby | Topics | Previous Topic | Next Topic
Messages in this topic
MTABusRunner (7 posts)
Jun-16-01, 05:32 PM (EST) 1. "RE: NEC mileposts in wrong locations..." I wish I knew how to fix this problem, but I don't. I do concur that Baltimore is placed a bit too far South of Philadelphia. As a result, both myself and another fan have noticed early arrival times at Baltimore on Northbound trips. Then, when departing on time, a late arrival at Wilmington can be expected.Living in Baltimore and travelling to Washington often on the Corridor, my own observations do seem to verify that there is some "missing territory" in West Baltimore, while East Baltimore seems a bit long. As an aside, the trackage pattern is totally off in Baltimore as well. Northbound thru trains use track 6, while Southbounds use track 7. The trains use the tube of the Hoffman Street Tunnel that is disconected in game play. In the game, most trains use tracks 3 & 4 which are used mostly for MARC Commuter trains in reality, only used infrequently for Long-Distance trains like the Crescent and Silver Star when their times are close to a Corridor train. Remove | Alert Edit | Reply | Reply With Quote | Top

Lock | Archive | Remove

Lobby | Topics | Previous Topic | Next Topic