Jump to content

Marissa Farrell

Marionette Maven
  • Content Count

  • Joined

  • Last visited

Everything posted by Marissa Farrell

  1. It looks like you aren't getting values returned from your Get Record Field nodes (They are resulting in "<Unknown Value>"), which will affect the rest of your network. You can see that you have wires coming out of your Filter nodes that have 0 items, which will prevent the network from running correctly. I would suggest looking into why values aren't being returned appropriately from the Get Record Field nodes and going from there.
  2. The issue is that the file name for line styles is translated in non-English versions. You should be able to change the filename in the node script to what your file is named and it should work.
  3. Are you in a non-English version of Vectorworks? I've learned that my network may only work with English. I have a node in progress that will work in any language.
  4. No problem! I think it's really close to what you had before, I just seem to have lost at least one node when moving things around. Creating a red symbol is easy - when creating a symbol from a Marionette Object, in the Symbol Options dialog choose "Convert to Plug-In object" You can also change an existing black symbol to a red symbol by right clicking on the resource in the Resource Manager and editing the symbol options from there. Let me know if you have any questions 🙂
  5. If you name the Popup List node in the OIP with a name, it should appear in the OIP when converted to a Marionette Object.
  6. Ah - I forgot to mention the step where you delete the line at the very top that starts with #COMMAND. If you delete that entire first line, the script/node will update.
  7. This file has a lot of problems with it, and I'm having a hard time believing it's a native 2018 file since many of the nodes are from earlier versions of Marionette resources. If you enter the symbol and edit the script, the Marionette object displays an error when exiting edit mode, it then displays an object that doesn't look like the symbol did before edit (but does appear to look the same as if you copy-pasted into a new file) I think your Marionette script is corrupt, and there's not much anyone could do about it without rewriting/rewiring the whole thing. I've made some progress rewiring it, but I don't know enough about the object to finish it up. Right now, it does appear to be pasting correctly into a new file. The revised symbol now has "rewired" appended to it. I also changed it to a Red Symbol, which will insert it as a Marionette Object instead of a 3D Symbol. I also changed some of your Int nodes to Dim nodes so that it works better when changing document units. Onderkast 3 fronten check_MFarrell cleanup.vwx
  8. @fpaniz Are these generic solids created in Vectorworks, or were they imported from a different file type?
  9. Yep! So the Popup List node is a template for users to edit to make their own lists. You can add/change the "Choice 1, Choice 2, Choice 3" and add more items to that list as well. The outputs will start at 0, so if Choice 1 is selected, 0 will be the output. Does this help?
  10. Hi @Onink I'm looking into this right now, but I have a question first - which version of Vectorworks was this originally created in? I'm working on reorganizing your nodes (they all got stretched out) so just wondering if this was created in 2018 (which is the version it appears to be last saved in) or in an earlier version. Thanks! Marissa
  11. You can save the Marionette Object as a Red Symbol in your Resource Manager which would allow you to insert it into other documents (you could save this file to your user folder or to your Favorite Files for easy access) When creating the symbol, make sure "Convert to Plug In" is checked in the Symbol Options window to make it a red symbol instead of a black symbol.
  12. Marionette Objects are the closest thing to a PIO that a Marionette script can be automatically converted to. You can export the Python script for the Marionette Object with the context menu command and create a PIO from it with the Plug In Manager, but the code in there is pretty ugly looking and nearly impossible to read to edit later (also not optimized at all), though it might be what you'll need to do to accomplish this. (I'm not positive if you first need to convert back to a wrapper node prior to exporting the Python script.)
  13. Hi! Could you send me this file either as an attachment here or privately? I can try to take a look.
  14. @CollaborativeMT Are your objects on the same layer? I believe it's necessary that they are in order to run the command. By grouping them, you force them onto the same layer which is why that would work.
  15. @gguerriero Looks like it's still being worked on by the engineers. It's been marked as a critical bug, so hopefully a solution will be found soon.
  16. My understanding is that editing the record attached to a symbol definition will only apply to symbols added to the document after the edit, not existing symbol instances in your drawing.
  17. In addition to Mark's suggestion - here's a Python script that will find all of the 3D polys on the active layer and replace their center point with a 3D locus. My limited testing leads me to believe it works fine 😛 lName = vs.GetLName(vs.ActLayer()) def createLoci(h): (p, zValue) = vs.Get3DCntr(h) vs.Locus3D(p, zValue) vs.DelObject(h) vs.ForEachObject(createLoci, "((L='"+lName+"') & (T=POLY3D))")
  18. Can you provide a dummy file with a small subset of these objects?
  19. You can run the command Tools > Utilities > Reset All Plug-Ins to force an update.
  20. I think Marionette is a great solution to this problem and I would be happy to work with you to get this started.
  21. In your screenshot, your attributes palette is at the bottom left of your screen. With your slab(s) selected, if you click the button that has "100%/100" you can adjust the opacity there. (The attached image says 10%/10% because I changed it for testing)
  22. Following up on this - it appears this is by design, based on another reported issue. Object opacity is no longer controlled by style, so you'll have to use the attributes palette.
  23. Thank you! I do see that the opacity settings do not appear in 2019 vs. 2018. I'll put an issue in, but for the time being, you can use the attributes palette to set an opacity for your slabs. Hope this helps for now!
  24. I'm able to change the transparency of slabs using the Attributes palette. How are you trying to change the transparency? What version and service pack of Vectorworks are you using?
  25. Yep! The tuple node is just a modified float node, I didn't even update the description (oops!) Its only purpose is to convert a list type into a tuple type.


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...