SBarrettWalker
-
Posts
335 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by SBarrettWalker
-
-
Here is a definition I did a while ago for a landscape architect and I wanted to repost it here because I have gotten a lot of requests for it.
-
Hi Robert,
I think you might have already done this yourself but I have created a node that takes strings formatted into feet and inches and turns them into usable floats.
-
Patrick this is awesome! I am very excited about this!
-
Hello all, I just wanted to give everyone an update on the info given in the last webinar. At 12 min. 30 sec. of this webinar, I say that the command vs.RectangleN() can be given a variable name. This is not correct. This function returns None, so the variable would be equal to None. No matter what, it is necessary to use the vs.LNewObj() after the rectangle function in order to give the created rectangle a variable. I apologize for giving the wrong info, I hope I didn't confuse anyone!
-
Personally I think it is a very silly detail and it is completely understandable to have missed it. But I would get used to the feeling - It happens a lot with Marionette because we are not used to working so explicitly.
-
Hey Rick
I think I got your definition to work - the main issue was that a Custom object need a polyline or polygon as its path, not a line. There were some other changes I made if you want to check it out.
Let me know if that is what you are looking for
-
Hi M Evers, Alan is right. Marionette definitely has the capability of doing these things - the only reason that we may not have samples of these things available is that no one has had a chance to do them yet! Marionette has only been available to all users since September and to beta testers less than a year, so we are still in the early stages of helping users to understand Marionette's full potential.
The important thing to remember is that Marionette is designed to be ever-expandable and creatively boundless - If a node doesn't exist that does what you want it to do, it can be built using existing nodes and the Python programming language.
-
Hello - The difference between the two networks is that when you have two separate Name nodes, there are actually two different networks, meaning the object inside the name node gets used by one network and then another different one. This is possible because the network doesn't change the original object inside the name node so it can be used over and over again. It would be the same if you had one name node, and attached it to one network, ran it, then detached it and attached it to the next. If you want to run both actions as one network, simply make a copy of the name node using the copy node, and run one output to the negative definition and one to the positive definition.
-
Hello all,
It is frustrating that a number value can't be used as the input of a rotate node, but that is because the rotate node allows you to rotate objects not only two-dimensionally, but also around the x and y axis. Thus you have to specify the axis that you are rotating around with a point3 or vector3 node. In order to create a series of rotation values, use a Point3D node from the Points category and put the angle values into the z input of the Point3D node. (A point3 or vector3 node does not allow inputs from other nodes, only typed in inputs.) Remember though that you need the same amount of objects as rotation values, otherwise it will add the rotation values together.
-
Alan,
It looks like you still need "get fill color" nodes to attach the objects to - the inputs for max mid and min need to be colors in (r,g,b) format.
-
Hello,
Here is a node that does something similar to the network that I built in the 3rd Webinar to create a range of colors, but this one adds a third color to the range. So basically it creates two ranges of colors, similar to a three color gradient.
-
Hi JSpodick-
It sounds like you are talking about showing an elevation of your light plot. If this is so I would recommend using viewports instead of Marionette. With Marionette you would either have to change the information in your lighting devices or make copies of them, and I don't think you want to do that.
Do you model your light plots in 3D?
If you would still like to use Marionette here are some suggestions. As far as the Objects by Criteria Node, it can only attach to objects by type, so it can attach all rectangles in the drawing to the network, or all symbols, but not simply those objects that are selected. There is no node currently that attaches to selected objects. A way to work around that is to group the objects and name the group, and then use a name node for the group and a contents node to access the objects inside the group. The other way to do that is use an Objects by Criteria node with it set to T=Symbol and then to filter out the objects by using some sort of conditional network. Any node that has a boolean output along with the filter node can be used to filter a list.
Also, the orient node is a good way to change the plane of your objects.
-
The rectangle node you are using is incorrect. Here is a fixed version that will move past the origin.
-
Hey Rick,
I am not sure what you mean by "Object Parameters," but the inputs for the Get Record Field and Set Record Field all take strings and their output values are also strings. So if you want to create a new record field or value, you have to type that value into a String node (from the Input category) and use a string node. If you want to transfer a value you use the output from Get Record field to the input of Set Record Field. The script provided tells you the names of the fields so you can type those names into string nodes.
I hope that helps.
-
Ah, that file was not included - here it is.
-
Hey Alan- so the reason I use a negative node is to invert the values - if you take them out you notice that the colors switch their order - It was a way to make the "max" color match the "max" value. They are not truly necessary - there are other ways to make this work.
(I had to double check this because when I work on definitions for a while - things can get redundant because I find different ways to solve problems as I work, but I believe it is true.)
-
Debug
in Marionette
Hey Rick - when running debug mode, if a wire is not selectable, it is usually because there is an error further up in the definition, it depends on the type of error in the definition so this is not always true, but if you can debug some of the wires in the definition but not all, that is usually the case.
-
Hi Rick, perhaps this file will help. It includes a script (not marionette, just vector script) that gives you a printout of the field names and values for a particular plug-in object. Then you can use those fields to make a marionette definition that will fill in certain parameters.
-
Hello - I have been working a lot with GIS Data as well and I have found that you have to do a lot of translating before you can use Marionette with it. For some reason, even if the record formats say they are numbers or dimensions, they are read by Marionette as strings. So you would first have to write a script that changes the dimensions written to a float: 130'4 ½" needs to be written as 1564.5 (inches) or 130.375 (ft). Once you get the values in the records into this format, you still need to add a "float" node after the output of the field values to make sure that Marionette reads them as numbers.
Also, I would make copies of the polys and then extrude those. You can then use the original polys to get the record and field names and then transfer them to the extrusions.
I hope this helps- good luck!
-
Hi Alan - I did this in 2D with a polygon instead of a curbs curve. Does this help?
-
Hello everyone! Thanks to those of you who attended today's Webinar. If you were not able to catch it, it will be available one YouTube soon.
For now, I am attaching the file I used in the webinar - I didn't get a chance to show what all of the definitions can do, so feel free to play around with them.
-
Hey Alan, I am not sure why a rectangle does not have to be converted to a polygon - I don't know if the idiosyncrasy is with the oval or the rectangle. Its one of those things that has to do with the basic VW commands that nodes are based off of. I only came upon it when debugging this script.
-
Here is the file with a better script. If you convert the ovals to polygons the script works the same as it does for rectangles.
-
Hey Alan-
The filter wrapper is there because when you send multiple polys/rectangles/etc to a planar boolean node, it cross references the list and therefore creates a lot of polys that did not get subtracted from each other. This is a flaw in the boolean node that we will hopefully be fixing soon. No matter what geometry you send through, the filter number should remain #21 - the number for polyline. the reason is that the objects you want to keep are the ones with holes cut out of them, and those are always polylines. The filter gets rid of any object that was not booleaned.
Therefore an oval should work it the filter number remains 21. I will double check.
Cubic vertex mode polyline
in Marionette
Posted
Hello,
I recently came across this problem as well and modified the Change Vertex Node accordingly. It is a symbol in the attached file as well as being used in a few definitions.