Route_Riter & OR

[rlkimbal]

It would be nice if a future version of Route_Riter would catch the same errors as OR and attempt to correct them. I have been surprised at the number of warnings I get from OR on routes wcich have no errors in R_R.

[baldwin]

Development of Route Riter has ceased so what we have is it. The errors that you are seeing in OR have always been present, in most cases, but MSTS is more tolerant in that respect. OR has a much more robust error trap. RR was designed to catch the known errors in MSTS, but with no access to the MSTS source it was and always will be impossible to find and correct anything else.

[apco25]

MSTS had nothing even close to error tolerance. In fact MSTS just ignored error it didn't know what to do with or as we are all too familiar, would produce vauge errors that were difficult to track down or would simply just crash. Remember, the MSTS code was never fully finished, but a semi functional version rushed to market by Kuju for Microsoft. OR, is pickier, but also far more forgiving at the same time. Errors that would have barfed MSTS are simply noted and informed to the user. Better still the errors are specific and not just a vauge suggestion as to what is wrong. Yet further, OR is also bringing out old, long standing coding errors, sloppy, duplicate work and all sorts of minor issues that were floating around in MSTS routes for years now.

The "errors' that OR finds are pretty simple and easy to fix. The error log has everything you need to find and fix them.

Don't forget that OR is still developmental software so some things may be considered errors that are no more than code hasn't yet been written to handle a certain feature.

[eric]

1) correct that Mike has stopped enhancing R-R.

2) It's a bit of a mixed bag -- some things MSTS ignored, ORTS barfs on; some things ORTS flags and moves on, which would otherwise cause MSTS to trip over itself... For the most part, I find ORTS is far more stable.

[seagoon]

... For the most part, I find ORTS is far more stable.

Ditto.

[twpol]

The error log has everything you need to find and fix them.

That's the aim, certainly.

OR also categorises things it finds quite deliberately: Information - something you should know about but can't fix (such as something not implemented yet), Warning - something you can fix (but which we'll cope with anyway) and Error - something you need to fix (because we can't cope).