Is it possible to put an alias of a control morph into the main body of Genesis?[solved]
DrunkMonkeyProductions
Posts: 1,152
If I create an alias of a P designated parameter in edit mode of the parameters tab, i can put it in any subnode, but unlike M designated parameters, i can't get the alias to move into the main body, via Property mover, or via manual editing of the Alias DSF.
Just a limitation of studio, or am i doing something wrong here?
SOLUTION
An ALIAS of a control morph or pose morph(P designation when in edit mode of the parameters tab) CANNOT have the same Name(not label) as the parent property, if being moved to the base node.
An ALIAS of a morph(M designation) does not have this restriction.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
You should've used Property Cloner and tick the option Create As Aliases.
I already know how to make the things, the problem is, getting the alias from the hip to the main body.
It works fine,via property mover, for morphs(M designation), but does not work for control morphs or pose controls(P designation).
Property Mover can only move the Properties that vendors or users created by using : Create New Property... (with icon P)... their Owners are Nodes rather than Morphs. Properties with icon M are Morphs (Modifier/Shape) with Owner: Morphs, they cannot be "moved" across Nodes with Property Mover. (ss1) Morphs can be only "cloned" rather than "moved"... so I really wonder how you made them moved by using Property Mover.
On the contrary, "Control property" as well as Pose Controls (both with P marks), again, their Owners are Node, they just can be simply "moved" via Property Mover (as long as there's no property with same Node Name in the target Node). (ss 2 ~ 4)
I wonder why it didn't work for you ~~
Edit: if as you said, from Hip to root node, I don't have any movable or cloneable properties on Hip node (G8/G9). So I wonder what you were referring to... If they're Transforms properties, nope... they can be neither moved nor cloned. If they're the ones you moved from other Nodes, you can move them to any other Nodes by using Property Mover, or clone them with Aliases by using Property Cloner.
The reason for the confusion, you seem to keep missing i'm working with ALIAS parameters.
You don't have anything in the hip node, because you haven't created a new ALIAS and put it there, unlike i did.
You did, inadvertantly, solve my problem though.
An Alias(A designation parameter) cannot have the same Name(not label) as a P designation parameter in the root node.
By changing the Name(not label) of the ALIAS, i was able to put it back in the root node, create a new DSF and it works as intended.
Thanks.
A couple minor corrections though.
As i understand it, P is "Pose parameter", M is "Morph Parameter" and A is "Alias parameter".
The primary differnece, P and A type do not include the 'morph" line of code in the file.
Functionally, an M can be a morph, and/or a pose/control, depending on whether it contains the rest of the morph code, such as vertex data.
The designations can be changed by editing the DSF, though they may not function properly on subsequent loads.
P to M and A to P, don't appear to cause problems, but M to P and A to M do. at least in my testing.
Create New Property, can create P, M or A designated parameters
This is determined by the node selected, and whether the "Create Empty Morph" box is checked or not.
If the root node is selected, P or M are created, with M being created by checking the box for "Create empty morph".
If a sub-node, such as Hip, is selected, P or A are created, with A being created by checking the box for "Create Empty Morph".
P and M type will load from a dsf created for them, even if they don't do anything, but A type won't, if there's no association with a parent parameter..
In regards to Presentation Type(modifier, modifier/shape, etc) this has no real correlation to the P, M or A designation, nor does changing it change the designation.
Basically, it's upto the PA/creator what type is used, if anything, as None is an option by deafult
As a couple of examples, G8F's Chest Scale has a P designation, but a type of Modifier/shape and Breast Control's Center shift is M type with Modifier/Pose.
It's also possible to make a custom type, by ediing the "type" under "presentation" in the DSF. Though, this doesn't appear to carry over to the drop down for other parameters.
A is Alias and M is Morph, P is anything else - not just a pose. Names must be disctinct for each proeprty on a given element, not just the root node.
Right ~ I didn't thought of that you wanted to Move an Alias back to Root Node... Usually, all control or morph properties are 1stly created on Root Node before cloning Alias on other Nodes, though the workflow can be done reversely...
But yes, editable Node Names of the properties that have same Owner must be distinct, e.g. in your case, A and P have the same Owner... while if with different Owner, Node Names can be identical, e.g. M and P(or A, R).
P for "Property" (General Purpose), and R for "Rigging", I just know these 4 types.
Content Type of Properties are mainly related to Saving Preset filters and some DS built-in functions... so reasonably and correctly setting Content Type really matters, for instance:
1) Saving Shaping Preset dialogue only lists properties with Modifier/Shape. Restore / Zero figure's Shape only deals with the properties with Modifier/Shape.
2) Saving Pose Preset dialogue only lists properties with Modifier/Pose. Restore / Zero figure's Pose only deals with the properties with Modifier/Pose.
3) Clear Generated Morphs only clear the morph properties with the designated setting of Modifiers, yada yada ~
As for the example you mentioned. Chest Scale is a property ERC Freezed with Scales of some sub-Nodes of the figure... rather than a real Morph, so P just works fine.
Center Shift has delta vertices embedded, so it has to be M first of all, otherwise Morph Loader Pro cannot import OBJ to it or update it. Since Breast Controls deal with the breast shapes for posed figures, when Restoring / Zeroing poses, the stacked "morphs" need to be restored / zeroed, so the Content Type of those properties have to be Modifier/Pose.
You can only modify Type in DSF files according to the values in enum list of Content Type of a property. They're built in DS application and cannot be customized (create new...)
Yeah, that was a brain fart on my part.
Best i've come up with is that P is either Parameter, or Property, but i have yet to find anything difinitive in the wiki.
Wouldn't happen to have a link?
As for Names(not labels), that's not true for alias's(A type), based on M type.
Hence why i asked my original question, as i was able to move Alias's, as long as they were from M type, but P type wouldn't move.
I was using 4.22.0.16 and 4.23.1.36(beta) for testing this.