Curly Top Updo Hair Texture Expansion not showing up in Daz
LaPartita
Posts: 414
Curly Top Updo Hair for Genesis 9 works just fine, but no matter what I do I can't seem to get the expansion pack to install correctly. According to the DIM, the expansion pack is installed, but when I go into Daz Studio I can't find it. Has anyone else had this issue and/or know how to solve it?
Post edited by LaPartita on

Comments
I tried to install it and looking at DIM log, it's unable to find the various files it has to install but for some reason, the installation is deemed succesfull
What I don't understand is after installing the product manually and importing its metadata, as far as I can see, everything works fine.
A temporary fix:
1. Extract 'IM00087388-01_CurlyTopUpdoHairTextureExpansion.zip' yourself (outside of the DIM folder)
2. Copy all the content of the 'IM00087388-01_CurlyTopUpdoHairTextureExpansion/Content/' folder (you should have a People and a Runtime folders selected) into a library (some advices about which library to chose below).
Now, you should find the files to load the various presets in '/People/Genesis 9/Hair/Daz Originals/OOT Curly Top Updo/MATS' inside the chosen library.
About which library to use, I suggest avoiding using the library managed by DIM, in case it cause problem later and the safest bet seems to create a library just for the expansion, one you'll be able to easily remove after a proper resolution to this problem will be provided by Daz.
If you're using Smart Content, you will have to do the following step to get access to it:
With your Content Library active, right click on the tab and select Content DB Maintenance:
A window will open, select Re-import Metadata:
In the new window, unselect everything (the goal is to only import one product metadata, because it's faster this way) and search for the extension (easiest way to find it is scrolling down until you see it's product ID: 87388), then select the extension. You should have something like that:
Click accept and after a couple of seconds, you should now be able to access the extension through Smart Content too:
For a more definitive fix, you'll have to open a ticket (I'll do it myself too).
This was amazing; thank you so much!