Overlapping KUID's - Suggestions?

[BrianPacos]

Looking for anyone that has a creative suggestion to the really dumb problem I alone created for myself...

A while ago, I lost all of my Trainz 22 content (thank to Avast Cleanup doing too good of a job and deleting all my TS22 game content). I recently started working from a blank slate and began creating new content, and so far it's been just fine, though I am missing a huge library of content I previously had.

I recently was able to get an old laptop with Trainz 19 running again so I basically have new access to a "snapshot" of what my content library pre-2020 when I built my PC (the one where the content got erased). HERE's the problem: I want to start migrating content from the old game into my current one, but there's quite a bit of overlap with my own KUID's now as a result of not having access to my previous content and therefore not knowing which KUID numbers to avoid. (Full disclosure, I did predict this could happen but as far as I knew it didn't matter since the old content was, at least in my mind, gone). Is there any way anyone can think of where I can for example, bring in the content with the overlapped KUID's? For example, I want to bring in a route to TS22 on my PC that has a lot of my former content in it, it was hard to run on my laptop (detailed, etc.), and a few dozen of the dependencies share a KUID with newer content in my present version of Trainz. I obviously don't want to overwrite the new content because I'll lose THAT content but I can't bring the old route in wholesale with all its dependencies. The only thing I can thin k of is just start manually overwriting KUID's in whatever config files I need to, and then bringing in old content with new unique KUID's (import content from a folder instead of as a CDP) but I can see that taking forever, and then there's no guarantee that I'm not creating more overlap in the future.

Kicking myself because I created this mess for myself and at the time I even considered creating a new account in the event of this happening so the numbers wouldn't match, and then just didn't. If any creative minds out there have either experienced this (for your sake I hope not!) or if anyone with a problem-solving mind wants to weigh in with suggestions, I'm open to hearing/trying anything!

 

[stagecoach]

You could try and import the asset which should remain open for edit. You could then clone the asset while open for edit in CM. Delete the imported asset so as not to overwrite the existing kuid and then submit the cloned asset which should give you a new kuid.

 

[BrianPacos]

You could try and import the asset which should remain open for edit. You could then clone the asset while open for edit in CM. Delete the imported asset so as not to overwrite the existing kuid and then submit the cloned asset which should give you a new kuid.

I do like that solution, if I have to make all new content then that's what I'll end up doing. The bigger issue is changing the kuids around in their dependent assets (routes, etc.), any ideas for that? Or am I just gonna have to bite the bullet and do all of that manually?

 

[JCitron]

Yeah, Stagecoach's method is one that will work. It's a pain but it's the only way.

 

[stagecoach]

Use a spreadsheet and in TRS19 CM select all your content and copy and paste it into the spreadsheet. Then do the same for TRS22 in the next column. Sort each column and check for duplicates. Clone the duplicate assets from TRS22 leaving TRS19 with all the original assets. If you have created any routes in TRS22 with the latest duplicate assets they will need to be obsoleted by the clone. Open any routes and resave so the cloned asset enters the config file. Remove the obsolete from the cloned assets and submit.
This should have any routes in TRS22 with the new cloned assets and allow you to import your TRS19 assets without duplicates.

 

[rwk]

I have that problem when importing from previous versions if the version I'm using already has a kuid that is the same as one I'm trying to import. I save the existing asset as a CDP then delete it, import the other asset and clone it, delete the old asset and then import the other asset back. It's a pain in the but but it works.