If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

If you download a new asset that requires dependencies you already have newer versions of, sometimes during the installation process it will open the newer version for editing, decide it doesn't need to install the older version, but then doesn't bother to close the edit. I normally just submit all edits.

1) You've had a crash and the route you were working on is open along with the temporary files.

You go in and revert or save the changes when loading the route up again (I can't remember the exact wording), and continue on where you left off.

2) You install stuff from a third-party via CDPs, for example, stuff from Jointed Rail or elsewhere including your own saved content.

In this instance, it's a fail-safe mechanism. Rather than just overwriting already installed content the assets remain open for edit for review. I wish there was an option for this, or a message that says when installing from content packs assets will remain open for edit if they are already installed. When installing content from CDPs, revert these assets since they are already installed. I keep the Open for Edit filter in view when installing stuff from CDPs and go back and revert the open for edit assets later.

For the leftovers from a crash, you can go back at a later date and remove the old temporary files - they show up as "new asset" but contain route parts, after you have saved the route or session and continued on. In this case, I always wait a day or two before I clean up to ensure that I don't delete something in haste, and by clean-up I mean delete these since they're long old - I always check the date too just to make sure.

...
2) You install stuff from a third-party via CDPs, for example, stuff from Jointed Rail or elsewhere including your own saved content.

In this instance, it's a fail-safe mechanism. Rather than just overwriting already installed content the assets remain open for edit for review. I wish there was an option for this, or a message that says when installing from content packs assets will remain open for edit if they are already installed. When installing content from CDPs, revert these assets since they are already installed. I keep the Open for Edit filter in view when installing stuff from CDPs and go back and revert the open for edit assets later.
...

It may also be possible, that a creator of an asset on a third party site is making a new version of an asset but is not using kuid2:x:y:1, that is, he is using the same kuid (e.g. sometimes Jointedrail; the problem is, the maximal number for an asset is kuid2:x:y:256, that is 256 versions). In this case the installed asset will be opened for edit too, but because the new installed asset is indeed the newer one, you have to commit the open asset and the new version of the asset is installed. It is sometimes very difficult to decide, if there is such a case.

It may also be possible, that a creator of an asset on a third party site is making a new version of an asset but is not using kuid2:x:y:1, that is, he is using the same kuid (e.g. sometimes Jointedrail; the problem is, the maximal number for an asset is kuid2:x:y:127, that is 128 versions). In this case the installed asset will be opened for edit too, but because the new installed asset is indeed the newer one, you have to commit the open asset and the new version of the asset is installed. It is sometimes very difficult to decide, if there is such a case.

Regards
Swordfish

Yes. I forgot about those cases and they do occur. Justin or one of the guys over at Jointed Rail will tell us to overwrite the assets if necessary.