multiple machines/kuid management

[justinroth]

I'm wondering if anyone else who uses multiple machines for Trainz has a good system to avoid kuid conflicts? In the past I've had issues with assets being overwritten and of course, I didn't have the original .cdp to restore the asset. I wish trainz gave a warning BEFORE overwriting assets.

 

[deneban]

Trainz doesn't always give a warning because it saves each incremental asset change to the the userdata/backups folder. You can vary their retention time in Trainz Settings dev tab. Also you can make your separate Trainz installations assign different ranges of asset numbers by using the TrainzUtil setnextcontentid command.

 

[Forester1]

You may also be able to right-click the new asset and select "List Asset Versions" The earlier version should be listed and you can re-download it, then export it to CDP for safekeeping if you want to hold onto it.

 

[stagecoach]

The asset is not overwritten, it just has a newer version added which Trainz always reads the newest version. Delete the newer version and the older one becomes the newest version installed.

 

[deneban]

You may also be able to right-click the new asset and select "List Asset Versions" The earlier version should be listed and you can re-download it, then export it to CDP for safekeeping if you want to hol donto it.

The asset is not overwritten, it just has a newer version added which Trainz always reads the newest version. Delete the newer version and the older one becomes the newest version installed.

Gentlemen he is referring to the identical local asset number being generated on separate installations ("machines") for distinct assets: ("I'm wondering if anyone else who uses multiple machines for Trainz has a good system to avoid kuid conflicts?")