Page 2 of 2 FirstFirst 12
Results 16 to 19 of 19

Thread: Simple vector math is not simple

  1. #16
    Registered User
    Join Date
    Jan 2013
    Location
    NA
    Posts
    79
    Quote Originally Posted by dpont View Post
    so if you use a different MDD Cache for Adding and Substracting
    using a copy of the node, this should work
    Thanks for the workaround, it works very well. This is very important for V11.6.3 user like me.

    Quote Originally Posted by Sensei View Post
    What effect should I see?

    I tried ATM LW 2018.0.7.
    As Denis said, you saw the final effect as stage2 maybe you were on V2018, and I'm on V11, thanks for help anyway.
    Last edited by mewnow; 05-24-2019 at 08:07 PM.

  2. #17
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    7,891
    Quote Originally Posted by dpont View Post
    I think I found a workaround,
    the issue is caused by the second evaluation of the same MDD Cache node,
    one for Adding and then for Subsracting,
    in this case the node editor seems to miss/decal point iteration (?),
    so if you use a different MDD Cache for Adding and Substracting
    using a copy of the node, this should work,
    note that it shouldn't use more memory,
    because it uses instance of the MDD file.
    What did you mean?
    Your node->Copy() function does something else than user can do manually picking up the all fields by himself/herself in UI (and making settings-equal version of node) ?
    If yes, that's very bad...
    LW uses node->Copy()/node->Load()/node->Save() internally to e.g. implement undo AFAIR..
    If you will put MessageBox() to node->Copy()/node->Load()/node->Save()
    you should see that they are called much more often than you expect..

  3. #18
    Member
    Join Date
    May 2006
    Location
    France
    Posts
    3,978
    Quote Originally Posted by Sensei View Post
    What did you mean?
    Your node->Copy() function does something else than user can do manually picking up the all fields by himself/herself in UI (and making settings-equal version of node) ?
    ..
    No, I meaned that older version had a limitation,
    node must be evaluated once only,
    for another operation of the same MDD,
    user need to add another node, or a copy.


    Denis.

  4. #19
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    7,891
    Ah, right, because it had internal vertex index counter/"pointer", which is incremented each time Evaluate() is called to the next data.
    I had to use newer version, because could not see any bad effect. Therefor asked him to show screen-shot what he see. But now all is clear.

Page 2 of 2 FirstFirst 12

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
  •