V4.2 with morphs++ does not work properly
Hi everone,
maybe somebody can help me, solving the following issue. I am using Poser 11 Pro. After injecting the morph++ to Victoria 4.2 things do not work as they should (or as I think they should - I am quite a newbie):
- When injecting morphs for figures, all head morphs work , but
- most the body morphs do not work (although some do I am referring to ones that are supposed to work with V4.2 / morph++)
- None of the morphs in the library at Pose: Poser11/Daz's Victoria 4/Morph Injections/ does seem to do anything (although I do not know, how they are supposed to work) at the same time, I do find some morphs in the parameter tabs for the various body parts.
It took me hours of trying, without getting that fixed. Any ideas what to do?
Cheers Holger

Comments
Hi, Holger. Welcome to the forums.
In Poser, when you load a figure such as Victoria 4, only the base figure loads. If you wish to use any of the morph packages that you may have, including the base morphs that come with the figure as well as Morphs++, those morph packages have to be loaded manually into the figure. Make sure you have the figure (V4) selected when you load the morphs. It is also important to understand that the Poser content library will not only show the injection files used to load the entire morph package (such as Morphs++), but also will show the individual morphs contained within that package which can be loaded individually if you wish. If you want to load the entire package, you can scroll down in the content library pane under Pose - DAZ's Victoria 4 - Morph Injections, and you should see the list of entire morph packages you have for V4. Those are what you want to inject to have access to everything. (see attached screenshot) Double clicking on Morphs++ with Victoria 4 selected in the viewport should load the package and when you expand Morphs++ in the parameters pane, you should see the spinners for applying the morphs for various body parts. Note that some of the morphs only show if the correct V4 body part is selected in the viewport, i.e. the head.
There may be times when you might wish to only inject specific morphs from a package, but most of the time I simply load the entire package and then I can access any ones I want to use from the parameters pane below.
Hi SixDs,
thank your for your response. But that does not help with my problem. The basics that you describe are clear, but my problem ist beyond hat:
As i wrote:
" After injecting the morph++ to Victoria 4.2 things do not work as they should (or as I think they should - I am quite a newbie):
- When injecting morphs for figures, all head morphs work , but
- most the body morphs do not work (although some do I am referring to ones that are supposed to work with V4.2 / morph++)"
So´, if I do not misunderstand anything I have done everything that is required: What I do see, is the parameters in the parameter pane, when clicking on a respective body part. But when applying a (full) body injection they do not work for some of the figures, while other morphs work (all meant to be used with morph++). At the same time all head morphs work when being injected. It is a bit like there ist some kind of partial missconfiguration.
Where and how did you install V4.2?
"most the body morphs do not work"
Can you give a specific example of one that does not work?
Edit: in re-reading your response, I get the feeling that we have had a breakdown in communications here. Your original post seemed to indicate that you were having difficulty in getting Morphs++ to work correctly. In other words, that some of the Morphs++ morph dials weren't working correctly. Now, I'm not so certain that that is what you are talking about. I'm beginning to think that Morphs++ is working correctly, but that you are trying to load a character morph that relies on Morphs++, and it is that character morph that you cannot get to work. Is that right?
If that is the case, it is not V4 or Morphs++ that are the issue, but the character morph. Can you tell us which one it is? The more information you provide us, the more likely it is that we can help.
I am also having the same exact issue described above. Did anyone get it resolved?