Jump to content

Marissa Farrell

Marionette Maven
  • Posts

  • Joined

  • Last visited

Everything posted by Marissa Farrell

  1. @gplumb I don't have the nodes that were created when mentioned before available right now, but here is a file that includes what I believe you're looking for. Newer versions of VW come with a small set of worksheet nodes, you can use Get Cell Value to return the subrow value. I created a node to get you the subrow count. I also saved it as a resource so you can save it to your library if you'd like. (If you need directions on how to get it to show up in the Marionette resource popup, let me know.) Please let me know if you need a version prior to 2023. Subrow Nodes_MFarrell.vwx
  2. Currently the Surface from Curves node can only be used in a Marionette Menu Command. I haven't figured out a way to allow input of curve handles, as the function requires the curves be selected, and Marionette does not allow you to act upon selected objects when not in Menu Command form. What's your final goal with this? What do you plan to do with the surfaces? There may be a way to bypass that step.
  3. The most similar behavior we have for this is the "Print Debug" node in the debug category. This node will create a text object that displays the values passing through the input wire(s) and the order they are received.
  4. No, Marionette scripts are still entirely open and editable.
  5. Yes, there's a missing line of code. In the #inputs section, add bComplex = self.Params.bComplex.value You'll also need to delete the first line in the script that begins with #COMMAND This has already been fixed for next service pack.
  6. Currently I'm unaware of a way to do this, even with styles. Right now the only value available to set by style/instance is the Reset on Move checkbox. We haven't exposed Marionette created variables at this time (I am unsure if it's because the capability is not there or if it will come at a later phase, I'll look into it.)
  7. The solution to this would be to set the settings of your data tag style to have 'Use world-based units' checked and 'by style' instead of 'by instance'.
  8. This appears to have to do with your active layer scale. My best guess is that the script is referencing the layer scale of whatever is active when it runs, since your data tags are set to be a certain way with regards to world-based units, the scaling is layer dependent. This can be tested by changing the active layer scale on your design layer to 1:1 and running the script (then pan or zoom to refresh the screen) The script DOES reset the objects every time it's run, it just appears to have a dependency elsewhere.
  9. You can just ungroup the Marionette object using the keyboard command (ctrl+U, cmd+U) and that will leave you with just the geometry 🙂
  10. My approach to this would be to generate your paving pattern, overlay a grid of points which would correspond to the individual pavers, and use the image processing technique shown in this example to color the pavers: Of course, the complete process may be more complicated than that, but I think it's a good starting point.
  11. This has to do with the way Marionette runs - it will run as many times as the longest list, repeating the last value. It's lightly discussed on this page: https://developer.vectorworks.net/index.php/Marionette_Basics In any case, I'm attaching a network that I think does what you'd like better, let me know if you need any more help! GetLayerLevelType_MFarrell.vwx
  12. Try using Set Planar Ref https://developer.vectorworks.net/index.php/VS:SetPlanarRef
  13. @MattGHave you refreshed your library? Also, this appears as though it's coming from a tool, is that correct? If yes, which tool?
  14. I think it's a little more than this. I've discovered it somehow has to do with stacking order and depends on something else that determines which way it traverses through the network. My assumption is that it chooses a starting node based on stacking order, then follows the connections from that node (in what way, I do not know), and then builds the script by traversing through the wires. I seem to recall seeing that someone created a method to number the nodes showing the traversal pattern... I'll see if I can find it.
  15. You should be doing this in the OIP, not the script editor. Use the Name field of the Marionette node, as shown in Antonio's example: Notice that the purple nodes are still all "Name" nodes, they just have a custom name above them that was entered in the OIP. EDIT: I do see that it appears you ARE still attempting to do both, I was caught off guard by your OIP control also having the numerical prefix. If you're still running into issues, please directly send me a file and I'll take a look.
  16. Hi Scott - I'm not very familiar with this, can you provide me with more information?
  17. You can place them as (196,220,196) HOWEVER, these values are in the range of 0-65535, so you need to multiply the standard 256 values by 256 to get the right color in VW. so, for example, your values would be (50176,56320,50176) You can enter the string right into the Any node text field as the 3 values within parentheses. Also, you can technically use a point3 input node with your r, g, b values as x, y, z.
  18. The good news is I was able to reproduce in SP3.1, but not in my testing builds, so it appears to me that come next SP things should be in good working order for you 🙂
  19. I'm not seeing any VS function accessibility for feature layers at this moment in my list, either. I can throw an enhancement request in for you if you'd like?
  20. @Benson Shaw There's also an Color input node that will pass the color of the node as a tuple in the Input category, if you wanted to pursue that option instead.
  21. Classes do not matter for the purpose of wiring, that shouldn't affect this at all. I still am unable to reproduce this following the steps you've given me. Which build are you using? I was able to see the error you mention in the file you shared with the error already present, but I cannot get my own copy-paste to have the failure. This, however, is similar to another issue that was posted on the forum recently, so I don't doubt it's happening, I just need to be able to reproduce it to further investigate.
  22. I didn't run into an issue when copy-pasting to a new file. Let's look into this more. Could you try it again? This will be tricky because objects created by Marionette are replaced on each run Marionette Objects are Plug-In Objects. All objects within (created by) a Marionette Object will be on the same layer, just as with every other Plug-In Object. It's likely there's something within your script that is working incorrectly, or unexpectedly. This will result in an empty Marionette Object (there's an open bug for this)
  23. As much as I advocate for Marionette, I will always stand by the opinion that a traditional script is the way to go if it's doable for you! Marionette, to me, is just a way to hold your hand while you learn. I'd like to suggest you also try recreating this script using Python in Vectorworks, just to introduce you to a different set of syntax that generally is more user-friendly than traditional Vectorscript. It shouldn't be hard to translate 🙂
  24. I'd like to correct myself here and provide a better solution. Your symbol resource that you reference is NOT being carried over when you copy it, I'm actually not sure how it's fixing itself. The attached file is a better solution. I advise you to place all resources that your network requires within the Marionette script container (you'll notice in this file if you edit your script that there is a group of objects, within that group are symbol instances of the symbols you've referenced in your popup) Unstrut v6 v2022 v2.vwx
  • Create New...