Sky

Member
  • Content count

    101
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Sky

  • Rank
    Journeyman

Personal Information

  • Occupation
    Architect & Interior Designer
  • Homepage
    www.schismdesign.com
  • Hobbies
    Restaurant, retail, commercial office, custom residential.
  • Location
    Los Angeles, CA, USA
  1. I was doing a bunch of renderings overnight of a restaurant, and in the morning I found that VW2017 was paused by Mac OS Sierra because of low memory. Looking at the Activity monitor, I saw that it had used up most of the 16GB on my Mac Pro (Late 2013). I upgraded the computer to 64GB so I wouldn't have that problem again. Last night I was doing a solar animation of a community center and again it paused because of low memory. How could Vectorworks possibly use up 64GB of memory? I tried doing a smaller animation on my MacBook Pro (15-inch, 2012) with 8GB RAM and the Memory Used topped out around 6 GB without any swapping and stayed that way until it finished. I tried a similar rendering on my Mac Pro and the Activity Monitor Memory Used slowly crept up from 14GB to over 22.3 GB by the end. Even after the animation was finished, the Memory Used didn't go down. Is this a memory leak? Why would it affect my Mac Pro and not my MacBook Pro? Has anyone else seen this problem?
  2. It's not working for me either. It was one of the best features they added too. It used to work. I don't when it stopped working correctly. But you are right, I restarted VectorWorks and it worked again. Wonder how long it will last before I need to restart it again.
  3. Thank you! I will give that a try.
  4. I've been using 2017 for a couple of weeks on a project and it's been a problem. 1. It crashes. A lot. Multiple times a day. 2. It is soooooooooo laggy! Cutting and pasting. Panning. Everything. When I go back to 2016, it is noticeably different. 3. Sometimes I do something (join walls, resize something, etc.) and it still looks like I didn't do it. But when I force the screen to refresh (zooming out or in) it shows correctly. I don't think I have ever been so disappointed with a VW upgrade as I am now. Are these known issues? Will these be fixed?
  5. People having problems printing to Canon printers should publish to PDF or print to PDF and then use an app like Preview to print. I have not upgraded yet, but I am itching to do so.
  6. So I upgrade my Designer + RenderWorks every year. If I am interpreting the website correctly, if I join Service Select, it will include the 2017 upgrade when it is released later this year? And Service Select is actually cheaper than buying the software every year?
  7. Thank you! That was tremendously helpful!
  8. Does VectorWorks use mostly graphic card processing or computer processors to do renderings? Will upgrading to a 3440 x 1440 monitor that uses 2 thunderbolt connectors from a 2560 x 1140 that uses 1 thunderbolt connector cause a slow down of my renderings? Any insight into this would be greatly appreciated! Sky
  9. That was a great tip. I set the jamb to a class that isn't used in the renderings and the white lines went away. Thank you!
  10. I think I know what was wrong. I originally made this drawing in v2014. I importing to v2015. Then I imported to v2016. Somewhere along the line, it corrupted the stairs. I deleted all the starts and remade them and it is fine now. A lot of extra work though...
  11. This is driving me crazy. I"m working on a 3-story home and If I highlight a stair and click on settings, nothing happens. After that, I can only select objects by using a right click. But nothing works right at that point. I can't quite the app either. I have to use Force Quit. When I open the file, I can work with everything else fine. It is only after I try to edit a stair (any one of 5 stairs in the file) everything goes bad.
  12. When I change stair graphic attributes, Vectorworks becomes unusable. Going back into the stair settings, the pop-up window is incomplete and unusable. Selected objects, if it allows you to select anything, will not appear in the Object inspector. I need to force quit as simply quitting doesn't work. I have confirmed this by doing it twice and creating a new file with only a few objects in it. Only when I change the stair graphic attributes by making the 2D Treads to the class line and fill settings (Vert Trans-Main), does the whole thing go crazy.
  13. Check out the kbase article: http://kbase.vectorworks.net/questions/1362/__unhighlight
  14. Really, really need this...
  15. I just came across this thread because I was just working with storefronts in a wall and wanted to know if there was a good way to dead with this. What I ended up doing was putting a Door "Opening" into the wall and then placed the curtain wall into that opening. Has anyone found a better way of doing this?