Marissa Farrell

There will be a breakout room centered around Marionette

I'm working on a solution to this, is it a requirement that the resulting objects are rectangles, or can they be polygons?

@Dendecko If you wire the rectangle you'd like subtracted to hTool instead of hBlank, does that work? If you're still struggling, could you attach a file? I'm not sure what the issue is that you're trying to describe.

I have not encountered this, the next time you encounter it could you try to get a screen recording and provide the file where you're running into this so I can take a look? Feel free to directly message them to me.

@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!

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

Are you in a top/plan view? That's required for wiring nodes together.

@DBLD HI Dan! Can you tell me which version and build you encountered this in? Thanks! VB-182139

This isn't possible currently.

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

@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

Could you attach the Vectorworks file?

You'll likely need to adjust some Z values prior to the solid addition - but just for visual clarification... Path Extrude Not Rotating_MFarrell.vwx

Right, I'm suggesting you build the whole solid laying down first, make it a 3D object prior to rotating it to be perpendicular to the floor.

Have you considered adding the EAPs to your panels prior to rotating them? Only rotating the one solid piece may be helpful.

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!

Can you provide me with the original file and the file created upon conversion? I'll try to take a look.

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?

@Christiaan I'm not seeing the errors you're receiving with Alan's original file. Also, the errors are pointing to incorrect syntax, so my assumption it's from you modifying code somewhere. If you'd like, I can take a look at it.

Can you give me an example of a file you're trying to use in 2021 that is failing?

Here's a solution using the Mix2 node. Example - Grid of points is in or on multiple polys_MFarrell.vwx

I've been wanting straight lines for ages, so I'd be on board with this 🙂

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.

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.