David O Posted November 4, 2017 Share Posted November 4, 2017 Hello everyone ! A few months ago (version 2017) i created a topic mentioning about the node Wall left walls unconnected when you feed a list of vertices into it's inputs. Now (in 2018) i realized that the Wall node is still presenting the same issue... I wonder if there's any form to join walls via Marionette without having to re-program the node... Thanks for any tip... Quote Link to comment
AlanW Posted November 8, 2017 Share Posted November 8, 2017 @David - CADTECHi, in this network the node closes but i think it is because i link the last node to the first. HTH. Close_Wall_Node.vwx Quote Link to comment
AlanW Posted November 8, 2017 Share Posted November 8, 2017 @David - CADTECSorry David i uploaded the wrong file, see attached. it appears the 2018 shipped node does not not close any walls but the previous one Marissa gave me closes all walls and the end. See attached file. HTH Close_Wall_Node_v2018.vwx Quote Link to comment
David O Posted November 22, 2017 Author Share Posted November 22, 2017 @Alan Woodwell Thanks for your comment ! As you know there's a tweet in the wall node code provided by @Marissa Farrell in my first post in March ... That will work fine ... What i wonder is why not incorporating that new solution to the wall node that comes with the program ? I think the evolution of the nodes is an important point to remember when releasing new versions of VW don;t you ? Or do this behavior of the wall nodes is something that is expected ? Cheers ! Quote Link to comment
Marionette Maven Marissa Farrell Posted November 22, 2017 Marionette Maven Share Posted November 22, 2017 9 hours ago, David - CADTEC said: What i wonder is why not incorporating that new solution to the wall node that comes with the program ? I think the evolution of the nodes is an important point to remember when releasing new versions of VW don;t you ? Or do this behavior of the wall nodes is something that is expected ? Hey David, We are continuously adding and updating nodes in Vectorworks, however we have to send them through a process where the new changes can be approved. In the case of this node, it just hasn't made it through the approval process. It will likely find its way into the software later. Hope this clears things up. Marissa Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.