[NOT EXPECTED] SubTree reset

Forums › 💬 NodeCanvas › ⚙️ Support › [NOT EXPECTED] SubTree reset

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • March 19, 2021 at 11:02 am #16011
    driiade
    Participant

      Hello 🙂

      I have a sort of “Bug”, it’s more like clearly really not expected.
      If you place a Dynamic selector with a SubTree, or SubNode (capture1), and if in the SubTree you have a dynamic selector too (capture2), in fact the subTree can return a status of failure. BUT the subNode will not be checked again because as it fail, SubNode will not try to check it again and just skip the SubTree.

      You can put a Reset on top of the SubTree, but it will cause other sad behaviour to happen.

      What is expected is that the SubNode doesn’t skip to check SubTree if it fail, because it dosn’t know the internal structure, and maybe the subTree is dynamic or whatever. For me SubNode doesn’t have to “logic”, it’s just a way to reuse branch, and putting or not branch in SubNode has exact same behaviour.

      Hope i’m understandable ^^”
      Cheers,

      March 20, 2021 at 12:07 pm #16013
      Gavalakis
      Keymaster

        Hello again 🙂

        Hmm. Can you please show me a simple replication example so that I can understand better what you mean?
        Also, what version of NodeCanvas are you using?

        Let me know.
        Thanks 🙂

        March 22, 2021 at 10:42 am #16012
        driiade
        Participant

          Yes I can 🙂

          Simply put a Selector as Dynamic (figure 1) with a subtree and a runForever.

          In the subTree, place A dynamic selector which run only if conditionnal met (figure2).

          If you change the condition to be true, you will see you will not run the subtree. which is totally counter intuitive.

           

          You can workaround this by placing Reset or the same conditionnal on Top of the subTree Node.

          The first work around doesn’t work as intended as Reset also Reset action / condition, and sometime you don’t want.

          Second work around break genericity / composition, as sometime SubTree doesn’t have same conditionnal requirement.

        • Author
          Posts
        Viewing 3 posts - 1 through 3 (of 3 total)
        • You must be logged in to reply to this topic.