Jump to content


  • Posts

  • Joined

  • Last visited


154 Spectacular

Personal Information

  • Occupation
    Vectorworks Design, Presentation & Construction Drawings
  • Homepage
  • Location
    United States

Recent Profile Visitors

2,036 profile views
  1. When run, the wrapper in the attached file (VW 2021) produces the window trim as expected. But when I go to convert the wrapper to an object node, I just get the spinning beach ball and need to Force Quit Vectorworks. It doesn't seem like there's anything wrong with the network, since it runs successfully, so I'm not sure what I'm missing... Any thoughts greatly appreciated. Thanks! VWIS220 02-Object Node Crashes VW.vwx
  2. Okay, thanks. Sadly, I've had no luck searching the web for tutorials on Vectorworks Python. I wish Marionette would just work. A network that I've been working on runs fine, even when wrapped, but crashes Vectorworks when I go to convert it to an object node. I feel like whichever way I turn there's a dead end: Marionette is dysfunctional, and it looks like scripting will require a tremendous investment time-wise to learn (which I wouldn't mind if it weren't for the financial implications, especially after having already invested so much in Marionette). But I digress!... Thank you Pat for your feedback; I appreciate it.
  3. Do I need to download the Python software / "interpreter" and Mu, or are these functions provided via Vectorworks' Script Editor? It looks like Python code lines start with " >>> " where in Vectorworks they don't and/or they starts with " vs. "? I guess the question is, do I want to learn Python within Vectorworks, or through the Python website? Thanks!
  4. Thank you Pat, that is all very helpful. I've been looking at Vectorscript out of a fear that Marionette's issues stem from Python. But maybe it's safe to say that they don't, and that Marionette is dysfunctional on its own? I've heard of Pascal before (and there you have a synopsis of my experience with it...). Not sure I really followed your last paragraph; it sounds like Python isn't perfect, but I will check it out. Thanks! -Will
  5. I'm so frustrated with the instability of Marionette, that I find myself looking in these Vectorscript and Python forums, though I don't know what the difference between the two is or which might be best for creating parametric objects (or plugins?). I think Python is used for Marionette? I like the "approachable" graphical interface of Marionette - the colorful nodes and connecting 'em with wires is fun - along with its ability to (sometimes) create extremely useful objects. But if only it worked more often than not...
  6. That worked great in the file that I sent you! But not so much in my original file (attached).... When I changed the "s" to an "i" in the file that I sent you, I got a dialogue box about a "REFFILE keyword" (see screenshot in attached file) to which I said "Yes." When I went to update the node in my original file, the "s" had already been replaced with the "i" (which I assume has to do with the "REFFILE" thing...). But the network failed... Ultimately, I found that if I copied the node that I'd originally modified and used that, the network would succeed and generate the expected solid. The attached file displays the steps I went through. It also includes a screenshot of a warning that I frequently get. And I've noticed that the Scale Symbol node has a red gradient in the RM, but in the file it's just white... don't know if that's significant. VWIS219 Thanks! Will 05-Scale Symbol Node-02.vwx
  7. When I use the "Solid Boolean" node to try and combine two symbols, one of which is scaled, as a solid addition, it doesn't work. If neither symbol is scaled, a solid addition is generated as expected. See attached. How are scaled symbols added together with Marionette? Thanks! 03-Add Scaled Symbols-02.vwx
  8. I couldn't for the life of me figure out how to make a rendered viewport grayscale... this did the trick. Thanks!
  9. Wow, looks like I first encountered this issue (VWIS008) in 2013: Currently, the problem seems to occur after editing a 2D symbol on a design layer. @GWS said "The whole Layer/Screen Plane issue has never really been resolved, it's so far behind other CAD programs. Even the less expensive end of the market has this sorted. It is basic structure like this that is holding VW back in the market, and indeed from the user point of view." And that was in 2013!!! EIGHT YEARS LATER and we're still struggling with Layer Plane, Working Plane, Screen Plane, Screen Aligned, Symbol Definition, 3D, Extrude Along Path. Holy cow!!! In the meantime, could we PLEASE have a REAL & PERSISTENT ability to select "Working Plane Only" in the Plane Mode options of Document Preferences?!?!? Please!!!!!!!!!!!!!!!!!! VWIS008
  10. The beauty of Styles was that you could have, say, sixteen different window Types (different sizes, different operations), as symbols, all using the same Style. Then, if you wanted to change, say, the trim width for ALL of the windows in a project, you could do so globally via the Style. To use Styles like symbols (as I think you're suggesting) defeats that beauty entirely, as it would then be necessary to update all 16 window styles in order to change the trim width. I've just tried adding Tags inside the symbols - one in plan and one in 3D for each symbol. Works fine for the Floor Plan drawings, but the most I can get to show up in an Elevation (Section) Viewport is the hexagon, and not the text, even with "Display Text and Markers" selected. Worksheets and the Modification and Selection tools can find things in symbols; I wish Data Tags could too.
  11. How do I make data tags recognize window PIOs that are inside of symbols? Thanks.
  12. Hmm... I have my RM just floating on a separate, small monitor, always visible... Also, speaking of the RM, thumbnails seem wonky. Often after editing a resource, its thumbnail either disappears (blank white) or changes to some scale that's not especially meaningful. Textures sometimes seem to be represented just by a black-to-gray gradient.
  13. I wish it wasn't necessary to scroll down to "Locate Symbol in Resource Manager" when right-clicking on a symbol that's too close (which isn't very close) to the bottom of the drawing area (because the pop-up context menu doesn't simply shift up to be entirely visible). VWIS066 (2016) I wish it wasn't often (or always?) necessary to right-click on a symbol and select "Locate Symbol in Resource Manager" TWICE before it's actually highlighted in the Resource Manager. And currently I'm trying out the "dark mode" thing, and finding that the highlighting, once activated, is barely visible anyway (but maybe there's a setting for that that I'm not aware of). Either way, really wish it wasn't necessary to have to always go through the symbol locating process twice. VWIS180
  14. Why do I keep losing the ability to access a window's settings? There's no response double-clicking on a window, right-clicking on its style in the RM, or clicking on Settings in the OIP. It seems to start - inconsistently - when working in a window's symbol. The only solution seems to be closing and reopening the file. Not super efficient having to constantly close and reopen the file in order to work with windows.
  15. Why has Vectorworks recently taken up reverting to Screen Plane? I'm finding every third thing I do is wrong because I think I'm working in Layer Plane mode, in 3D, no need for screen plane, don't WANT screen plane, but it just keeps randomly deciding that Screen Plane is right for me. It's NOT!!!!!!!!!!! I KEEP telling the software, in Document Preferences > Plane Mode that I want "Working Plane Only." Repeatedly. Over and over. Why can't I, as the user, decide which plane mode I want to work in??? Am I missing something? Probably... after several days of fighting with Marionette my patience for VWDW is pretty limited...
  • Create New...