Jump to content

Luciole Design

  • Posts

  • Joined

  • Last visited

Everything posted by Luciole Design

  1. AutoTURN looks expensive, and I don't do enough of this to justify the cost. Although it could be reasonably priced, but the cost is hidden because AutoTURN makes you fill out a full contact form just to get a price. I really don't see the point of getting email forever just because I wanted to see if it was affordable. Anything else that's simpler and included with VectorWorks?
  2. BRANCHING: I get the same crazy results as you. Vwx does say something about strange results in their help page... right they are! I think the discrepancy between manual calcs and vwx is they seem to use more inline drip, even though the border is a different class for the lines (no dots). I add a note saying to divide the drip zone area if needed, and ignore the drip zones, just in case. The numbers seem close enough, and I'd rather vwx estimates higher than lower. Not sure they can fix this - I remember something about looped lines being very difficult to calculate for computers. I think "branching" means connected at both ends of the drip in a loop (pvc or poly at the edges, water can flow from both ends of drip lines). That's not a great term - misleading, since branching usually means like a tree branch, at least to me ("divericating" in biogeek speak). FWIW, I place drip emitters at the plants and link with poly tubing wherever I'm not using a grid. Maybe someone from vwx can chime in on this? Fixable or better to simply eliminate the botched "branching" option?
  3. Funny, I ran the terminal command on the zip file to de-quarantine it and got the same result as before. Maybe you have to run it twice, once for the .zip file and once for the unzipped library file? Still, Vectorworks says "incompatible with this version" so it must be seeing it and trying to run it... Thanks for your help! At least it's a known bug and will be (has been) fixed!
  4. I'm going to wait for SP2, where the bug will hopefully be smashed. For now, it seems that drip zone polygon size and complexity affect the crash, so I deleted the zones that caused crashing and re-drew multiple zones in the same area, then linked them with lateral lines to the valve. Not foolproof, but it did reduce the number of crashes and let me finish laying out the drip zones. The patch has problems with Apple (unsigned? possibly malicious code) and VectorWorks (incompatible plug-in with this version of vwx). So expecting Apple to sign a plug-in and Vectorworks to do a recompile is beyond delusions of grandeur, and these things will be done for SP2 anyway, I imagine. Thanks for all your help!
  5. Anyone know how to apply the correct symbol for irrigation heads (get it to "stick")? When I pick the correct symbol (1/3 head, standard vectorworks symbol, filled), vectorworks picks a different, wrong symbol (Q head, unfilled). Luckily, the catalog data remains the same. Replacing with a custom symbol works, but it does not rotate correctly, cannot be manually rotated. Or maybe it can, but I don't know what to include in my symbol to create a properly rotating symbol, nor show how to specify the direction to the center of the spray pattern, nor basically anything I'd need to make this work. Workaround (bad): create a custom symbol that does not show arc so if it doesn't rotate, no big deal. Not a great solution, but better than quarter heads for half pattern! OI Palette was my compromise so I could continue working. Yes, I really did want the symbol in "wanted.png"! FIRST IMAGE: Vectorworks (wrong) pick SECOND IMAGE: WHAT I WANTED: My choice from standard Vectorworks symbols THIRD IMAGE: My crappy compromise that doesn't rotate away from the spray pattern.
  6. I did make a duplicate, but it didn't work for some reason. Same errors, but it had a creation date in September so I'm guessing it was the original file.
  7. For what it's worth, the bug affects the Windows version of VectorWorks, too (Windows 10). So no hope in switching to a Windows machine (if you have one)!
  8. Don't install the updated library on a Mac! The thing is unsigned, and won't install. Vectorworks won't accept it either because it's not compatible with SP1! Have to reinstall VectorWorks!!! The solution was worse than the problem!!!
  9. Vectorworks 2021 is crashing about every third time I move the connection point or adjust drip line emitter direction. As per your tutorial, I'm adjusting the drip line before connecting it to a valve. Sometimes deleting the drip polygon and redrawing helps, but the crashes still continue. Most often it's a "beach ball of death forever" freeze, but sometimes it's Flash! Gone! No Vectorworks. Restarted computer. Still crashes. iMac 27" retina 2017, 40 GB RAM, Vectorworks Landmark 2021. Mac OS 10.15.7.
  10. I wish someone at VWX would streamline this process. As is, too clunky to bother with!
  11. I'm not currently experiencing this issue. I get crashes on using the eyedropper, but at least the plant counts seem to be fixed.
  12. Sorry, but I'm on a deadline so I can't spend hours debugging. I just fooled with settings until they came back. Maybe when things are slower... Sorry.
  13. The worksheets are on a sheet layer. There is nothing hiding them, their classes and layers are on, but they will not display. All layers and classes were set to visible. This happens on multiple files. The next time it hits a smaller one I'll send it (this file is rather large with lots of 3D info on a large site. Reality check: if hidden classes/layers were the culprit, how come they magically reappeared when I restarted VectorWorks???
  14. Sometimes worksheets will disappear from a sheet layer. There is nothing hiding them, their classes and layers are on, but they will not display. When I open the sheet, the worksheets flicker briefly, then disappear. The only (bad) solution seems to be a restart of VectorWorks. Does anyone have a better way to make them appear, and if so will it stop them from disappearing again? Restarting Vectorworks is not a fast process! iMac 27", 40 GB RAM, Mac OS 10.15.6 (and earlier). This is a continuing issue from vwx 2020.
  15. Congratulations, Vectorworks! The problem was solved in SP2! Numbers back to normal!
  16. Same problem here. Buggy version much, VWX 2020? How can you buy anything other than multiples of 1 plant? Someone at vwx needs to think about how plants are sold! toggle mass plants on and off - no good. setting file units to "no fractions" - no good. This workaround is ugly, but it works (not our office standards, either - but the plans need to go out!) STEP 1 - set your tag attributes as you wish (ID + QTY in my case). You'll get 2 decimal places, but this is the only (timewaster!) way to select the attributes you want! - Set tag bubble to "RECTANGLE". Wait for vwx to put the correct things in the rectangles. You'll still have the decimal counts next to the boxed attributes STEP 2 - Set tag top, center, bottom display to "NONE". this should make the redundant data disappear. Setting the bubble alone does not eliminate the decimal places. Haven't published or printed, so we'll see if it works on export... what a mess.
  17. Doesn't work for me. No solution in VWX 2019, alas. (Mac). Tried all this and no joy. Reverting to Dropbox folder with files but giving up on making it a workgroup folder (renamed, restarted, etc. etc.) Wasted an hour of my time on this horrible thing and that's enough. I'll just have an accessible Dropbox folder with my symbols etc. inside that I'll just open in VectorWorks and import through the Resource Browser. Nobody else in the office even tried to mess with this nightmare (needs to be simple, not übergeek level!
  18. Seems to be running fine on my test machine, but then I haven't worked on anything very long (yet). Seems to be slow to initialize - should be faster with new file system. Having issues with printing to HP DesignJet PostScript (workaround is open file on other machine or publish to PDF and print that on the other machine). Might be better to hold off a while if you don't want any surprises!
  19. Is the line type layer the same scale as the other design layers? Sometimes you add a layer that's set (somehow) to a different scale, causing it to shrink/magnify out of the viewport.
  20. You can probably extract the data in a new worksheet/report, but that's a lot more work than just opening something up and saying "recalculate". I ended up doing this just so I'd know how the thing works.
  21. I keep a master file with my customized plant symbols that converts to the new version of vwx. Kind of cludgy, but at least I know where everything is and I'll be able to find my plant symbols. They're updated to the vwx plant database, too. I'm not a huge fan of the Filemaker runtime / Vectorworks UI for the plant database. One workaround is adding a period after the plant name so I can have two versions of a plant in the database (one with my local data and another with vwx national data). Since we do a lot of sustainable / native plant design, we add a LOT of plants.
  22. Has anyone had trouble viewing VectorWorks webinars? I can't get any of them to load on any Mac browser. No dates and times are mentioned in the text, there's no message saying when the videos must be watched, so I thought they streamed on demand. Perhaps not... I received notification of a webinar on October 31 that might have only been available October 26, but that doesn't make sense! Error loading media: File could not be played in Firefox, Safari and Vivaldi. Play triangle does nothing in Chrome. test: http://www.vectorworks.net/inspiration/industry-webinars/site-viz-site-design-visualization-using-vectorworks?utm_campaign=webinar&utm_source=planet.vectorworks.net&utm_medium=intext (Mac running El Capitan)
  23. Anyone know if 2017 SP1 added Mac Sierra compatibility? Can't find this information anywhere. Some release notes would have been great, but no link, no notes so far.
  24. I'm getting crashes while working in 3D on relatively small files, especially when playing with Renderworks textures. It also seems to crash when updating referenced files, importing vw2016 files (some), working with smart objects (some) and sometimes for no apparent reason at all. Luckily the backup files seem to work, but it's still annoying. Bottom line: set the autosave to a time frame short enough where you don't have too much déjà vu redoing things, save often and backup everything... and hope the Sierra compatibility update makes VWX 2017 more stable!
  • Create New...