Announcement

Collapse
No announcement yet.

Why when cloning liquid simulator its output changes ?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Why when cloning liquid simulator its output changes ?

    Why when cloning liquid simulator its output changes ? I'mean both of 'em change path.
    I just can't seem to trust myself
    So what chance does that leave, for anyone else?
    ---------------------------------------------------------
    CG Artist

  • #2
    What version of Phoenix are you using? Is this Max or Maya?
    Georgi Zhekov
    Phoenix Product Manager
    Chaos

    Comment


    • #3
      Latest. max. That behavior is about several months from today. So, literally it is not build number dependent
      I just can't seem to trust myself
      So what chance does that leave, for anyone else?
      ---------------------------------------------------------
      CG Artist

      Comment


      • #4
        Yup, if you clone or instance a simulator, $(scene_path) or $(scene_dir) macros in the simulator's paths get deconstructed into their building blocks, respectively:
        $(dir)\$(scene)_Phoenix_frames\$(nodename)_####.au r
        $(dir)\$(scene)_Phoenix2_frames\ND$(handle)_$(node name)_####.aur

        If this did not happen, the copy/instance would be empty without a loaded cache, because $(nodename) is different for the copy, and $(handle) is different too.

        Is this a problem for you?
        Svetlin Nikolov, Ex Phoenix team lead

        Comment


        • #5
          They are both changes. The one that is a source for the copy and the copy itself.

          I'm not sure whether it is a problem or not
          Last edited by Paul Oblomov; 24-01-2019, 06:39 AM.
          I just can't seem to trust myself
          So what chance does that leave, for anyone else?
          ---------------------------------------------------------
          CG Artist

          Comment

          Working...
          X