Relinking objects

So I have a number of items that are assembled from objects I've created. Except I've reinstalled since I first did it, so the file doesn't know where the objects are any more and I end up with a bunch of featureless blocks.
How do I update where these links are pointing?
Comments
The first way would be to use the Locate option when it throws the "cannot locate content" error.
The next way would be to edit the Duf or cr2, depending on format being used, updating any references to the previous locations with the new ones, correcting for mesh files and texture files.
I personally use Notepad++ for this as i'm able to change multiple references in the file, as well as multiple files at once. It also doesn't screw up the formatting like wordpad or notepad can.
If it's just a mapping problem, you might be able to get away with remapping the directories you use in content directory manager.
Is there a way to use Locate if I haven't been prompted?
This is geometry, not surfaces, unfortunately.
Those objects where probably converted and their geometry (and other info) placed in the "auto_adapted" folder inside the "data" folder of the library you saved to.
It looks like garble when I open it.
Is there seriously not a way to change object references in engine? This means just about all my stuff is going to break any time I reinstall.
Not if you remeber to back-up the auto_adapted files or better yet make them into Studio native props yourself.
Hey Will,
If you run into this again (or anyone else...), as described above, it looks like the .../data/auto_adapted/... folders are a copy/cache sort of thing that DS does to 'convert' non-DS content to a DS-happy duf/dsf-like format. I see them all over the place in my content folders so they may get created in any of the Daz content folders you've got 'mounted' when working on a project.
So the trick seems to be either: disable such caching/conversion (?), edit those references in the scenefiles (as mentioned above - thanks!), or put all those caches in a common place, as I've take to doing. Probably gets rather large over time, but at least you can 'take it with you...' - if you know what to take...
I've taken to creating and 'mounting' a generally empty 'local' DS content space (I call mine 'DSCache'), using the DS content manager to move it 'to top' of the DS content folders list, and am hoping that all 'data/auto_adapted' stuff is put in the first/top folder found by DS. If I find other instances of these .../data/auto_adapted caches scattered about my content folder's 'data' directories, I now manually move them *all* to this folder's .../DSCache/data/ folder and restart the DS session (refresh) after moving these folders around.
Seems to be working so-far, but yeah, if you share runtimes between machines, or mount/unmount your content/runtimes a lot for project-specific reasons, these invisible (to end-users) .../data/auto_adapted folders may seemingly disappear randomly, when in-fact, it seems the randomness is actually *which* content folder a cached item is *created* in. I'm hoping it's the first-one-found (top of the list), and putting all of my caches there, and keeping that folder on the top of my DS content library lists. A good side-effect, is, if you 'share' this 'common' DS content folder (via network sharing, etc.), and have it 'on top' on all of your 'client' machines DS content library lists as well, and reliably put all caches in it from all participating machines, my arbitrary scene-files all seem to be able to find what they're looking for on all machines - even if we can't 'help' find them when that silly missing content message appears!
And I know where to store and look-for such cache files now.
Does anyone know if there's a flag/checkbox that disables this caching and forces the item and dependencies to actually be available in your current content folders when you open a scenefile - giving you a warning when it's not found? I don't like depending on such caches, as I can see a scene failing to load a couple years down-the-line because that cachefile has long-since been deleted/moved, or the scenefile is opened on a completely different or rebuilt machine... urg.
clear as mud? Hope this helps,
--ms
(edited to reword/clarify)
Oso, did you by any chance find an easier work around for your problem. I'm experiencing it at the moment. I can't make head or tail with above.
Edited to fix quote