Jump to content

Marissa Farrell

Marionette Maven
  • Posts

    1,473
  • Joined

  • Last visited

Posts posted by Marissa Farrell

  1. @line-weight

    I'm not seeing a wrapper in the original file that I shared, and I am also seeing that it behaves identically in 2022 to 2018, so I assume it also works correctly in 2021.

    Can you give me more information as to what you're encountering? Possibly share a file, either here or by direct message?

    More than happy to help you solve this issue!

  2. I created a custom node for this, and it's not currently deleting the last created object when finding this point (due to how Split2DObjectByLine works), but this should get you started!

     

    Use the dim node to define the Y dimension where you'd like to split the curve.

     

    My script currently works with polys, as I am unsure which object type you are displaying in your screenshot.

    Split Poly at Y Loc.vwx

  3. On 6/15/2021 at 10:45 AM, Antonio Landsberger said:

    @Marissa Farrell

    How easy do you think would it be to modify the Chunk List Node in such a way, that it could take a list instead of a single number?

    If the chunk list has less items than necessary to chunk the other list, repeate the chunk list from the first item.

     

    I don't think it would be too hard. I'll take a stab at it once I have some free time.

  4. @spries

    I'm attaching a file with a modified Popup node. It will output the value chosen by the user.

     

    The lines that are modified:

    13 - defines the list of options

    14 - displays the list in 13 for the values in the Popup

    30 - gets the selected item from the values in line 13 as defined by the result of the selection in 14, then converts it from string to float for numerical operations.

     

    I hope this helps! It's very similar to how Jesse described his method, but avoids the spaghetti mess of placing all of those nodes.

    moddedPopupNode.vwx

    • Like 1
  5. The issue is in the naming of some of your nodes. I think the primary culprit is the " ">" " node. I would suggest avoiding characters that are not letters or numbers.

    Was this created in 2021?

     

    Edit: it's the node AFTER that. Your > Text node is causing the issue. I'll be submitting this is a bug 🙂 Thanks for bringing this to my attention!

    • Like 1
  6. Subrows are calculated based on criteria, so the way to do this would be to modify the data attached to the item the subrow is referencing.

    Which field do you use when adding the count data to the space object?

  7. OIP controls are not dynamic and there isn't a smooth way to do this at the moment. It's something I've been looking into for a couple of years now, I have some ideas in progress to get around the limitation, but they aren't completely set yet. I'll try to remember to update once I get things nailed down better.

  8. I have a couple of quick suggestions before we continue - I would store the pillow as a symbol rather than reference it from inside your Marionette Object (I would place an instance of the pillow within the script area still so that when you place it into a new document it comes through as well, though)

    Your point going into the Move node should be a 3D point - use Get XY to separate your desired point and recreate it with the Point 3D node as you've done in other areas of your script.

    I'm not sure you have the point you desire going into this port, though I may be mistaken.

     

    I'm more than happy to keep working through this with you, but please try what I've suggested and see if it helps you at all.

×
×
  • Create New...