Open Rails x.2027

[poochwilly]

I downloaded newest version x.2027. I run a couple of activities with the BNSF Scenic 2 plus the upgrade. Westbound coal, Lumber run and Canadian imports give the same error and won't load, something to do with a traffic file. When I look at all the stuff pertaining to the Route and traffic file it's all there, runs okay in MSTS just will not load in Open Rails.Strange, work in progress. I originally dl the 0.9 version then I moved up on the updated versions. Do you just remove the first version and extract new version to folder and carry on playing? Seligman has 1or 2 that do not work also.

Thanks Poochwilly

[seagoon]

Are you starting an Activity from scratch or trying to resume a previously-saved Activity?
In case it's the latter you need to be aware that Activities saved in one version of Open Rails cannot be resumed in any other version.

However, if the former then my suggestion is that you stop using any previous version of Open Rails and just use the most recent X-file, remembering that any saves made in that version must be resumed in that version.

For what it's worth, I've had no problem with any of the activities you've mentioned, running (and saving) them under the latest X-file.

[Don6218]

When I get an updated Open Rails, I just store it, then copy and paste right over the old in the appropriate folder. I always have all the versions stored to return to if required, separately from the download file.

[poochwilly]

I started with the 0.9 version, then heard about the x versions, originally I set up one folder and just installed the next version over top the previous version, guess I got a little to ahead of myself and tried to load up a saved activity. Walked a way for a bit yesterday then when I came back I jusy removed all signs of Open Rails,did a flush clean on my computer and set up another new folder,clean install of version x.2027 and all seems normal again.Glad to have people in this sim community step up and give help/advice.

Thanks again

Poochwilly

[seagoon]

I ......removed all signs of Open Rails,did a flush clean on my computer and set up another new folder,clean install of version x.2027 and all seems normal again.Glad to have people in this sim community step up and give help/advice.

Thanks again

No worries....nice to read that you have it sorted.

From now on, I suggest that you download and save each X file, unzip into its own folder, and initiate the EXE from that folder.
Keep a few previous X's, just in case you want to roll back or compare how something works in one or another versions.

[twpol]

Generally speaking, extracting a new version of Open Rails over the top of a previous version will work. However, it's not guaranteed to work and (should anything go wrong) the advice is to start with a clean/empty directory. (You can keep as many or a few versions of Open Rails in their own directories as you like.)

[neyland]

There are a few problems running the new MEP release with OR.

This version and the last X version.

Incomplete consists, dmu's incapable of more than 35mph.

Almost impossible to keep to timetables and freight schedules.

DMU power car engines cutting out and then gear selection becoming inoperable.

Is there a keystroke for re-starting engines in OR ? I couldn't see one in the F1 display.

Not restricted to MEP, but why do those artifacts, appear above some of the trees and foliage in OR.

They are not visible when running MSTS, anyway of removing them at all.

I am running a Geforce GTX 6600 @ 2gb.

[baldwin]

The new MEP was not made with ORTS in mind. Everything has been tuned to work perfectly in MSTS. The AI in OR des not work in the same way as MSTS either. However, the drivable DMUs do have some low power settings and strange throttle settings.

Incomplete consists can be caused by an error in the eng file. I think all of the incomplete consists involve the Class 105.

The artifacts are caused by a bleed-over of the texture from bottom to top and is a well known thing in MSTS and the correction method involves editing the ace file.

[seagoon]

The new MEP was not made with ORTS in mind. ...

That's a most pertinent point and should be at the top of every readme for any route or item authored for MSTS.

Until such time as OR has its own editing suite (and a set of rules for creating content solely for OR) then that statement should be considered as the Golden Rule and Commandment No. 1.

[muskokaandtahoe]

Do you just remove the first version and extract new version to folder and carry on playing?
Thanks Poochwilly

I always create a folder specific to each version I download -- V2019 for instance and I keep a couple dozen of those on hand. I have another folder I use for running OR that is tied to a desktop icon (in my case it's called Current Debug Version but the name doesn't matter). By replacing whatever is in my run folder I can change versions as needed and the Desktop Icon will always work.

Doesn't solve any issues w/ saved games but it does make changing versions pretty trivial.

[rdamurphy]

That's a good idea, actually. I usually just keep the latest on hand, and download any old ones I need. I don't spend as much time running OR - or MSTS - as I do in either GMAX or Visual Studio...

I've pretty much given up on the RE, I guess my route will never be finished...

I guess the pertinent point is simply that ORTS can't fix every mistake in MSTS. It may "work" in MSTS, but it may be unique to a particular model, route, or texture, and it simply won't work in OR without some change to the file. It's really not practical to change OR code to compensate for one item that may work in MSTS, but still has a fatal flaw in OR...

Robert

[neyland]

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.

[eric]

OR is designed to use MSTS content, but there's been never been a commitment that it would run exactly the same. The OR team created new physics models and rules, all of which has been fairly transparent to the user community if you pay attention.

One thing that ORTS doesn't appear to be doing is something Microsoft is notorious for -- fixing flaws in their code on the fly, or compensating for it elsewhere.

Their early GPS code was so bad that their mapping interface code would imitate better accuracy by forcing the "you are here" cursor to stay on a known roadway vector in the map, even if in fact you were off-road. It was quite humorous at times to see me driving on the highway when I was 500m in the middle of a field, or in a subdivision which had been build subsequent to the map database being published.

Using their web server, HTML code would execute even if mandatory end-tags were missing; IIS would make assumptions on where they thought the end tags should be auto-inserted at runtime.

Same thing with several generations of Visual Basic and their programming compilers. It's not until the last 5-10 years or so that they've enforced strict coding and started erroring pages/code which didn't have the proper syntax.

Things like that allowed for sloppy coding practices to continue, and it's why their software had such a bad reputation for never really being ready for prime time until the first Service Pack was released.


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.

[baldwin]

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.

ORTS is designed up to the release of version 1 to run MSTS content. It is not designed to accommodate MSTS models and code that have errors. Those errors within the MSTS content have to be fixed or the model discarded. Looking at your claim about the DMU sets, I agree that they do not work in ORTS, but that is because they have been made to perform in a particular fashion in MSTS and ORTS is not going to be modified for them to work, the eng files all have to be redone to work in ORTS. If you download an MSTS DMU set and install it to ORTS, it will run far faster than 35mph. Bottom line is if the eng file has not been hacked about, it will work in ORTS.

Bugs, find one and please report it. Without bug reports, it can only be assumed that everything is fine. Bugs do get prioritised so a fix may not be immediate.

As for knowing it all, not me.

[bprice]

I've pretty much given up on the RE, I guess my route will never be finished...Robert

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.