Onink Posted October 8, 2020 Share Posted October 8, 2020 (edited) I'm using marionette for cabinets. So the bottom and sides, etc are extrusions. I can give a name to a normal extrusion which I can find in my spreadsheet with it's measurements. But how can I give a name to a extrusion in a marionette object? I want to extract the measurements of my extrusions out of the marionette objects into the spreadsheet. Edited October 8, 2020 by Onink Quote Link to comment
Onink Posted October 15, 2020 Author Share Posted October 15, 2020 I found out that naming the extrusions will not work. Is there a way to get the name of the marionette object in a spreadsheet? Or the wrapper name? Any name at all...? Quote Link to comment
Pat Stanford Posted October 16, 2020 Share Posted October 16, 2020 What do you mean that naming the extrudes inside the Marionette won't work? Take a look at the wrapped network and the worksheet in the attached file. I am able to name the extrudes and get that information in the worksheet. Make sure you Run the Networks and Recalc the Worksheet. What am I missing? Marionette Named Object Test v2020.vwx Quote Link to comment
Onink Posted October 16, 2020 Author Share Posted October 16, 2020 I guess you're not the one that's missing something...😁 I hadn't found that name node. Thanks, this helps me halfway. I can't name multiple objects the same, since every object must have its own name. So the sides would have to be named different, well that's possible.. How can I name the entire marionette object? In the spreadsheet I would have the name of the cabinets in one column and the name of the parts in another. I don't know if that's going to work, because I would have multiple object with the same name, only from a different object. Any ideas on that? Quote Link to comment
Pat Stanford Posted October 16, 2020 Share Posted October 16, 2020 That is not going to work because VW only allows a single object to have a specific name. Perhaps what you want instead of using the Name field in the OIP is to create a custom Record Format and attach that to the object and store your "part name" in a field there. You can still access it from the worksheet, but you can then have multiple parts with the same name. Quote Link to comment
Onink Posted October 16, 2020 Author Share Posted October 16, 2020 I understand what you mean, but I can't find how to store my part name in the record. Can you help me out? Quote Link to comment
Pat Stanford Posted October 16, 2020 Share Posted October 16, 2020 Take a look at the Set Record Field node in the Record & IFC section. You should be able to use String nodes to set the Record Name, the Field Name, and the Field Value. One Set Record Field node for each of the extrudes in your Marionette should be all you need. You will need to already have created the Record Format in the drawing prior to running the Marionette. Or you could use the Create Field node to build the Record Format from inside the Marionette. But in MNSHO, it is safer to have it already created. Quote Link to comment
Onink Posted October 20, 2020 Author Share Posted October 20, 2020 I can see how this works as I am testing it, thanks for your advice. Now to implement it in the cabinets I have allready made... Quote Link to comment
SimA Posted July 29, 2021 Share Posted July 29, 2021 Hello Pat I have a proper name for the DB object. For comparison you will find the whole thing as a normal script in the file. Do you know how to solve the problem? Thank you very much for your help Greetings from switzerland (Google translater) DB_2.vwx Quote Link to comment
Pat Stanford Posted July 29, 2021 Share Posted July 29, 2021 I need a better description of what the problem is. The Marionette is complicated enough that I don't understand what you are trying to do and what the script is not doing that you want it to do. Quote Link to comment
SimA Posted July 29, 2021 Share Posted July 29, 2021 Hello Pat Basically everything works until I wrap the network and turn it into a marionette object. 1. As a script network, i can name the bars and read them of correctly in the table ("Item" A, B, C, D). 2. If I run the tool as a marionette object, the names are no longer correct ("Item" A, A, C, D)....? You can find .1 and 2. on a separate work plane as an example. The script and the object contain the same network. I think that the problem is to be found in the creation of the names or in the DB connection. Thank you for your help Quote Link to comment
Antonio Landsberger Posted July 30, 2021 Share Posted July 30, 2021 Hi @SimA, setting names is not recommended, especially when you plan on using this multiple times. If you want the names to be written into the record field, why not just connect the Ordered List node directly to the Set Record Field node? Like so: Seems easier than first assigning names to objects and then extracting the names again. Regards, Antonio Quote Link to comment
SimA Posted July 31, 2021 Share Posted July 31, 2021 On 7/30/2021 at 9:00 AM, Antonio Landsberger said: why not just connect the Ordered List node directly to the Set Record Field Hi Antonio The problem remains the same. I have unique names or labels for every single bar in the marionette object. These names or labels do not appear correctly in the table. The dimensions, however, are correct. I have noticed that this problem only exists with the marionette object. The list serves as a material list. I have a piece of each ingredient. It is also wrong if "frame below" is displayed twice. Thank you for your help. Quote Link to comment
Antonio Landsberger Posted August 2, 2021 Share Posted August 2, 2021 I figured out what the issue is and why it doesn't happen while it's still a network and not a marionette object. The node Parent PIO doesn't do anything while in a normal Marionette network, simply because there is no Parent-PIO at the time. When this network is made into a Marionette object, Parent PIO puts out a new Handle - additionally to the four 3D boxes already present. After removing the node Parent PIO everything works just fine. Question is: what use is this node where it is positioned in the network? What is the goal? 1 Quote Link to comment
SimA Posted August 2, 2021 Share Posted August 2, 2021 Hello Antonio If only it was always so easy to solve problems. I used the Parent PIO node because it can be found in most of the functioning networks in the forum. As a beginner, I can just leave the knot off. Another theme ... As a professional, how would you import an external database or CSV file? I would filter the values with Marionette and continue working with the filtered values. Thank you Quote Link to comment
Antonio Landsberger Posted August 2, 2021 Share Posted August 2, 2021 CSV files can be imported as worksheets and then you just need to read the information using the Get Cell Value or Get Cell String node. In case of an external database, you'd simply have to read out the information from the corresponding fields using the Get Record Field node. 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.