Atomic Systems

I can't mention the source, but I have recently purchased the Class 82 (AL2) electric loco.

It has an aliased Class 86 cab (from the WCMLN Class 86, not the RSC Class86Pack))

I have worked out that I can insert the Class 82 loco into a scenario on any route by checking, in the editor, both the developer > Class 82 boxes on the right hand flyout, PLUS the Keithmross > WCMLN > > Class86 boxes, so that both assets are enabled (it doesn't work without the Class 86 being enabled, which I understand)

HOWEVER I can only get the Class 82 to work with Quick Drive on the WCMLN. I understand why it is working on that route . . . but is there a way I can get it to work on other eligible routes (e.g. ECML South, Edinburgh to Glasgow, or GEML) ? ?

BTW, I have established by trial and error that it is nothing to do with the <ValidBuildandDriveRoutes> tag at the bottom of the QD .bin files. In fact I'm not sure these tags are even necessary at the moment as I have seen a lot of developer-created QD .bin files where these tags are not completed.

I realize that I could probably copy over all the cab-related files from the Class 86 into the Class 82 folder structure, and edit all the paths in the Class 82 loco .bin files to point to the new location. But I can see spending a lifetime getting that all set up correctly, and hope there's a better and easier way of making this work!

Can anyone point me in the right direction here? Thanks.

To (partly) answer my own question, I have gone ahead and imported the relevant files from the WCMLN Class 86, and edited the Class 82 .bin files to point to them internally. So the Class 82 is now totally "self sufficient" and Quick Drives work fine on any routes.

However, I still haven't answered the original question, which could apply to many other situations . . . if a loco relies on any form of aliasing pointing at another asset (e.g. a cab, sounds, etc), how can it be Quick Drive enabled on other routes?

Chris

chrisonline wrote: However, I still haven't answered the original question, which could apply to many other situations . . . if a loco relies on any form of aliasing pointing at another asset (e.g. a cab, sounds, etc), how can it be Quick Drive enabled on other routes?

I haven't tried this, but I wonder if you enable the route for editing, and set the scenery browser filter to include the Keithmross > WCMLN > > Class86 asset. I suspect that the QD scenario will pre load the route's scenery filter set which may enable the assets you need by default.

wacampbell wrote:

chrisonline wrote: However, I still haven't answered the original question, which could apply to many other situations . . . if a loco relies on any form of aliasing pointing at another asset (e.g. a cab, sounds, etc), how can it be Quick Drive enabled on other routes?

I haven't tried this, but I wonder if you enable the route for editing, and set the scenery browser filter to include the Keithmross > WCMLN > > Class86 asset. I suspect that the QD scenario will pre load the route's scenery filter set which may enable the assets you need by default.

Wayne, I assume that may work with a full QD Scenario, but I am just creating Quick Drive Consists (light engine or engine + fragment) to select the loco and then select a route. Not sure how there is an editor in play at that stage in which to enable the assets . . . if I understand you correctly.

Chris