TABLE OF CONTENTS Introduction Route Information Sections Google Earth Project Google Drive Playing The Route How To Get Involved Conclusion INTRODUCTION Hello! My name is Brandon Phelan (also known as cActUsjUiCe) and I am the leader of the "Northeast Corridor Simulator Development" group. The group currently has around 730 members on Facebook and we have been planning the development of the Northeast Corridor in Train Sim World for the past three years. Members of the group have created content for Train Simulator over the years such as: Northeast Corridor: New Haven to Boston Northeast Corridor: Wilmington to Washington Keystone Corridor Repaints Sound/Physics Mods Now we are ready to create the entire Northeast Corridor for Train Sim World! ROUTE INFORMATION The Northeast Corridor is located in the northeastern United States and runs from Boston, Massachusetts to Washington D.C. The route is 455 miles in length and is completely electrified with overhead catenary. We will be creating this route in the present day and updates will be released in order to stay current with the latest construction projects. Until additional rolling stock is created, only Amtrak services will be replicated. It may be possible to utilize existing rolling stock for other services such as commuter rail in the meantime. Our ultimate goal with this project is to have the entire Northeast Corridor created in a single Train Sim World route package. This is a monumental task and will take years of development to accomplish. In order to keep our goals reasonable and to maintain community interest, the development effort is being divided into several sections. SECTIONS We have chosen to divide the development effort into thirteen distinct sections. We will fully create and test each section before moving onto the next. This will allow the players to experience and enjoy a fully functional, decorated, and meaningful section while we work on the next one. Keeping each section a reasonable size will help to minimize developer burnout. The first measurement figure listed is the actual track length of the section. The second measurement figure is how far we will actually be laying track and decorating. This extra area is being fully decorated to maintain an immersive environment for the players. It would be a shame if all decoration suddenly ended as you approached the end of the section! Section 1: Boston South Station – Providence · 43.58 miles (End of track at Boston – West end Providence platform) · 44.60 miles (43.58 miles + track extending to Milepost 184) · Travel Time: ~40 minutes Section 2: Providence – Westerly · 43.75 miles (West end Providence platform – West end Westerly platform) · 44.00 miles (43.75 miles + track extending to West end curve at Milepost 141) · Travel Time: ~35 minutes Section 3: Westerly – Old Saybrook · 36.15 miles (West end Westerly platform – West end Old Saybrook platform) · 37.46 miles (36.15 miles + track extending to West end curve at Brook interlocking) · Travel Time: ~45 minutes Section 4: Old Saybrook – New Haven Union Station · 32.98 miles (West end Old Saybrook platform – West end New Haven platform) · 34.37 miles (32.98 miles + track extending to West end curve at Milepost 71) · Travel Time: ~35 minutes Section 5: New Haven Union Station – Stamford · 39.19 miles (West end New Haven platform – West end Stamford platform) · 39.83 miles (39.19 miles + track extending to West limits CP 232 interlocking) · Travel Time: ~45 minutes Section 6: Stamford – New York Penn Station · 36.00 miles (West end Stamford platform – West end New York Penn platform) · 38.73 miles (36.00 + track extending to West end Hudson River tunnels) · Travel Time: ~45 minutes Section 7: New York Penn Station – Metropark · 24.46 miles (West end New York Penn platform – West end Metropark platform) · 25.29 miles (24.46 + track extending to first curve West of Milepost 24) · Travel Time: ~35 minutes Section 8: Metropark – Trenton · 33.36 miles (West end Metropark platform – West end Trenton platform) · 34.48 miles (33.36 + track extending to Milepost 58, just over river) · Travel Time: ~25 minutes Section 9: Trenton – Philadelphia 30th Street Station · 32.54 miles (West end Trenton platform – South end Philadelphia 30th Street platform) · 33.34 miles (32.54 + track extending to Milepost 2) · Travel Time: ~28 minutes Section 10: Philadelphia 30th Street Station – Wilmington · 25.60 miles (South end Philadelphia 30th Street platform – South end Wilmington platform) · 26.68 miles (25.60 + track extending to Milepost 28) · Travel Time: ~21 minutes Section 11: Wilmington – Aberdeen · 38.18 miles (South end Wilmington platform – South end Aberdeen platform) · 39.38 miles (38.18 + track extending to South end of curve that is North of Milepost 67) · Travel Time: ~30 minutes Section 12: Aberdeen – Baltimore · 30.20 miles (South end Aberdeen platform – South end Baltimore platform) · 31.94 miles (30.20 + track extending to South Portal of B&P Tunnel) · Travel Time: ~22 minutes Section 13: Baltimore – Washington Union Station · 40.10 miles (South end Baltimore platform to Milepost 136 at Washington Union Station) · 41.67 miles (40.10 + track extending South of First Street Tunnel at Milepost 137) · Travel Time: ~45 minutes View a full route map divided into sections here: http://drive.google.com/uc?export=view&id=1IfM8umlYZwBjqQqpMwb1pdcfqfuyJ3f2 GOOGLE EARTH PROJECT There's a project that we’ve been working on for the past few years that we call the "Google Earth Project". Our goal with this project is to create a fully visual representation of all the official documents we have accumulated. This information includes speed limits, signals, defect detectors, curve parameters, and interlockings. Instead of wasting time sifting through documentation, developers simply have to refer to the Google Earth Project to obtain the information they need. Here are some photos for your viewing pleasure! Underground track plotted at Boston Back Bay. The path of these tracks was plotted using curvature values from official documentation. Speed limits, signals, and mileposts in Canton Junction, MA. Tracks, signals, and switches in Harold interlocking and Sunnyside Yard. East Side Access elements are visible as well. An amazing feature of the Train Sim World editor is the ability to import a KML file and lay it over the route’s terrain. The Google Earth Project can be exported to such a file! We never anticipated having access to such a feature, but it’s going to definitely make the development process a whole lot easier! You’re welcome to view the absolute latest copy of our Google Earth project. Simply download the KML file and open it with Google Earth. Download Google Earth: https://www.google.com/earth/versions/ Download Google Earth Project KML: https://drive.google.com/file/d/0Bz8eG2qa_5ltUEVTNkUzQ3RXMWM/view?usp=sharing GOOGLE DRIVE Since the group’s creation, we have amassed a wealth of documentation and photos for this project. All of these files are kept on our Google Drive. Official plans for track & signal reconfiguration at Kingston, RI. Made public via an official FRA request to modify the signals in this area. Feel free to take a look for yourself! Northeast Corridor Simulator Development Google Drive: https://drive.google.com/drive/folders/0Bz8eG2qa_5ltdF9QeXNORHhtRTg?usp=sharing PLAYING THE ROUTE As we develop the route, players will be able to test the absolute latest changes to the route via a "Beta branch" of our project source. We are hoping that Steam Workshop functionality will allow the players to test the latest progress each time we make changes. If not, then we will find a workaround to get the content to you! The public version of the route should be available on the Steam Workshop just like in the original Train Simulator. This branch will be released as stable as possible. Keep in mind that the beta branch will have the absolute latest changes. Test at your own risk! The route is not guaranteed to function as intended. HOW TO GET INVOLVED There are many ways to get involved with our group and contribute to the development effort. First, I highly recommend joining our Facebook and Discord groups! This will allow you to communicate with other members and get the latest information on project progress. Facebook: https://www.facebook.com/groups/NECSimDevelop Discord: https://discord.gg/nqktYVu If you wish to assist us by becoming a developer, please post in either the Facebook or Discord group. We can provide information on how you can best assist! CONCLUSION We are really excited about developing for Train Sim World! It’s been a long three years of planning, but we are finally in the home stretch. Stay tuned to this thread for updates on our development effort! If you have questions or comments, please leave a reply!