Marissa Farrell

I'm just stumbling across this now. Here's a file that should help you along. Please let me know if you have any questions. Circles from WS Values AF add record_MFarrell.vwx

The reason that is exposed is because you've named the nodes. Named nodes will be exposed in the OIP for objects. You could label them with a text object next to them.

Are you using the menu command at File > Import > Import Image File(s)...? That should bring you to this dialog after choosing the image file in the browser From there, you want to make sure the top dropdown is set to Bitmap if you want it on the drawing area (or you could do Bitmap and Image Resource)

Thank you, good catch. The SetListAbsorb() is what is causing the failure. I'll get a fix in as soon as I can. For now, the node in this file works. valve_fixed.vwx

Does the import work well when done manually? Were the Marionette resources created in the same version as the version you're running the script on, or were they brought forward from an earlier version?

it will depend on the complexity of the string. Can you give some examples of what the strings would be?

I believe ComputerWorks is correct, hole cutting objects only work on walls and maybe roofs(?); you will have to manually do the cuts. I've been cleaning up the networks in your file to simplify them, you should be able to use them as references for other ways to accomplish things moving forward. I didn't get rid of your ungrouping at this point because i need to understand more about it. It's difficult working with your file in some ways since it seems you've created Marionette Objects within blue symbols. I'm having a tough time quickly determining where everything is coming from, and when I attempt to edit your blue symbols, parts are disappearing and I'm not sure why. I would suggest looking into saving Marionette Objects as Red Symbols instead of throwing them into groups and creating Blue Symbols. I'm attaching a file that seems to work with the Rondo symbol, but the other two Marionette objects within the symbols need some tweaking because they don't seem to be rotating correctly. I added a layer called Marissa with two Marionette Objects that show some ways to simplify your scripts, hopefully this can give a starting point on some things to at least modify your logic. I'll try to find some time to do more digging. spots_v2026D_MFarrell_v2025.vwx

I'm looking into this, but a note I'd like to make - I wouldn't use Ungroup nodes before your apply texture, I would use Contents nodes. There's no real reason to ungroup things unless you're trying to operate on their locations differently, just changing attributes won't necessitate this. You're right that this has to do with different coordinate systems, and it has to do with how you're ungrouping everything and filtering out objects, some objects are being left in different locations and that's messing with the referenced points.

Yes, the Button, Radio Button, Popup, and Slider nodes that we ship are all essentially template nodes so that users have easier access to starting points for those OIP controls, although the latter three can be modified directly and used in a network as-is.

can you provide a sample file?

I think the primary reason we haven't included them is because they universally won't work, they'll only work in Marionette Objects, and we don't want users to be confused by their accessibility. There are a couple of other nodes that are restricted to use outside of running straight from the Design Layer, and those are Control Geometry, Control Point nodes (2D and 3D), and Set Selection, the 3 first are for use only in Marionette Objects, and the last only works in Menu Commands. (I may be forgetting one/some, but I don't think so?) When a network is run on the Design Layer, it does a fun traversal up and down the network to build the script out, and it's not really predictable. I have yet to figure out exactly how to make it generate in the same way every time. (I would guess it has to do with which node you had selected when choosing to run as well as the stacking order of the nodes attached to the selected node, but I honestly have no clue, I just know it's complicated and fussy.) The suggestion to group and ungroup is still a good one; the only other thing I can think is to make the network more linear with less branches, but the way a lot of our nodes are created won't really help you there, and I can't see a good way to rewrite the nodes to accommodate that, either.

Can you share your file so I can take a look? Marionette networks are difficult when it comes to stacking because the order the traversal up and down the network isn't really straightforward, it often works better when you create a Marionette Object to make sure what you want is on top, but once I have an idea of what you've done, we may be able to work around that if a Marionette Object won't work for you.

The output of the mirror node only outputs one object, the mirrored object, so only the object that results from the mirror will change color. If you want to also color the original, you'll need to wire from your input object to the attributes node as well.

You can certainly export the Python file and use it, but it's not very efficient. There's are a few discussions about it, I've linked two below. Unfortunately, exporting the script will result in a bunch of lines of code and logic that doesn't always play out how you want. If I were to approach it, I would copy the guts of the nodes and write my own PIO script.

Did you manually create those polylines? This can certainly be done, I'm just trying to figure the best way to guide you through it.