Sky

Member
  • Content count

    107
  • 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'm looking at it more carefully, and I think they are auto rotating. But the cross planes are causing it to cast shadows on itself. I tried unchecking Cross Planes in the image prop, but it is still showing as cross planes in 3D. The other option would be a way to turn of shadows for the plants, but I haven't been able to figure that out either.
  2. I made a simple file with 4 plants and a viewport with a 3D view. Landscape_Test.vwx
  3. Thank you for your response Alan, but I'm not sure how this helps me. When I do a 3D rendering, they are clearly not rotating towards the viewer. I don't have a lot of experience using plants in Vectorworks, but I have used image props many times and never had a problem with the image prop not rotating when the option is checked.
  4. I'm trying to get the plants I've placed into the site to auto rotate. The 3D Graphics image prop has Crossed Planes and Auto Rotate checked off but it doesn't rotate in my renderings. What am I doing wrong?
  5. Vectorworks on my Mac Pro is not releasing the RAM after it finishes a rendering. So if I do multiple renderings (or an animation), it keeps taking more and more until it runs out and pauses all the apps. Right now, I render a few and then quit the app to free the RAM up before doing more. This does not happen when rendering with the same file running on my MacBook Pro. I'm running 2017 SP4 on both machines, but this was occurring before SP4 was released. Both machines are running MacOS Sierra 10.12.6, although at the time it was running an earlier version of Sierra. Still has the same issues now as it did back in late May.
  6. Is no one else having this problem? I find that Vectorworks is not releasing RAM after a rendering is done. So when I render multiple view ports, the amount of RAM consumed by Vectorworks just keeps growing. I have to render a few then quit the program to get it to release the RAM, then restart it again and do more renderings. I've had times where it pauses overnight when it runs out of RAM.
  7. 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?
  8. 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.
  9. Thank you! I will give that a try.
  10. 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?
  11. 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.
  12. 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?
  13. Thank you! That was tremendously helpful!
  14. 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
  15. 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!