Installing a V4 Activity onto V5 (Dorset Coast)

[icornish]

Hi,

I searched the forum but couldn't find anything. I've downloaded and installed and upgraded to DC v5. I've done the 2 V5 activities, and felt like doing the Tangmere to Guildford (cos the track is at the bottom of my garden, and I've seen Tangmere many times go past). However, this is a V4 activity, and when I try to install it, it refuses, giving "This package requires a route called Dorset Coast Route v4, UID Dorset".

I have trainstore installed, and Dorset Coast v5 is unstored. Any thoughts?

Ian

[ralph0chadkirk]

It's because it's looking for a route called Dorset Coast v4, whereas your's is called Dorset coast V5

[icornish]

So how can I install/build this activity to work on Dorset Coast V5? Or is this a "design feature" of MSTS ?

The UID's are the same in both cases.

Ian

[ralph0chadkirk]

I suppose you could go into the Activity Editor and change the route - not sure how though

[gswindale]

It's more likely the Route Editor you'll need to go into.

I think you may get away with editing the .trk file only with notepad, but not 100% confident - if you do, take a backup first.

Which is the activity in question? I'll try and have a look this evening to see if I have the same problem.

[icornish]

It's file ID

BKDC6 - Tangmere to Guildford [16621 bytes] - BKDC6.zip File ID: 17287 Date: 18 Aug 2007 - 623 Downloads

, BKDC6 - Tangmere to Guildford

[gswindale]

OK,

I've tried and firstly after thinking DC5 was unstored got the message you describe. Checked in Train Store and DC5 was not unstored - I misread the screen and my copy (dorsetmod) was unstored instead.
Having then unstored 1 activity only in DC5, I tried again - this time I got the message

The installed track database for this route is 10762, the activity was built on version 9428. Continue?

As I've not yet read the readme and am unsure as to the stock requirements, I clicked no.

Therefore I'd suggest double checking that the route is definitely unstored in TrainStore.

[thenudehamster]

In most cases you can get away with installing an activity built on an earlier tdb version into a route with a later one, but you might run the risk of broken paths if the tdb was actually changed between the two version numbers. There's no easy way of knowing unfortunately. MSTS changes the version number every time the route is saved from the RE, even if the tdb was untouched - add a building, move a tree, Save, and the tdb version gets updated! The only way to be sure is to try it and see.

[ccsdc]

In most cases you can get away with installing an activity built on an earlier tdb version into a route with a later one, but you might run the risk of broken paths if the tdb was actually changed between the two version numbers. There's no easy way of knowing unfortunately. MSTS changes the version number every time the route is saved from the RE, even if the tdb was untouched - add a building, move a tree, Save, and the tdb version gets updated! The only way to be sure is to try it and see.

Just to confirm that from V3 to V4 to V5 there are no changes that affect the track layout of earlier versions, so you are quite safe to install V3 or V4 activities into the V5 route without getting any broken paths.

Dave