Mosk the Scribe - 17 November 2012 11:24 PM
Ok - checked the other post. I only have 10 scripts, not 11, in my categories/default/utilities/scripts/posemaster/utility folder - so looks like the update to 1.5 isn’t taking hold for some reason.
Note, I also have a cridgit folder under categories/default/scripts/cridgit (with posemaster/utility and posemaster/test as subdirectories, none of which have any files in them.
And I also have categories/default/unassigned/scripts/cridgit/posemaster/utility which has PoseAssetSerializer.dsb in it
It sounds like we might be getting closer to the issue. If you have PoseAssetSerializer.dsb in Categories/Default/Unassigned/Scripts/Cridgit/Posemaster/Utility then at least the file is on your system, but it sounds like the metadata didn’t get installed or has invalid references.
What doesn’t sound right is having a Cridgit folder under Categories/Default/Scripts/Cridgit. Does that mean the path is Categories/Default/Scripts/Cridgit/Cridgit? That’s certainly not correct, and Categories/Default/Scripts/Cridgit/PoseMaster should have 6 scripts in it, Categories/Default/Scripts/Cridgit/PoseMaster/Test should have 1 script, and Categories/Default/Scripts/Cridgit/PoseMaster/Utility should have the 11 scripts in it. It might be useful for you to check the file system to see where those scripts have ended up (what is in the My Library/Scripts/cridgit/PoseMaster folder on your hard drive?).
I’m almost sure the install must be going into the wrong location, which invalidates the metadata references so they won’t show up in Studio. If you try a PoseMaster reinstall, please give me a screenshot of the screen where you specify the install location? The scripts can’t simply be missing - they have to be going somewhere.
Mosk the Scribe - 17 November 2012 11:24 PM
And if I go under Products/P/Posemaster for DAZ Studio - I have 17 scripts there
If you can see the scripts in the PoseMaster product view, try running PoseMaster copy from there by double-clicking it. If it works, then we know the problem is in your Content Library references.