[CrisGer]

I ran OR fine a day ago.

With no changes i tried running the same route again, got this error:

Quote

External component has thrown an exception

after this error i was unable to load or run the route in either OR or MSTS. tried removing all activities paths and services...but still wouold not run. Route was dead for good.

UPDATE:

This was the result of having a consist with an OR only engine in it for the MSTS route while trying to run the route in MSTS> My bad.

Glad i learned about that.

[CrisGer]

My error resulted from my having a consist with OR onlly engine it it for this route, so i appolgize for my post above also edited ;)

just have to be sure to keep OR conssits out of working MSTS routes.

[longiron]

CrisGer, on 31 May 2010 - 10:00 AM, said:

after this error i was unable to load or run the route in either OR or MSTS. tried removing all activities paths and services...but still wouold not run. Route was dead for good.

Had to re install route completely plus substitution trees and activities. Tried again MSTS ran fine. OR threw the same ERROR and the new re installed route was dead again.

CrisGer,
Open Rails makes NO and I mean NO changes to your MSTS installation. All it does is "read" your ACT, CON, ENG, WAG and other files. Running OR will not convert a working MSTS installation into a "dead" one.
chrisvw

[copperpen]

Crisger, if you try to run Silverton in MSTS with Bazza's OR equipment, MSTS will toss the route out. You cannot run the route with that engine in an activity outside of Open rails.

[CrisGer]

ah ha
that explains it

yes i did have a consist in the folder made to run OR

ok, i will edit my post, and appolgize. I appreciate the info and help learning all of this.

[captain_bazza]

The new OR loco version K35 #501 will only run on the Silverton, or any narrow gauge route, in OR. You should include OR in the Activity name so you don't run it in MSTS.

The older version of the same OR test loco is K27 454 and it runs in OR in versions 101 thru 114 only.

The problem is not with the shape file, it's an ENG problem....some small glitch in the file that was basically OK in MSTS (I used same ENG as for MSTS) but the later versions of OR 115+ will not run.

I hope to have a K35 shape update available later today.

Cheers Bazza

[CrisGer]

OK thank you Captain. I restored my Silverton route, it sure helps to know to be very very very careful about the consists that are loaded when you start up OR and MSTS. I just have gotten very fond of your engines and feel..well.... wrong, when i run the Silverton testing or in MSTS without them. I just need that detail you put in to feel right about things.... so thank you and thanks for the update.

[captain_bazza]

Thanks, that's why the feedback is so important when trying to find the right protocols.

Cheers Bazza

[copperpen]

Just to make it quite clear to anyone reading this thread, any of Bazza's OR locos must be removed from the MSTS trainset folder before running MSTS. You must also remove the activity and consist that use the engine/s. One way round this would be to create a dedicated mini install just for OR and name it as such. This will keep OR high poly stuff out of the MSTS trainset.

[CrisGer]

That is exactly what i plan to do today, make a exclusive OR install, will help keep the testing that i do. I will test all the default routes first.