I wonder whether someone can help me with this please....
I have a large (enough) route which was built with TS2004&6
and in TS2010 it has many 'errors' (..surprise!).
Indeed, the updates showed (originally) some 5500+
'updates'.
I have been trying to download these but as I'm sure you'll
all realise, they have to be done (in TS2010), one at a time.
(..unbelievable)! Currently it is 'down' to ~4500.
And it is taking sooooooo long, I am desperately trying to
find a better solution to recovering this route.
NB: I definitely do not want to have to start all over again,
ie: in TS2012.
This all came about due to the loss of a HDD which,
unfortunatley, also contained the backups.
(Please don't go on at me about offline etc, I am a
programmer and fully understand the ramifications - it just
wasn't feasible at the time. Things have changed now & I
have the means to (realistically) back up offline...... now)!
NB: I have just recently bought TS2012 & it has been
suggested to me I should import the 'dud' route CDP into
TS2012 as the updates are 'automatic' (ie: don't have to be
done one-at-a-time).
I have imported the (faulty) CDP into TS2012 .. BUT ....
- I can't even edit the route .. it doesn't even appear in
the routes display
- there are no updates showing at all, presumably because it
appears to have not imported the route (...because it's
faulty..... ...Gee thanks Auran/N3V!
.So .. is there a better way to do all this please?
Hopefully since some years have elapsed since I, errrr...
gave up on this, some solutions have emerged on how best to
overcome the issues.
Some possibilities have occurred to me...
- I can write a program (see Note) to do modifications to all the
config.txt files where the 'complaint' is that the relative item
is no longer permitted under TS2010.
Clearly this won't help anything that needs to be there and isn't
there. Unless a blank entry will suffice in that case - and I'd
certainly go for that as a 1st 'try'.
If this would solve enough issues, I would read in a text file
containing say.. (1 item per line, each item separated by a space).
- code to indicate the 'type' of config.txt that is relevant
(or other means to identify the correct config.txt to modify).
eg: 'scenery'
- code to indicate a delete or insert eg: 'D' or 'I'
- text or keyword - to either search for - or insert...
as appropriate.
Then, the info in such a file could be applied to all config.txt
files located in a given path, since they're all just plain text.
ie: easy to implement.
Such a list could obviously be processed over & over and even
extended over time, as new issues became ... 'obvious'.
The idea is .. hopefully, that the bulk of issues could be
resolved this way, getting the problem down to something
manageable, manually.
Obviously I don't expect it to resolve *everything*.
But there are many common errors appearing - that ought to be
resolvable with this sort of approach.
Or....
- I seem to recall there was a program which would replace all
faulty or missing items with a 'placeholder' .. the idea being that,
on editing the route (under TS2010), it would be apparent what
needed to be replaced and thus say, a 'missing' bridge could be
replaced with a different, valid one. I seem to recall that a large
red exclamation mark (!) was used to identify where something
had to be fixed.
Possibly though, this program was for TS2004 ... (can't remember).
Does anyone know of this .. or similar please? And where it is, now.
At least that way, it would be preferable to having to just delete
all faulty content - and then try & work out (everywhere) what needed
to be fixed. Deleting everything faulty/missing isn't really a
feasible/acceptable ...solution.
Many Thanks.
Barry
[Bazza99 ....NB: UTC+10]
Note: re: writing a program...
Please be aware I have no knowledge of the structure of a CDP -
and can thus only operate on (all) config.txt files.
(ie: prior to the route being packed into a CDP).
