What about the route merging bug in 19 where Trainz would just hang during the merging and you would have to force quit Trainz sometimes resulting in a DBR when you restarted Trainz? I think TANE and 22 don't have that issue, yet one person here said that 19 is the most stable version even over 22. So, how do you merge two routes that don't merge in 19 and use the merged route in 19? If you import to 22 you can't go back and you can't import 19 routes to TANE.
Correct. Even the early version and the first couple of service packs in TRS22 had that problem as well as the portal problems that plague TRS19. It was as if the code was the same and all they did was change version numbers.
The current version of Plus, as many will hate to admit, I'm not that familiar with Platinum since I only use that for testing assets, is pretty stable. I use Surveyor for over 8 to 10 hours on some days without any hang. The Bulk Update and Replace works in both Surveyor versions, although it's still slow in Classic as I reported and others have too now. I also discovered if I leave things alone and let it run, and not poke around, it'll complete. This issue has been reported by others and myself. I always save prior to running this just in case something decides to take a dive, but saving early and often has been part of my Trainz MO since the early days when a BSOD wasn't uncommon when exiting along with an occasional GPF error.
The big issue though, is the Schedule Library in the session editing when the interface has been maximized. This has been reported and acknowledged as a problem. Hopefully, this issue will be fixed soon. My workaround is to use an un
Other than those issues mentioned, Driver works quite well now. I ran my bugaboo Gloucester Terminal Electric route with well over a dozen AI tram drivers, trains coming from portals, and myself driving for hours until I got tired rather than for 15 minutes where I had to chase AI drivers around and constantly untangle them and put them on timeouts.
I also ran my really huge ancient route, started in TRS2004, ca. the first week of January 2004. This route has 50 or more drivers running a passenger service between terminals and multiple portals and extends close to 350 km, all without any problems. The AI did what they wanted to do while I switched trains in one of the freight yards and ran a local to various industries. I had this route running for about 4 hours before I got tired of driving and did something else.
If the issues with the Schedule Library and other rules that use that interface are fixed sooner than soon(tm) this will be a good version.