data auto_adapted showing up in Content Library

srieschsriesch Posts: 4,241
edited December 1969 in Daz Studio Discussion

When I create .duf scene subsets and save them into folders and map as DAZ Studio native content, I get a bunch of extra junk I don't want showing up in the Categories > Default > Unassigned. For example
Hexagon car2 > Data > auto_adapted > car2_23897 > geometry_a4b101...fb_6b69dfcc8a88

How do I avoid this? Do I need to do something other than just creating an empty folder and saving the duf into it and mapping it?

screenshot,_auto_adapted.png
700 x 237 - 51K

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,363
    edited December 1969

    I suspect your primary content directory is inside another folder selected as a content directory, which might be confusing DS. Please go to the Content Directory Manager (right-click on the Content Library pane's tab and pick it from the menu) and post a screenshot showing all of your content directories.

  • ReDaveReDave Posts: 815
    edited December 1969

    I had that in RC1 or 2, then it went away without any intervention on my part.

  • srieschsriesch Posts: 4,241
    edited December 1969

    I suspect your primary content directory is inside another folder selected as a content directory, which might be confusing DS. Please go to the Content Directory Manager (right-click on the Content Library pane's tab and pick it from the menu) and post a screenshot showing all of your content directories.

    Yep, thanks! I forgot I had the folder "custom objects" mapped. I removed the unneeded mappings to the subfolders in it, then deleted the data folders next to the duf folders, and it looks like with the exception of one duplicate content thumbnail things are working again.
  • srieschsriesch Posts: 4,241

    Does anybody remember the trick to clean up after this mistake without having to manually delete thousands of accidentally-added folders one at a time out of Unassigned?  (in 4.8 if it matters).

  • srieschsriesch Posts: 4,241

    It appears that exporting the database and mapped directories, erasing it, and restoring them (and possibly something else I did but forgot) did the trick, although I had a few hiccups along the way and some unexpected other events that I can't quite figure out what happened or what fixed them.

Sign In or Register to comment.