Loading...
> >

Daz Studios's scene tree

Doc AcmeDoc Acme Posts: 1,153
in Technical Help (nuts n bolts)

I've spent way  too much time trying to find out how to do a very basic task & that's to simply hide/show specific items.  Ya, there's the eyeball for indivitual nodes but that's not what I'm referring to.

In ALL other apps I've used over the decades, toggling a Parent item to OFF also hides it's Child items.  Not so in Daz, or at least not by any means I can find such as a right click or menu drop down.  Surely there must be a way?

On a similar topic, is there a way to easily export out just a single item, object, camera or light?

Comments

  • ebergerlyebergerly Posts: 3,255
    https://www.daz3d.com/forums/discussion/252471/apply-operation-to-multiple-selected-items-solved
  • MelanieLMelanieL Posts: 7,481

    One way to hide all the children is by adding the parent to a group then hiding that - it takes out everything in the group. (I have NO idea why hiding the parent doesn't work like that already).

    Second way is with a script - I picked up a freebie ages ago which propagates visibility down the chain. BUT I have forgotten where I got it - maybe someone remembers?

  • Doc AcmeDoc Acme Posts: 1,153

    Wow.  What a convoluted process.  Thanks for the link info.

  • Doc AcmeDoc Acme Posts: 1,153

    On a similar, or rather continuing as this is what prompted my question to begin with, is there a (simple) way of exporting only selected item(s) from DS?

    I'm slowly translating my library to Lightwave & having excellent luck now since using FBX2012 rather than FBX2014.  I can even easily apply angular corrections for the lights such as adding 90 deg to Pitch.  Cameras on the other hand need some TLC. They are positioned correctly & all the scaling works out, but angular values I'm at a loss but not that they're messed up.  They see the same thing as in Daz once focal length & Dims are set. It's HOW are they doing it.

    EVERYTHING imported from the FBX gets a parent null, which fortunately is quick & easy to selectively change, effectively performing a DeParnet in place. The result is the camera sees what it did before, but it's HPB has no correlation to Daz's Xrot Yrot Zrot values.

    For example, I set a Daz camera to -30 on all the rot values. 

    So:
    Xrot = -30
    Yrot = -30
    Zrot = -30

    For Rotations, Daz's Xrot = P
                                  Yrot = H
                                  Zrot = B

    In LW, that cam's values are all 0 as it's parented to a null that has these values:

    Prior to DeParaenting, the Null has:
    H=9.46
    P=40.51
    H=-34.72

    After the DeParaenting, the Cam now has these values:

    H=-22
    P=14
    B=-0

    Yet it's still seeing the exact same thing as the same cam in Daz.  How that possible?  I'm not a math dummy, but I'm not seeing any correlation here.

    I can only guess that the values Daz is showing aren't what it's really using internally and it's all "gaining" something in translation. I don't need (I hope) to know that, just some to set up a cam in LW that matches that in DS w/o exporting the entire 250Mb scene. 

    I can of course just manually creating a fresh cam in LW, use the Daz info to position & then eyeball the rotations, but I'd really like to figure out a technique that's accurate.

     

  • ebergerlyebergerly Posts: 3,255

    Same as the visibility thing. Make the stuff you don't want exported invisible, then when you export check "ignore invisible" or whatever. 

  • ebergerlyebergerly Posts: 3,255
    edited April 2019

    As far as the LW stuff, I have no clue since I can't figure out what you're referring to. My best guess is maybe it has to do with local vs. world coordinates, or parent vs. world or something like that. If you de-parent maybe it shifts to a world coordinate system rather than relative to the parent. Also look at the DAZ Import/Export settings and make sure it's all set correctly (coordinate system, scale, etc.).

    Also try google, since I'm sure a lot of other LW users have had this problem with the HPB stuff. 

    Post edited by ebergerly on
  • Richard HaseltineRichard Haseltine Posts: 102,730
    MelanieL said:

    One way to hide all the children is by adding the parent to a group then hiding that - it takes out everything in the group. (I have NO idea why hiding the parent doesn't work like that already).

    It's a legacy from Poser compatibility, back when most content was in Poser format and needed to work consistently across applications. The group node was added as a way to hide all elements of a hierarchy.

  • Doc AcmeDoc Acme Posts: 1,153
    ebergerly said:

    Same as the visibility thing. Make the stuff you don't want exported invisible, then when you export check "ignore invisible" or whatever. 

    OK.  I asked that in another thread on how to easily hide stuff.  Pain in the butt frankly how you have to do that in DS but I'll certainly investigate that.  Doesn't seem particularly practical when you've a huge scene like any of Stonmasons products.  It's actually way, way quicker to simply export the entire scene & then toss what I don't need. 

    I was wondering if the rotation stuff question might get some "deer in the headlights" reactions here, but I've seen some pretty clever folk come out of the woodwork too so had to ask.  I'll reword a bit & ask over on the Lightwave forum. 

    So it goes. 

    Thanks all.

  • Doc AcmeDoc Acme Posts: 1,153
    MelanieL said:

    One way to hide all the children is by adding the parent to a group then hiding that - it takes out everything in the group. (I have NO idea why hiding the parent doesn't work like that already).

    Second way is with a script - I picked up a freebie ages ago which propagates visibility down the chain. BUT I have forgotten where I got it - maybe someone remembers?

    Ooo!  There ya go. Script sounds good.  Hopefully someone recalls.

Sign In or Register to comment.