the frog

Hello I found a strange behavior of the dim nodes in enveloppe scripts. If you make a script, give a name to the dim node and then enveloppe (this is the base), when you copy the enveloppe to use it somewhere else and change the Dim node value without changing the node name, everything is fine. When you finish your script make the object it is still fine. BUT when you copy the object… The values of the Dim nodes with the same name change values to pick up one of the value (I guess the first one in the Vector script text file) and apply it to the other nodes. Of course, the copy object looks bizarre! I found it while working on the Ikea cabinet I just posted. It took me hours to find the pb and change the names.

Thanks for the info. Concerning the script modification date 2017, the 2019 mirror script is different from 2026. As they both have the same modification date, I assume it’s just some kind of forgetting.

Hello I discovered a strange behavior with the mirror node. If you mirror without duplicate and then give an attribute, the color changes. If you duplicate the mirrored side changes color but not the original. I looked into the node script and dates between 2026 node and the one I used in 2019 is unchanged 2017, but the script changed. I tested the old and the new node, they both do (or undo) the same way. Any idea?

Hi The best way to understand Marionette is to follow the node colors. It seems a strange way to learn but it works. If you put a green node, you are in 2D the input will be blue etc… When you look at the marionette selections you already should have a good idea of what’s needed. As you are a beginner you should try do draw your intentions, thinking of the result you want. Once done, search for the best node in the library corresponding to the immediate script needed. Eg: I want to make a cube. What is a cube? A rectangle equally sized on all of the six faces. Therefore, I need a rectangle, and an extrusion and a number (size). My input number (real) is unique. Pick in the library a rectangle node, a real input and the extrusion one. Link and run the script, it works and you know why! I am sure you know this, but whatever the complexity of your expectation, the method is the same.

Hello I found a strange solution to your question. It consists in naming each part of the surface by double ciick; edit volume; select the object and name it. Do the same on the sculpting one with, of course, a different name. In the marionette script in the name nodes put the object names You will get what you look for in a group. If you ungroup you’ve got your nurbs. Hope it works for you solution?EXTRACT CURVES NURBS SURFACE_MARIONETTE.vwx

Last version 2.1 Added the multi polygon option. You can choose the roof slope in ° If you want to add a layer look inside the "floor_number_decision" node once you've created your layer buiding by layer V2.1.vwx

hello please attach the VW file

Here is a debugged version (false 2d restitution) + the "terrasse" roof added. This version allows you to choose in the OIP, the ceiling high, the roof typology, and the numbers of level before the object is considered apartments with no roof. There is still a bug with the double roof, it won’t take the attribute and stays colored (VW mystery). The Enveloppe node won’t return the 3d name, that’s why you have the last node attached. If you run the developed script, once you’ve put back in the last node, it works. buiding by layer V2.0.vwx

Hello Thanks to Marissa (the copyName problem), after digging into your question, here is a possible solution. In the VW network, you have the developed script (to see the way it’s built) and the enveloppe one. The script works with rectangles and 4 sided polygons. I kept your layers names and added a “specific“ one where the script is written. 1- To make the script work you need to choose the layer you want the building to be. THE LAYER DEFINES THE NUMBER OF FLOORS AND THE TYPE OF HOUSING. 2- Second you draw your e.g: rectangle where you want it on the plan. 3- You give a name to the rectangle (bottom of the OIP) 4- You run the node. A dialog box will open where you copy the name you gave to your rectangle 5- Magic it returns a 3d model with the parameters (number of floors, roof type, layer) you asked in your post. 6- If you are in a different layer when you draw the rectangle and change the object layer, the result will be seen on the chosen layer AND will become the active one. 7- If you copy a 3d group, its name will increase by one. Remember that a name is unique in VW never give twice the same name or it will return the Marionette node number If you are not happy with the ceiling high (now 300 cm) dig in the script, the “real”node name is “ceiling hight”. If you want to change the number of floor parameters e.g: a “Detached house is built with 2 stories you need to change at the beginning of the scrip the “param” value AND open the “floor_number_decision” enveolppe node to modify inside the chosen layer enveloppe node, the “int” number (number of floors, always smaller or equal to the “param”). For the name buildings and shapes I choose, you might recognize the Hague addresses (thanks to Google earth)☺️ building by layer V1.vwx

Thanks Marissa So the script I wrote in the “copy node“ was not sufficient to change the name. Still a lot of progresses to make… Thanks for the “concatenate” Changed the input get name to original output and added “3d” instead of “_”. To satisfy you curiosity I want to have for each object its 3d image with the same name +3d.

Hello Here is the problematic network. When you run it with the input string node it works. When you run it via the get name node it doesn’t. I’ve written 2 new nodes “Copy Name for layer” and “set group name” The Name node (on top of the copy one) wont function. If you hit duplicate, the layer changes to “network”, if you stay with no “duplicate” you lose the object but keep the layer. For the last one “set group name”, it was the only way, I found, to change automatically the group name. On the image I moved the resulting objects for better understanding, when you run the script the result object is of course on top of the rectangle. I guess the reason lays in the deep structure of VW. It would be great if somebody had THE solution network problem.2vwx.vwx

Hello If you look in the Marionette gallery, the last object (frame artwork), the network does the same starting from an excel file. the frames are spaced an ordered according to their size

Got the idea You spoke about polygons, are they all four sided or rectangle only? Do you want to see the separation between the floors? Do you need to choose with or without roof? In you first post you said the roof was 1,5m now the high has to comply with the number of floors (1 level 1,5m 2 levels 3m etc…), or do you want to be able to specify the roof high? Only the first questions before writing the script

Hello This is what you get 2 floors and the roof. Of course it's possible to fill the roof. The easy way is to send a vw file with the result you want. This way it's possible to help.

As Pat said the easiest way is to start from an existing node. To be precise you have to change the first 2 lines #COMMAND;READONLYREFFILE;[VWLibDef]/Data Flow\Pass.py; #Modified by MFarrell May 2017 Delete the first line but keep the “#” this is a good habit because you keep the number of lines (useful when later you modify an existing node) Change date and name in the second one Then put the name you want here “pass” #APPEARANCE #Name this = Marionette.Node( 'Pass' ) Last try to keep the node color chart as you go, it makes life easier.

A I said previously this is very tricky specially when using home-made data bases because nothing changes in the figures. I realized that the symbol images kept their inch dimensions and applied them instead of converting them in cm. As the object library extend it becomes crucial to look for those “problematic” nodes that refer to external strings or data bases. I built an enveloppe node (Letti R advice) that makes the script works.

You are right this could be a way to do it. This adds time to the object final calculation. You then have to convert the differences between frame size and artwork size in feet, to centimeters (or else) in the resource manager, not converted when you change the type of units in the preferences. This is why there should be a way of modifying the way VW handles the decimals separator (like excel where you can choose). The same with the data in the OIP. This becomes a main concern when importing or using objects connected to data bases.

Framed Artwork 1.0.0 This new post about a problem that occurs when using the Frame artwork Object. As Magnus Mikaelsen reported the string to float conversion is not working. This is a problem between US and European versions. The “float” node works only with “.” for decimals. Therefore, as in Europe the decimal separator is “,” When extracting values from the data base it doesn’t get the signification of the sign, and returns “unknow value”. In VW, data bases in Europe cannot be expressed with “.”, so there is no way to use a Marionette object or network that involves the float node. To test I changed the network, adding the “Replace String” node and the network works. Of course this is just for testing because otherwise you have to manually change the strings each time you encounter a float. No idea how in the States you could manage to make this works in Europe

Are you looking for DomC node ? Easy to use fast and great !

Hello Jumping on what you said “For example, the Texture nodes have always been a headache for me.” The textures in Marionette are just a nightmare. Since the beginning the random texture problem is yet unsolved. Why are the textures changing name as the script is executed? Even when you download the file a new unknown texture can replace the one in the file. For us this is the true limit for using the scripts in our flow. Too much time lost on this matter as the object changes some textures as you try to only change one. Yes, a new well working node that would allow all the texture parameters in one node would be great. This would be a good way to put the Advil back in the closet.

Hello this is one of the first version of marionette rectangle. I'd rather use Dom.C rectangle old version.vwx

Inside the “ insert symbol by size” post, I left a script “stage builder” where you can find a waiting enveloppe. I made it for the whole script to run when changed into object. Without this “delay” I was getting an system error message. Why is it working or not I don’t know but it working this way