Jump to content

Marissa Farrell

Marionette Maven
  • Posts

    1,473
  • Joined

  • Last visited

Everything posted by Marissa Farrell

  1. I think there are issues with the Set Layer node... (Okay, I know there are... and I have NO IDEA where Ham is coming from.) Give me a bit and I'll give you a working example on how to change an object's layer.
  2. Alan, I'm going to try to answer all of your questions, although they may be out of order, and some may take longer for me to form a response to. First, this file will help you get the correct values from your spreadsheet. In this case, we need to get the value of a subrow cell, instead of the value of a row cell. I've added two brand new nodes to your network (I probably have the same ones floating around, and these ones aren't clean in the sense of descriptions, but they work. One day I'll get all of my worksheet nodes posted with correct descriptions.) The first node is "Get Subrow Count", this will tell you how many subrows there are for a row. In your spreadsheet, row 2 has 2 subrows. I've incorporated this into your network to show you how to use it. The second one is "Get Subrow Value", this node will provide you with the value in the subrow cell. It takes the same inputs as "Get Cell Value" as well as a "Subrow" input. In this case, we will use 2 as our Row input, and 1 through 2 as our subrow input. I hope this can guide you a bit. As for the series node, that just has to do with how math is calculated. Float numbers can have infinite decimal places, sometimes they don't round out the same way that you would expect. I wouldn't worry about how far this goes, because having that many zeroes before that three means it's very, very insignificant overall.
  3. Whoops! That popup is my fault. The node in this file shouldn't do that anymore I often throw in alert dialogs to make sure my scripts are running correctly, and I forgot to comment this one out!
  4. Just in case anyone in interested in my answer to RMDiekmann's question posed above, I've posted my method here:
  5. I created a node in the attached file called "GetExternalSymbol" You'll be required to enter the full path to the file location as well as the name of the symbol you want to use. This can be changed, if you want, we can make it more custom later. A note on your path - based on your machine, you may have to normalize the path. The path in my example is windows based, you are required to do double slashes (//) instead of singular, due to escape characters in python. Mac may be more difficult. If you need it, I'll look into it and get back to you soon. Please let me know if you need any help with this.
  6. If you're talking about the default background, you can change this in the "Interactive Appearance Settings".
  7. Here's one way to extract just one light in your set. I boxed in the location where I added nodes. Let me know if you need help expanding on this.
  8. Alan, I love your extensions on this project! The colors are VERY fun.
  9. This script is very close, might need some tweaking, but produces very similarly to what you want. Let me know if you have any comments/questions. Marissa GoldenAngle_Tool_MFarrellSolution.vwx
  10. I just stumbled across this, but I wanted to say that I also would really love a feature like this included in VW - probably not specific to Spotlight, but incorporated into all packages. I'm a big fan of statics
  11. 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.)
  12. 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.
  13. 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)
  14. I'm actually very interested in the possibility of acoustic analysis (even more than the zoo animals, shhh) I should brush up on my old vibrations textbooks and get more learning into my head to make this a reality!
  15. Integrated zoo planning is my new wish list request! Thanks for the idea! (I see lots of giraffes in VWs future.)
  16. 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.
  17. You could use the move node and a 2D vectors to move them downward. This isn't the cleanest method, but maybe it can help you with an idea.
  18. 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.
  19. 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.
  20. Hi! I think this post might help: https://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Main=44522&Number=225623#Post225623 In that example, the Marionette Script will assign record values to the Marionette Object, which can then be reported in worksheets. Please let me know if this is what you're after/if you need any guidance. Marissa
  21. 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.)
  22. 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.
  23. This is due to the following line in the Contour Node: 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
  24. 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.
  25. This will show the period as the separator.
×
×
  • Create New...