-
Posts
1,530 -
Joined
-
Last visited
Reputation
640 SpectacularPersonal Information
-
Occupation
Quality Assurance Specialist
-
Hobbies
snowboarding, macrame, beadwork, embroidery, Binding of Isaac, Marionette, arts & crafts, 3D Printing, reading, saxophone
-
Location
United States
Recent Profile Visitors
28,638 profile views
-
The issue is with how you're assigning values. The alphanumeric code after your numerical value represents the handle, or ID, of the objects you're referencing. That's happening because you are taking the output from your rectangle and extrude nodes and passing it to through to your record values. If you're comfortable, you could upload the file here so I could look at it closer, or direct message it to me.
-
It's also hard since when Marionette was introduced (before I came to work at VW), all of the nodes were written to match the underlying Vectorscript calls and nodes mostly just matched the functionality of what already existed. At this point, I've reworked a lot of the library to minimize redundancies and try to make things more user-friendly, but I've tried to not overwhelm users experienced with Marionette as it was originally implemented with big changes. Another tricky thing is making sure that users understand that these dimensions are referring to an object's coordinate system, and not the drawing's coordinate system. When a user is querying an existing object, if it's rotated on the drawing area, they may not realize that they're not pulling from the x/y that they see on their screen. I do like the idea of referencing by x/y/z dims, I just want to make sure it's not MORE confusing than it already is, especially with Marionette being what I consider the "hand-holding" way of custom scripting. I also am an advocate of users eventually migrating to traditional python/vectorscript, so I don't like to stray too far from that syntax in the process.
-
This is an issue I've been trying to find the best solution to. It comes up because in 2D, we reference the Y dimension as height, but in 3D objects, the Z dimension is often considered its height. Some nodes (such as Get Poly Bounds) have been updated to reflect dimensions rather than the confusing terminology. For this node, Height refers to the Y dimension and BotZ and TopZ allow you to set your lower and upper value for a 3D height. If you have any suggestions as to how these can better be defined, please let me know and I will absolutely take it into consideration.
-
Version 1.0.0
11 downloads
I'm working on developing a version of the Compose node that won't rely on the Vectorworks Menu Command since that ends up not always behaving as expected in all cases. I figured I'd share my progress with it. It's not done, I haven't explored all edge cases, and it's possible that it's still buggy enough that you could end up in an infinite loop in some cases. With this in mind, I highly recommend saving your work before testing this node. I'd appreciate any feedback on where it's failing or where you would expect a different behavior so I can add error handling/improvements. The attached file is in 2025 version. I think it would be safe to export back a few versions, so if you're on an earlier version of Vectorworks but would like access to test, let me know and I can upload a copy for that version as well. -
I rearranged some things here - moved the Mix2 node so you only need one, added another filter. Just a quick note on the Print Debug nodes, if you weren't aware, if you put 0 for Max Items to Print, it will give you the input whole list. If you want to suppress the output text, you can disable them (as long as they don't have anything necessary attached to the output port). Figured I'd mention it just in case. Serious script experiments - what is wrong here_MFarrell.vwx
-
I missed another spot that you needed a Mix2. Here's an updated file. It looks like it works. VC Pickerington Campus - fka East - script experiment version_MFarrell filter edited_MFarrell_2.vwx
-
Short answer - the If In String node doesn't absorb the lists, so it's comparing them 1 to 1 and not cross referencing. I'm not entirely sure what I'm looking for for results because I haven't explored your file in depth, but here's a possible fix using a Mix2 node. Let me know if I'm heading in the right direction. VC Pickerington Campus - fka East - script experiment version_MFarrell filter edited_MFarrell.vwx
-
I'm not super familiar with ConnectCAD objects at this point, but I'll ask the tester in that area to try to gather more information. I can't see any reason why you couldn't set a name in the OIP field for them.
-
A quick workaround with native nodes, though not as efficient as writing a new node, is attached here. VC Pickerington Campus - fka East - script experiment version_MFarrell.vwx
-
I was going to suggest a Set Parent node, but apparently we don't have one in default content. I'll make a note to add one later 🙂 Here's a quick one, I didn't test it and it has minimal error handling, but just to have something available for anyone looking (please let me know if someone tests it out) This node will let you set the parent of an object, it can be a layer or a group (or other things depending on object types) Set Parent Node.vwx
-
dennisliesenhoff started following Marissa Farrell
-
Version 2025.0
25 downloads
How to Use the Marionette Script: Step 1: Install the Pillow Library The script requires the Python library Pillow for image processing. If you’re unsure whether you’ve installed it before, you can safely install it again. To install: 1. Select the Install Pillow node in the script. 2. Click Run in the Object Info Palette (OIP), or 3. Right-click the node and select Run Marionette Script. Step 2: Add Commands to Your Marionette Command Library To make the script easily accessible: 1. Right-click on each wrapper. 2. Select Convert to Menu Command…. 3. Name the command as you want it to appear in the Tools > Marionette Commands menu. Step 3: Use the Commands 1. Select an image (bitmap) on your drawing area. 2. Navigate to Tools > Marionette Commands > [Your Command Name]. 3. Test with sample bitmaps provided in the file’s Sample Images design layer. Special Notes: • Running Commands: Important: These Marionette Wrappers cannot be run directly from the drawing area because they act on selected objects. You must run them from the Tools > Marionette Commands menu. • Installing Pillow: The Pillow library will be installed to your User Folder. If needed, reinstall it using the provided Install Pillow node. • Image Import Settings: For the AI to Prop commands, always import images as JPEG. Importing as PNG will cause display issues. Use the AI to Prop with Dialog command to manually adjust import settings if needed. Once configured, the non-dialog version will reuse the last settings automatically. • Temporary Files: The script creates temporary images in your User Folder. These files can be deleted at any time.- 1 review
-
- 4
-
-
- marionette
- texture
-
(and 3 more)
Tagged with:
-
It should be in 2023, I see it as far back as 2022 (that's the oldest I have on this computer) and the comments inside mention a date of 2017, which means it likely was in 2018's release. Can you send me your file, either here or in a message?
-
It should be in default content, in the Input > Basic folder. Called "Color Input" Which version are you using?
-
If you want to avoid drawing and deleting extra objects: For text, you'd use the Set Line Attribute node with the Pen Fore color.