Open Rails x.2027

[bprice]

I keep a separate folder for each update. I name them according to the download date. One advantage is if I an running unfinished activities. I can go back and finish rather than start over or just move on. When I no longer need a version, I just delete it.

[lindsayts]

That is disappointing. I was looking forward to that one. I certainly understand though. I almost gave up on the Sharon Springs sub then just decided to finish it. It only took four years.

You have to be tenacious as building a route will never be "easy", but it does pay to take a break now and then to clear ones mind.

As to how long it takes the late Alan Lownsborough when he did the "Adelaide hills and SE" route (an Australian route) took 4 years and 3000 hours to complete the task. The route covers the entire 205 mile distance from Adelaide to Mt Gambier and aslo has a number of the lines including branch lines total main line distance in the route being around 600 miles. This route has been praised by old South Australian railway men as being a very good representation of the lines and the era, its set in the 1950's. Alan when asked how he acheived the accuracy stated a friend of his travelled the lines and took 10's of thousands of photographs (digital camera's are great) and he worked from those. Alan not being able to travell due to illness.

Lindsay

[seagoon]

......With that in mind, I'd rather see ORTS get it right than continue to get it only halfway. We've seen enough of that mentality in the train sim world from the various commercial entities.

Hear, hear!

[twpol]

So OR is from the outset designed to run using MSTS add ons.

But it is not supposed to work correctly.

I guess i won't bother wasting my time posting any more bugs to their site then.

After all the usual know it all's have put me right again.

With regards to things that work in MSTS but not ORTS, there are two quite different possibilities:

* It has realistic/correct data and MSTS has implemented this feature more/better than ORTS. In this case, we strive to improve ORTS to work at least as well as MSTS.
* It has unrealistic/bodged data to make it work in MSTS. In this case, we'll do a little bending to try and cope but in general this is considered a bug in the content and not ORTS.

Please bear in mind that which of the two cases a particular thing is, isn't always clear - even to those that know a lot about MSTS and ORTS.

I would strongly recommend you always report bugs with things not working in ORTS, including if you can details on how it works in MSTS, and we can then figure out what the way forward is.

[bprice]

If I am reading what some have posted on this thread are saying correctly, it would be better to wait until there is a fully tested full release. I certainly don't agree. There have been times that I wasn't really happy with a weekly release. In those cases I posted a bug report or posted here what the problem was. More than once the problem was ME. Even in those cases I assume that I am not the only one and we can learn from each other's goofs.

This is one of the reasons I don't just use one version. If there is something that isn't working right, chances are it will be addressed soon. WE, that is ORTS users, are beta testers. We help make it better.

This program has taken MSTS far beyond anything I could have imagined. The effects like super elevation, cab vibration, and extended viewing distances have greatly enhanced the enjoyment of this hobby. I eagerly await each new release to see what new "toys" the developers have included. That is part of the fun.

[Frisky57]

That is disappointing. I was looking forward to that one. I certainly understand though. I almost gave up on the Sharon Springs sub then just decided to finish it. It only took four years.

Nothing much to add here, except that I agree with the above statement.