Routes conflicting with XTracks in one way or the other
I write this to clarify some issues with a number of routes built using the early version XTracks 1.1 or some other track add-ons.
It is true that there can be problems with routes built with XTracks 1.1 but not necessarily all routes. I have downloaded and inspected all of these routes and would like to share my findings. Installing the routes on my system with XTracks 3.7 the routes Cannes-Grasse, PACA and Thionville-Luxembourg worked without any problems caused by XTracks 1.1. These three routes can be used with the latest release of XTracks. Only issue is not to tamper with the tracks in the Route Editor or you will loose the dynamic tracks. The other two routes, LGVA and RER B v1.0, both have problems that spring from XTracks 1.1 and canít be used with later versions of XTracks. Updated versions of these routes have been released that uses XTracks v3.9 or later (RER B v1.1 and LGVA v2.0).
Now the only remaining problem is with some commercial routes that completely ignores the community effort to make your MSTS life easier.
A corrected table for these routes and their requirements would look like this.
1) S&C 1930 - Seattle and Carlisle 1930 by Pat Dalton built with XTracks 2.0
I have added S&C 1930 by Pat Dalton to the table as this route has a similar issue being built with XTracks 2.0, it works fine though with later versions of XTracks from what I have been told.
(!RE) means these routes should not be worked on in the Route Editor with XTracks installed. Doing this and making changes to the tracks will destroy the route as dynamic tracks will then be lost.
The L2 v0.2 does NOT work with XTracks since it has it's own specialized version of the global tsection.dat. Please note that Chris Cykos new Chicago Elevated v0.3 (and future updates) is fully functional with XTracks. This route replaces and should not be confused with L2 v0.2.
RET Metro v1 was first released with a 'XTracks patch' that was faulty and not sanctioned by me. This patch altough appearing to work does not solve the problems with RET Metro v1 and should not be used. A new version of RET Metro v2 has been released and this is fully compatible with the standardized tsection.dat as from build #22. This means RET Metro v2 can be used with XTracks v3.9 and later, the patch for earlier versions of XTracks should not be used, update to the latest XTracks instead.
The Casino Express, Hokkaido and Usui Pass do NOT work with XTracks (or any other use of the standardized tsection.dat) as they each have their own specialized version of the global tsection.dat. If you want to use them I recommend a separate MSTS installation devoted to the route.
The Japanese routes Hokkaido and Usui Pass both by Twilight Express modifies the tsection.dat by adding their own entries in unused slots in the original tsection.dat. From what I've heard it does this by simply adding entries to the end of the file not checking if it's working with the original tsection.dat. The entries they add are in conflict with the standardized tsection.dat and thus those routes can not work with XTracks. This is similar to how the Maglev route from Abacus works and I suspect the Japanese routes and the Maglev route would have problems co-existing in the same MSTS but I don't know as I don't have these routes.
The London Brighton Express introduces a new problem I had hoped we could live without. The route installer also installs the standardized tsection.dat build #19 effectively backdating your XTracks installation to v3.6! Problem is easily solved by re-installing XTracks after the route but the route installer should have checked the build of the already present tsection.dat and made sure not to replace it if later. This is the main reason I don not allow XTracks to be integrated with any route installation.
The two Italian routes FORMIA-GAETA and SALERNO-NOCERA by Peppe Iannuzzi and available at www.amicitreni.net were built using a special tsection.dat file I belive came with some version of YTracks (not XTracks). That tsection.dat was not ment for released routes and thus causes problems with all other versions. Until this is resolved and new updated versions of these routes are available I must advice against their use. If you DO want these routes I recommend a separate MSTS installation devoted to the routes.
The (yes) notion of the standard routes with XTracks 1.1 & 2.0 is because though they appear to work fine there are a few issues with dynamic tracks that make for strange effects. An example can be seen at the southeast exit out of Essex on Marias Pass when running on the left hand track out of Philadelphia on the NEC is another example. This is the reason the compability was dropped between early versions of XTracks and versions 3.*. I strongly suspect that the L2 v0.2 and Maglev routes have similar problems.