The official “stable” release version of Open Rails has advanced to version 1.2. There were a number of development breakthroughs that happened not long after version 1.1 was released, and these have been refined and are now part of the stable release. This includes the ability to have working turntables, and a host of other improvements.
The RailDriver desktop cab controller from PI Engineering has been available for quite some time now. Although it’s been reviewed before, most of those reviews are older or are focused on using it with Trainz or Train Simulator 20xx (formerly Railworks). I finally purchased one for use with Open Rails, and thought I’d share my impressions and add a newer review to the mix.
Microsoft Train Simulator is turning 15 years old, and it’s still going strong. Not bad for software that’s officially listed by Microsoft as “unsupported” by Windows Vista and later versions. But it’s still possible to run it in Windows 10 on its own, and Open Rails will keep MSTS content alive for the foreseeable future.
How far have we come? Well, just for fun, here are a couple of screenshots. (Click the images to see the full versions.)
The first is the original MSTS Marias Pass route, from the cab of the default Dash 9.Next is the same spot on Marias Pass 5 (A more modern re-worked version of the Marias Pass route) from a modern cabview of the Dash 9, and taken in Open Rails.Quite an improvement!
This version adds several MSTS compatibility features, such as refilling steam locomotive tenders from water troughs between the rails, support for speed limits in temporary restricted speed zones in activities, better brake functionality, improved sound handling, better handling of cab lighting in tunnels (night mode switching), and more.
There are also numerous improvements and additions to features specific to Open Rails, many persistent bugs fixed, and overall underlying improvements to the application code to allow for future development.
If you haven’t tried Open Rails, or if v1.0 wasn’t quite close enough to an MSTS replacement for running trains, it’s well worth trying out this latest version.
Note: Currently, there is an alternative route editor in independent development, but there is no replacement for the Activity Editor or other MSTS built-in editors yet. Open Rails provides an vastly improved environment to operate trains in. Creating and editing MSTS content still requires the original MSTS toolset or other third-party tools.
Beginning with Experimental version x.3369, it’s possible to clear trees appearing on the tracks in Open Rails. Not every route has this issue, but you’ll know it when you see it — Trees appear too close to the rails, in between the rails, in tunnel openings — anywhere a tree has no business being. If you run the same route in MSTS, the offending trees are nowhere to be found. So what’s going on?
When a route is built in the MSTS Route Editor, it’s possible to create “forest regions” — simple boundaries that define an area for trees to be automatically populated. If the tracks fall too close to, or even inside of, the boundaries of a forest region, MSTS will automatically suppress the trees that would intrude on the tracks. Open Rails doesn’t use the same method to separate trees from the rails, so some routes will display trees intruding on the tracks.
Early attempts to apply an algorithm to find and suppress tree/track conflicts where a forest region intrudes on the tracks could remove the trees, but incurred a heavy impact on frame rates. A recent re-evaluation of the methods has finally resulted in a successful means to prune away errant trees without adversely impacting frame rates or causing any other problems with scenery objects.
Route Riter has been, and still is, the must-have utility for maintaining an MSTS installation. Mike Simpson, the author, stopped updating it with version 7.6.26.
Another programmer and trainsim hobbyist convinced Mike to release the source code to him for continuing development. In itself, that’s not a bad thing.
Unfortunately, a couple of bad things have subsequently happened.
First, the follow-on version of Route Riter (7.7.x) initially garnered reports of installation problems and bugs.
Second, the programmer who holds the source code became involved in some unpleasant and retaliatory behavior at Elvas Tower and TrainSim. It very nearly caused Elvas Tower to shut down the forums. Since then, accusations have flown, bad behavior has blossomed, and in general a dark cloud has settled over the MSTS/Open Rails world.
Right now, as of the date of this post, the only version of Route Riter that is positively known by the trainsimming community to be reliable, simply through sheer numbers of satisfied users, is version 7.6.26.
The download page for the newer version, not released by Mike Simpson, contains a “Buy Now” link for US $20.00. The download, however is free. The current programmer apologized in a forum post that there was a problem with the web page’s shopping cart function. However, the problem has not been corrected yet.
Version 7.6.26 can be downloaded from Mike Simpson’s website HERE.
If Mike’s website or link ever goes away, the Internet Archive’s Wayback Machine has cataloged the download. Here are two working links which will let you download Route Riter 7.6.26:
Link 1, based on the latest version of Mike’s Site: Wayback Machine Link 1
Link 2, based on an older version of the site — which may compose better in your browser: Wayback Machine Link 2
Currently, I can only advise using version 7.6.26. Subsequent versions are NOT authored or supported my Mike Simpson, Route Riter’s original author. Subsequent versions have not been extensively tested in the trainsimming community, and, as such are not widely trusted.
Editorial Note: Route Riter version 7.6.26 and earlier is the work of Mike Simpson and no one else. Any DMCA-related claims pertaining to version 7.6.26 and earlier are solely in Mike Simpson’s hands. No other parties should be allowed to lay any claims to version 7.6.26 or earlier. With respect to version 7.6.26 and earlier, this website does not recognize any DMCA claims from any party other than its creator, Mike Simpson. Rights to subsequent versions may be held by other parties. This post does not link to any subsequent versions. The MSTS Roundhouse does NOT endorse any version of Route Riter beyond 7.6.26.
I began an entry quite some time ago when discussion of the influence of Open Rails on the general trainsim community erupted into a fair bit of debate. Now that Open Rails has reached its Version 1.0 milestone, it seemed appropriate to revisit the topic and finish writing about it.
Open Rails v1.0 is finalized and released. Enjoy!
It’s a huge milestone to effectively say OR has met its initial set of goals. If you haven’t tried OR, now is the time. It’s already capable of more than MSTS, and development isn’t pausing at all. There will be refinements and new capabilities to add; the experimental and unstable versions will continue to be offered for testing and evaluation.
Right now, Open Rails can do virtually anything that MSTS could ever do. Any remaining differences are minor. Known bugs exist that will be addressed, but they’ve generally been found to be less significant or “edge cases”, in development terms, that typical operation won’t see effects of them. The “showstopper” bugs appear to be resolved. At this point, moving the focus beyond MSTS will allow more new approaches to old problems – and that alone may provide for ways that will both solve old remaining bugs and open up new capabilities.
What’s in the future? Not only further refinements and improvements in functionality, but now the editors and tools will come into closer focus over time. We already have basic path editing in the Track Viewer, the completely new and realistic Timetable Mode and the solid foundation for multi-player capability. Ideas are already circulating for how to achieve an MSTS-style activity editor and a route editor. And gradually, OR will grow beyond the MSTS “box” and into its own environment that will encompass MSTS content plus its own capabilities.
So, for anyone still wondering if there will ever be a train simulator to replace MSTS, it’s safe to say it’s here. Open Rails is ready and will continue to grow.
Mike Simpson’s Route Riter is the go-to utility for both Open Rails and MSTS for checking and fixing rolling stock and route files, plus it has an invaluable set of tools for route builders and a good consist editor. It also includes the TSUtil suite and provides an interface to the TSUtil tools inside the Route Riter interface. TSUtil, however, needs Java to run, and that’s added some extra manual configuration steps to get it working in modern versions of Windows and Java.
The most common problem is that, after installing Route Riter or after taking a Java update with an existing, working Route Riter installation, you get an error when Route Riter Starts that says “You do not have a Java Runtime system” and Route Riter won’t work. It sounds bad, what’s really happening is usually fairly simple to fix.
Open Rails v1.0 is getting closer…
According to a recent post on the Elvas Tower forums, it’s not long until v1.0 of Open Rails will be ready. There’s been a lot of discussion over just where the cutoff should be for MSTS compatibility in order to declare a 1.0 version. As of now, it looks as if the last few un-met milestones will be held off for version 1.1 and the current state will be wrapped up in preparation for a 1.o release.
There’s still work to be done; primarily in the realm of updates to the documentation, the creation of an installer for version 1.0, updates to the Open Rails website, and even a demo route (Which may likely need to be self-contained, with no MSTS assets or dependencies).
Open Rails has come a long way in the last year or so — not only with excellent compatibility with MSTS routes and assets, but with the first steps into new improvements, including an entirely new timetable operation system, multiplayer features and the beginnings of support for 3D cabs ,to name a few.
There is no date set for a 1.0 release yet — but it’s probably safe to say that 2015 should be a banner year for Open Rails development!