EricF, on 22 July 2014 - 03:41 AM, said:
But seriously, MSTS is, well, a train wreck as far as software goes. Without the BIN patch and workarounds developed over the years, it probably would have died off years ago.
The file formats used by MSTS are downright simplistic in some ways -- enough that Open Rails is right to treat them as just a subset of what it should ultimately be capable of. But there's so much content for MSTS out there; it's understandable that engineering enough fault-tolerance into OR when it sees MSTS files is still a good thing, in my opinion. It can use MSTS content as a springboard to bigger and better things.
The proposed MSTS 2 efforts never promised any backward compatibility or interoperability with MSTS -- probably because the programmers looked at the MSTS code and decided it would be better to just blow it all up and start fresh. OR has gone one step better, and has re-built the concepts behind MSTS, but all in modern, cleaner code. OR programmers have likely fought a lot of dragons along the way -- that's something to be thankful for.
It's important to realize that what OR is right now is just the tip of the iceberg -- with things like timetable-based operation, 3D cabs and the multiplayer feature, it's already leaving MSTS far behind. I do look forward to when MSTS "standards" are truly just a minimum or legacy feature subset.
:rofl2: Well said. Especially like the bit that mashed duct tape and star wars togerther - priceless. :rofl: