Hi all! I used V4.2 with Morphs++ for years.Now if i start new project,and load V4.2 with Base and Morphs++,some Morphs++ dont even show in the menu,such as hands(grasp,spread etc).. i dont know what to do,because i reinstalled and nothing seems to work..Any suggestions? Also have no idea what caused this trouble.. Any V4.2 i have saved with those morphs is working,but if i want them to sue on new V4.2 chararcter,they wont load,or only some of them.. thanks for possible help J.

Did you try reinitializing V4? You initialize the V4 figure by browsing to the 'folder you installed your stuff'/runtime/libraries/!DAZ and Click on both: (in Windows; there are Mac scripts in the same directory)

DzCreateExPFiles-V4.bat

DzCreateExPFiles-V4V3.bat

If this doesn't solve it, it's possible that there is a duplicate Victoria4.2.cr2 or /runtime/libraries/!DAZ folder somewhere in your Poser library..

**Well, since this is an ever recurring theme:

Is anybody able to determine what exactly this "Initialization Rite" does?

Any of the batch files only call a program called "DzCreateExPFiles.exe" with the parameter of the figure attached, e.g. DzCreateExPFiles "Victoria 4" "V4"

But what sort of "Voodoo" does it do? I mean, Poser has no sort of registry for library content, so maybe the only thing that this .exe does is copy the DAZ files to the correct location??**

Trying to solve this user's problem:

Since Generation4 figures came out I've updated Poser to a couple of new versions. Because V4 (now: SASHA-16) is still my main figure I, theretically, would have to "initialize" her for every new version of Poser.

I didn't do that.

Instead I just copied the DAZ folders from "GeometriesDAZPeople" and "Libraries!DAZ" to the basic runtime of the new Poser installation (that is: the runtime that is inside the Poser program folder - let's call it the "Native Runtime"), and all DAZ figures worked flawlessly in the new version.

The only thing I made sure of is that none of the basic DAZ Generation 4 are present as duplicates in any of my external runtimes. This makes troubleshooting a lot easier because if Poser can't find V4 files the problem must be within the Poser "Native Runtime", unvariably.

So before you continue, search all your external runtimes for these folders:

• "RuntimeGeometriesDAZPeople"
• "RuntimeLibraries!DAZ" and ->move the content of these folders to the "Native Runtime": "{Your drive}:Program FilesSmith MicroPoser {yourVersion}Runtime*.*"

This "Native Runtime" is the first where Poser looks when searching for content! Only if it isn't in this one, it will continue searching in the other runtimes. And the more files are scattered over various runtimes the more prabable it becomes that Poser gets confused, and the problems start. (That's also the reason why Python scripts should always go into the Python folder of the "Native RUntime"; if you want them to be added to the "Scripts" menue this is mandatory anyway because otherwise they won't show up.)

My assumption: The basic DAZ V4 as it came from DAZ uses a hell of a lot of scripting to reload code which reloads code which again reloads code until the figure is completed. Now imagine some code files aren't exactly where Poser is looking for it? YEP, Poser won't be able to find it and thus some morphs are missing or not working because of missing morph data.

QUOTE lelek240:

** Any V4.2 i have saved with those morphs is working,but if i want them to sue on new V4.2 chararcter,they wont load,[...]**

That's the logical consequence: Once the morphs were loaded OK by the scripts, they become part of the .cr2 file and will continue to work. Each "new" V4 character you try to create will again try to call the scripts, with the results as decscribed above.

Karina

As I understand it, the DzCreateExPFiles.exe reads the exp files for the installed morphs, and creates pose files that create the morph channels for the morphs in the figure when it is loaded. The cr2 has readscript lines that load these pose files, which reside in the /runtime/libraries/!DAZ directory...

Thank you WandW,

that's about what I expected. Now I only need to find out what those people were smoking when they devised these installation routines... (and why the Dickens this caricature of a "forum software" did eat the backslashes from the file paths in my previous post)

K

I believe it's because Poser never used to be able to dynamically load morphs into a .cr2, it needed a channel to inject them into. V4 and M4 used the .bat files to insert these channels, but they only inserted the channels for the morph sets you had, which is why you have to reinitialise them every time you added a new morph set. Example, you owned Morphs++ and initialised them. Later you got, say, the creature creator morphs, those channels needed to be added, so you had to reinitialise. A pain, but there you have it, that's why.

As for the disappearing backslashes, you\ can\ insert\ them\ by doing a double backslash where you want a backslash to be.

Dang it!\ But it gets swallowed when you edit your post\ so you must add those \ double backslashes \ manually again
I really hope I have my \Kalashnikov\ with me the day I meet the guy who had this \absolutely brilliant idea\.

You're right about the creation of channels:

Until PP2014 Poser couldn't create valueParms "on the fly" in a ready loaded figure. It had to be done while the inital figure is loaded: Load geometry, load body parts, load channel groups, create valueParm and targetGeom channels, load data for these, assemble the final figure.

That's also the way the SASHA-16 Setup works: A script preloads the geometry and some basic channels, and then, depending on the "elements" you click, the figure is built .

It's like building a LEGO figure, brick by brick. But once you've assembled the figure it's almost impossible to add more bricks right in the middle of the figure without breaking it.

However, in PP2014 I can already create "targetGeom" injections to be added anytime. There's also limited support for "valueParm" creation, though only via a Python script. What's still missing is full control over the creation of both channel types in both BODY and body parts. Then we could finally do away with all those cumbersome methods: Take a bare base figure, and inject whatever morphs you need, later, anytime.

We're almost there. Almost!

K

Pardon for late answer, i will check it out ASAP, i m too busy now.. hope tomorrow i get enough time! thanks for help now

Nevermind, just let us know what worked for you. -K-