Benson Shaw

I checked the resource mgr just noe. Any category labeled User contains duplicates of each file. The enclosing folders are not duplicated. All vwx libraries seem intact. I have vague memory of a balky install first time and therefore reinstalled, so your double migrate idea is likely correct. Could have been a cpu sleep interruption? -B

My template file list shows double of every migrated Use rtemplate. Templates in the vwx Default folder seem OK. The User templates seem to be exact duplicates. Previous upgrades did not produce such dupes. I intend to delete the originals from the template library. Anything dangerous to file structure about that? -B

"Urgh" Exactly! I think maybe useful for cabinet box design? I seldom create points landing on a grid. -B

@mjm Probably class title to suit. Maybe post an example if you find one that works for yo?. Have not seen post from @CipesDesign for quite a while. Retired? Anyway, I quite miss his insights. -B

It's most likely pilot error. I have experienced this poly tail as well. Solved somehow over the years and almost never cause it anymore. Some trouble shooting to consider: With NURBS, or other 3d Polys, the end snap can inadvertently go to layer plane instead of intended end point. OR Test adjust the snap box size up or down in vwx prefs. (A bit bigger might allow some tolerance?) OR Another long shot idea is if you have snap to grid enabled, your final snap may go to grid. Good Luck! -B

Reviving this thread to plead for mercy and good will. Here is some marketing discription from vwx: " . . . the Marionette tool provides a visual scripting interface, allowing inexperienced users to quickly understand and create complex scripts in the Vectorworks program without needing to understand the underlying programming language, Python. ..." Looks like v2026 has some marionette node improvements. Hats off to that! I'm no expert, but have had some successes none the less. With that in mind I have been trying to convince some other long time vwx users to "be not afraid", and give it a whirl. But the hurdles! One really basic architectural element is the rectangle. The default node did not find any improvement yet. It is a node that many would try as a starter, then immediately hit the wall. Then what? Watch a 30 min video? Not happening. Please! Could we have some love for this node? Or keep it as a legacy node, and add a new one, with features similar to Dom C's Enhanced Rectangle. -B

No clue why that happens, but possible workaround: draw the shape with polyline tool in basic toolset, then right click the shape>Object from Shapes>Landscape Area>assign your style -B

Thanks @E|FA , yes v2026 is shown as the default for vwx files. I prefer that the older version file icons remain in their context with only the v2026 files showing my new icon. I can change the new files individually for now. I think I must have missed a step somewhere in the icon conversion. I did restart the Mac and vwx v2025 and v2026 (obviously closing one prior to open the other). still trying stuff -B

@Francois Levy Thanks for that. Copy/Paste my new graphic from design layer directly onto the icon in the app Get Info pane easily changes the doc icon. My new icon does not include the background rectangle and is only a bit larger in the doc, which I consider a feature rather than a problem. but New vwx files created/saved with my v2026 retain the original black/white icon. I would prefer that the new files adopt my new icon. Any advice, anyone? -B

I can select a marionette object on the design layer and adjust the parameters in OIP. Object updates in real time, eg sliders and other input fields cause the model to adjust. Problem is, the object is selected, therefore highlighted. The highlights are not desirable, esp if demoing, or examining for edits, screen capture stills or videos, or etc. Must be something basic here I'm missing. Here are my dubious solutions. Anybody have better methods? tips? One solution is to disable vwx pref for selection highlights. Rather annoying, as it may need enable for effective design layer work. Also, the bounding box handles are still visible. Bad for viewing, stills, videos, etc. Another solution is to make the Marionette Object into a Symbol, then place an instance on the design layer and edit the symbol definition in a slit or floating screen. On a laptop (demo for client?) make the floating screen really little. This requires back and forth mousing between the two screens with additional clicks needed to reselect if symbol definition is deselected. Thanks! -B

Drop a stake … doh! @twk said it first. Adding that Send To Surface might be needed. For me anyway sometime the stake snaps to layer plane. -B

Hi, this file contains a Marionette node for Duplicate Circular Array in v2026, which is not yet in my possession. Please convert to v2025 or earlier. Thanks for any help! Circular Array.vwx

A few comments here: Recently spoke with an undergrad architecture major at University of Washington, Seattle. I asked which software they were learning/using for classwork. Answer, to my surprise, was Rhino. Whoa! I'm no fan of subscription software, but the company does its planning and sets policy, so we need to deal - accept the terms, or protest, or stay with current version and software (an option for now), jump to other software, etc. So hats off to commenters here. It all helps individuals make their decisions. One thing I have not seen here (or maybe it is buried back on page 6) -- Vectorworks was, for years, a low cost option with serious capabilities. Long term users saved a bunch of money over the years compared to others in the industry paying to keep current with AutoCad all those years. Not much consolation if one's budget is planned with the earlier, lower cost structure. Once the subscription model is fully implemented I do hope for a plan that allows occasional access to files after one ends the subscription, especially in instances of semi, or even full retirement. One might get questions from former colleagues or customers, or want to play around with the old files, or hobby wise experiment with new features, or export to other format. I'm thinking of a short term rental. Maybe metered? Open the software, eg in a browser, open your file or create a new one, to do whatever for a few minutes, or hours. Weekly/monthly rate? I know, this could be used as an exit strategy for those moving to other software, but it's not dissimilar to sending old files to a current user and asking for an export, or for a multi seat office keeping one vwx subscription active until all the old jobs are converted to the new office setup. OK, more of me going blah, blah, buuulah. -B