Loading...
> >

Parent in place doesn't work (object still moves).

FalcoFalco Posts: 241
in Technical Help (nuts n bolts)

I have a figure that is posed in a scene and it has translation and rotations on the root node.  When I take a static prop and move it into the position I want all is good.  However if I then parent it to that root node or any joint under it, it moves in the scene to a new location.  If I check "parent in place" while parenting, it moves to a new location that is different from the default parent action but still wrong.  If I parent the static object to a figure without any translations it stays in position.

Why is parent in place not working how I expect it should? I want to parent objects to objects or figures and have them stay in the same position in world space.  

Comments

  • FalcoFalco Posts: 241

    To clarify I've tried parenting from the right click menu and choosing the parent with "parent in place" checked, and also tried turning on parent in place in the scene options and drag/dropping to parent but neither works.  

  • Richard HaseltineRichard Haseltine Posts: 102,669

    Could you give some more exact steps? I just tried with Genesis 8 female and a sphere promitive in DS 4.11.0.383 and could not get any unexpected results by translating the figure, by the figure node or by the hip, and parenting the sphere, to the figure node or the hand.

  • FalcoFalco Posts: 241

    Ah sorry, just ran a few tests, to clarify it seems to be on objects imported into the scene from outside programs.  I did your test with a primitive and it worked fine.  But when I imported in an obj that was created in 3ds Max and was positioned to match the figure, thats the one that gets affected by the figure translations/rotations.  Basically my workflow is I pose the character, export it to Max as a reference, place props where I want them in relation to the figure, and export them as obj.  Then I import them into Daz and they are exactly where I want them, but if I then parent them to the figure thats when they get messed up.

  • JD_MortalJD_Mortal Posts: 760
    edited September 2019

    Are you parenting the imported object to the model, or the model to the imported object? (Honestly, it shouldn't make a diference, but Daz haz many quirks like this.)

    I think the issue is that "parent in place", loves "Daz x,x,x translations", and only sort-of likes non-native objects x,x,x translations.

    Try this work-around... Add a "New null node" or "New group node" to your object, after you import it, or before you import it. Throw it in there, then translate that, keeping your object on the original 0,0,0 but obviously, the node is now moving to x,x,x which should, "Parent in place", correctly.

    [My Object group-node] <- (Parent this, "in place", into the model)<br />
    -> [My Object]

    Post edited by JD_Mortal on
  • JD_MortalJD_Mortal Posts: 760
    edited September 2019

    Alternatively, you can do the same for the Objects and Models...

    Make a group-node, parent the model into that, in place, and parent the object to that, in place. Then move things around.

    [My Cameras group-node]
    [My Scene group-node]
    -> [My Object]
    -> [My Model]

    Post edited by JD_Mortal on
  • JD_MortalJD_Mortal Posts: 760
    edited September 2019

    When you import things into Daz, it creates a 0,0,0 (origin) that is irrelevant to where you had 0,0,0 (origin) in your external program. Same can be true if you export models from Daz, into some external program. The objects original origin isn't always used, with the translation offset. Some programs center X,Z and drop Y to the floor. Some just force X/Y/Z so it is 0,0,0 with the model being all positive values, and some place X/Y/Z at the objects center.

    Post edited by JD_Mortal on
  • FalcoFalco Posts: 241

    Oh nice, grouping it before parenting allowed it to parent in place correctly.  That's an acceptable workaround, thanks!

Sign In or Register to comment.