none of my generation 4 base models/assets load successfully in DS 4.9
xyer0
Posts: 5,926
V4, A4, G4, S4, Reby Sky, M4, H4, F4 bases and morphs fail to load in DS 4.9 using either DIM or Daz Connect. When updating metadata in an attempt to rectify this, it shows (for all items that I bothered to check) "6 items failed." No problems with ANY Genesis 1, 2, or 3 models. Any suggestions?
Comments
K4 either.
Fourth generation figures cannot be installed with Connect. They should, and do for me, download and install with DIM and load in Studio (much slower than the Genesis though).
Thanks jestmart, I will uninstall them and start anew. Now, did you discover this by trial and error or was there an official communication about this?
It's to do with the way the ExP morph system works in all Generation 4 figures; the morph packs must be installed to the same runtime location as the base figure, then the activation script must be run (if you're using DIM this should happen automatically). Connect is completely incompatible with this, because it essentially installs each product into its own runtime, so the activation script can never find the proper data files. The only way now to use these figures and their morphs is to use DIM, or a manual install.
Thank you, SpottedKitty, for the hidden info as usual. I loaded them using Connect, and when I tried to fix it by loading them with DIM, it didn't work. I am currently making a list of every Generation 4 product that won't work so I can fix them en masse.
"Didn't work" how? Were you trying to load them from the Smart Content tab or Content Library? Remember that the Smart Content view doesn't show your installed content files, it shows a filtered and sorted view of a database of links to your installed files. These database links are not your content, and if you installed through DIM without uninstalling the Connect items first, the database will still have the links to the Connect files. Only the Poser Format and D|S Format views in the Content Library tab show the actual current state of your installed content files.
Yes ma'am, I was using the Content Library not Smart Content. As you said, I attempted an install through DIM without first uninstalling the Connect items. So, I am now going through my Content Library making a thorough list of those products that are in that state, and I will uninstall them all from both Connect and DIM before I reinstall with DIM.
On a similar topic, should I be seeing files marked CF in my Content Library? This did not happen until I did a Content Database Maintenance metadata update. All of them are marked with the ! yellow triangle; so, I know they are inoperative, but since I cannot remember ever actively loading a CF file (I thought they just worked in the background), can't I merely delete them from the Content Library?
Thanks for all your help as usual.
CF items must not be mass deleted just because they're CF. It stands for "Companion File" — and there are two different types. Some products are created in Poser format, with a D|S CF containing only D|S materials. Some are the other way round, created entirely in native D|S format with a Poser CF containing DSON import files and Poser-format materials. The second type is the one you don't need if you don't have Poser installed. The first type is where you do need both installers.
Note that if neither installer is labelled CF, then the two are full independent Poser and D|S installers; again, you only need the D|S one.
A related point I just remembered; do you have the filters in DIM set for the D|S version you're using? That way, you'll only see D|S files unless the product is Poser-only (but will work if loaded into a D|S scene).
Thanks for all the clarification. I just set the DIM filters too.
I have already mass deleted all of the Poser CF items, but at least I know what to do if the product won't load. Hugs and kisses to you, my dear!
FWIW, you shouldn't have any "won't load" problems if you happen to come across a CF you shouldn't have deleted, but you will be stuck with Poser-style materials. The effect of rendering these in D|S will vary from "looks a bit weird" to "why is this rendering white" depending on the exact circumstances.
Ahhh, thanks again, sage feline, for the clarity. You just saved me probably hours, if not days, of mute incomprehension.