Jump to content

Marissa Farrell

Marionette Maven
  • Posts

    1,474
  • Joined

  • Last visited

Posts posted by Marissa Farrell

  1. Alan,

    After reading the explanation Kevin gave, I was able to modify your network to behave a bit better, although you'll have to let me know if it's really what you're looking for.

    As for determining which direction NURBS will be created, I have absolutely no idea. This has been an issue when generating contours and it drives me a little bit crazy.

    Once I figure out who to ask, I'll try to get back to you with more information. (I was also disappointed to see that we don't offer a node to reverse a NURBS curve... I'll look into that.)

  2. The issue here is that you have 21 inputs going into the Change Vertex Type node, which repeats that script 21 times. Technically, all of those outputs from the node are still the same Poly. (You're still only modifying the same poly.)

    One way you could handle this for now would be to use the "Get Item" node from the data flow nodes, using the list output from "Change Vertex Type" and an index of 0.

    I'll try to figure out a better logic for the "Change Vertex Type" to only output the number of polys input to it, rather than the length of the list of vertices. I'll post the revision here once it's done.

  3. On a surface you should be able to use the "Point On Surface" node.

    for the inputs:

    surface = handle to surface

    dir = (u,v)

    outputs:

    pt3D = the 3D point at that respective place

    normal = 3D vector normal to the surface at that point

    You originally asked about a curve, which there isn't a good response to.

    Hope this helps.

    (I haven't checked the results for total accuracy)

  4. Could you give me an example of what you're trying to accomplish? Vectorworks is generally able to work with planar objects in any orientation as long as you approach it from the right mindset.

    Marionette is also usually able to accomplish the same things, sometimes it takes a little more thought though.

    I'm more than happy to try to help you out with whatever you're trying to do.

  5. Hi Robert!

    I have answers for all of your questions!

    For your issue with the height, this happens because of the way you're generating your geometry. I've attached a simple file, "Simple Box", to show you a better way to produce this box and assure that it always gains its height upwards instead of downwards.

    With your records, you're very close. Attach whatever value you want to be the values for "wide" and "high" to your "Set Record Field" node in the "fldValue" port. I'm assuming you want Width and Height to be reported here, so simply wire those nodes to the respective ports.

    As for the symbols, if you want all of your planters to be the same size, then you would create the symbol just like any other symbol. In the Create Symbol dialog box, uncheck the "Convert to Plug-In Object" checkbox.

    If you're hoping to have many planters of different sizes, I would leave the box checked, however, as you've noted, when you drop them in, they will not be symbols. They will be Marionette objects.

    Please let me know if you have any questions/need any clarification.

  6. I do love this question!

    I don't have a great solution for this though.

    I can tell you, there is a node for 2D polys which will allow you to get the point and the tangent vector to that point... which I know isn't really what you're looking for. I thought it might work for 3D polys because it returns a 3D point and 3D vector, but it failed when I tested it. It does return correct values if you use a 2D poly as the input, though.

    I'll keep looking to see, but since NURBS are often interpolated, I don't know the best way to go about it at the moment. It doesn't look like there's a predefined function for this in Vectorscript.

  7. That script will work, but only under the condition that the layer you are trying to delete isn't your active layer. Also, you won't necessarily see the changes in the navigation palette until you go to another document. (If you check the Organization window, the layer will no longer exist.)

  8. Unfortunately, Alan, that script will only work on text objects.

    I think we were headed in the right direction with the scale node. If I get around to it today, I'll post a simple mirror node (I just have a couple more things I want to figure out on it). Otherwise, bother me next week and I'll get it up.

  9. This is due to the following line in the Contour Node:

    ubbthreads.php?ubb=download&Number=14989&filename=ContourScript.JPG

    If you uncomment this line (remove the "#", have it look how it does in the image above) then the reconstruction should be correct.

    It appears that we had that in the script at one point, but someone may have commented it out in a later revision. I'm not sure when or why that was done, but this should be the fix. It's on my list to fix in the default content! :)

    Hope this helps!

    Marissa

  10. Using the Marionette Object multiple times in the file shouldn't be dangerous, as for heavy, I'm not sure, but it definitely shouldn't be too complicated. The only time those objects will refresh is if you change the layer they reside on or the script inside, they shouldn't regenerate otherwise.

    You would want to save this as a red symbol, otherwise the elevation wouldn't update if you placed it on another layer.

    If you have a set list of classes you'd like to choose from, it shouldn't be complicated, but if you're hoping to generate a list from the classes in your document, it won't be as easy. If you want to set up, say, 5 classes that have styles that you'd want to use, you could manually create a popup menu that will display those as choices.

  11. This file might help you a little, there is still the case of changing the thousands separator from "," to "."

    I'm trying to decide the best way to replace the comma with the period, but it's a start.

  12. I'm not seeing your solution work, but maybe I'm missing something.

    I also think it wouldn't be optimal for the case where you want to mirror across a different axis.

    EDIT:

    Nevermind. I do see a possible use for this. I had to change my case to (-1, 1) though, due to the shape I was mirroring.

    But I'll still have to look into obscure angles.

  13. I think this has to do with Hybrid Symbols.

    As an example, draw a circle and a rectangle, select both and create a symbol.

    (EDIT - draw them on the layer plane, but keep the option to convert 2D objects from Layer to Screen plane in the Create Symbol dialog)

    Edit the 2D symbol and change the circle from screen plane to symbol definition, it will alert you that you're now creating a hybrid symbol.

    When you exit the symbol container, you'll notice that the circle will now display in 3D views, and the rectangle will appear in Top/Plan.

    Maybe this can help clear things up, at least a little, as to why this occurs.

  14. In addition, if it IS a group/symbol/container object, you may also want to call GetParent on it to see if it's a child of ANOTHER group/symbol/container. (If it returns a Layer, then you're at the outermost container object)

  15. What if you check the type of the object you're querying to see if it's a group or a symbol or another object type that could qualify as a container? That should let you know if it will have any "children".

    Still a little clunky, but I'm sure there aren't many other object types that would qualify as a container.

×
×
  • Create New...