I now have T:ANE. I've downloaded a bunch of possibly interesting freeware routes and sessions from DLS and I am now starting an ambitious (and possibly fruitless) effort to resolve missing and faulty dependencies in these assets. Let's take a very simple example I'm working with. I have the Robe River 2012 -v7 (no multiplayer) route, <kuid2:302602:100011:8> from alcaron. There are two missing assets in this particular route at this time -- <kuid2:124017:30014:2> and <kuid2:30501:1005:2>. 
I'll start with the most basic question(s) and drill down later if that's appropriate.
Is there any way to determine what a missing asset might be, even as broadly as its category? I don't see any way in Surveyor to find references to objects by kuid. Is there some way to locate object references in Surveyor so I might at least see where in the 3D world a missing asset was intended to live (which would at least give me a clue)?
On a more general note, are there any suggestions on how to proceed on a project like this, chasing down (and then possibly replacing) missing and faulty dependencies? The example I gave above is the simplest I'm facing. Several of the routes and sessions I've downloaded have a _lot_ of missing dependencies. And these routes and sessions were uploaded to DLS relatively recently. Am I wasting my time trying to resolve these issues, or is there some hope of my "fixing" these problems?
TIA!
--Gary
				
			I'll start with the most basic question(s) and drill down later if that's appropriate.
Is there any way to determine what a missing asset might be, even as broadly as its category? I don't see any way in Surveyor to find references to objects by kuid. Is there some way to locate object references in Surveyor so I might at least see where in the 3D world a missing asset was intended to live (which would at least give me a clue)?
On a more general note, are there any suggestions on how to proceed on a project like this, chasing down (and then possibly replacing) missing and faulty dependencies? The example I gave above is the simplest I'm facing. Several of the routes and sessions I've downloaded have a _lot_ of missing dependencies. And these routes and sessions were uploaded to DLS relatively recently. Am I wasting my time trying to resolve these issues, or is there some hope of my "fixing" these problems?
TIA!
--Gary
 
	 It has pointed me to _some_ of my missing dependencies, for which I am grateful. However, it has brought a disturbing issue to light. Some of the unknowns I have in my system are reported in the index as T:ANE SP1 (build 80349) builtins, but they are not in my build 84473 system (acquired recently from Steam). In one case (just as an example), the index says version 2 of an asset is a builtin, but my build only has version 1 installed. In many other cases, the assets are shown in the index as builtin but don't exist at all in my build and are not on DLS (presumably because they are built in). I'm starting to fear that as N3V releases patches they may be deleting builtins that they find to be incompatible with the new patch(es). Is that possible, or is there something else going on?
 It has pointed me to _some_ of my missing dependencies, for which I am grateful. However, it has brought a disturbing issue to light. Some of the unknowns I have in my system are reported in the index as T:ANE SP1 (build 80349) builtins, but they are not in my build 84473 system (acquired recently from Steam). In one case (just as an example), the index says version 2 of an asset is a builtin, but my build only has version 1 installed. In many other cases, the assets are shown in the index as builtin but don't exist at all in my build and are not on DLS (presumably because they are built in). I'm starting to fear that as N3V releases patches they may be deleting builtins that they find to be incompatible with the new patch(es). Is that possible, or is there something else going on?