Results 1 to 8 of 8

Thread: Node displacement size problem

  1. #1

    Node displacement size problem

    I have a feeling this is a simple one - and I missing something.

    I am attempting to do some node displacments with subdivided object and had issues with size with complex object and complex nodes - so I made it simple and did the crust sphere example in videos.

    My problem is the size is always too small - but I can make it work - if I increase its opacity to 3000 or so. It simple nodes - crust 3d fractal, spot info and vector scale.

    I am having troubles uploading screen shot - maybe later.

    On side note, my dongle is being sent back to Newtek for swap out with USB tommorrow - so I will be on discovery edition for a while.

  2. #2
    My best guess for the cause: displacements like that are in units of meters (not sure what happens if you've changed your default unit). If you have a large object, you need a stronger displacement to get the same proportional shift.
    8x2.8 Mac Pro, 8 GB RAM, Radeon 2600XT, Mac OS X 10.5.6 (previously: G5 Quad)
    Caution: tech-savvy artist in full-on geek mode. May obsess over technical challenges until solved.

  3. #3
    I did change my units size - it is also likely a quite large object - is there good method to base of off percentage size of the object.

  4. #4
    Kitty defender manholoz's Avatar
    Join Date
    Dec 2005
    Location
    Puebla, Puebla, Mexico
    Posts
    599
    Why not put a multiplier vector node between the displacement and the other nodes? Multiply it by a lot (1000 maybe) and leave the transparency to a more coeherent number
    passionately alive

    Visit my portfolio!

  5. #5
    Quote Originally Posted by manholoz
    Why not put a multiplier vector node between the displacement and the other nodes? Multiply it by a lot (1000 maybe) and leave the transparency to a more coeherent number
    I actual did that.

    I thought about that but I wanting to know why the value is small.. I think it something to relation of size of the object.

  6. #6
    Kitty defender manholoz's Avatar
    Join Date
    Dec 2005
    Location
    Puebla, Puebla, Mexico
    Posts
    599
    Ummmm if it aint broke, dont fix it!

    As I work in milimetres when not working with metres, the 1000 multiplier does not sound so far-fetched to me.
    passionately alive

    Visit my portfolio!

  7. #7
    I am actually working in SDK side of Nodes and deired a good understanding up this. It also appears to me there is also an understanding or problem with distribution of largest feature on macros - my guess is this is related to scale.

  8. #8
    Kitty defender manholoz's Avatar
    Join Date
    Dec 2005
    Location
    Puebla, Puebla, Mexico
    Posts
    599
    Could be, makes sense. I cross with those kinds of problems all the time, has to do with using software designed for imperial units, and using them for metric units. Always bizarre things happen with the scale. But I am sort of used to it by now, me and my trusty calculator.

    So I agree with you, it could be a scale and/or unit thing.
    passionately alive

    Visit my portfolio!

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •