Mark Aceto

  • Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

Personal Information

  • Occupation
    Producer, Technical Director
  1. Reporting back here with some findings... Been using an iMac Pro 3.0Ghz (10-core) 64MB Vega 64 (16GB) machine for a few weeks now. Haven't tried rendering yet but I can confirm that I frequently get the spinning beach ball of death "Application Not Responding" message a lot (Activity Monitor reports the good old "using 100% of CPU"), so I can say without a doubt for any work that you're doing in design layers, get the fastest single-core clock speed CPU that money can buy. And do all of your rendering in Cinema (or app of your choice). VW is absolutely CPU-constrained on a single-core before you ever get to the part where you render on multiple cores or, hopefully, GPU. That said, if you're on a Mac, you can't have both: it's either clock speed (iMac) or GPU (iMac Pro) for now.
  2. @Kevin McAllisterEditing, panning, zooming... all have huge lag, and will redraw the geometry (along with the weird ghosting you mentioned above). All of my colleagues are experiencing the same thing. We fly through 3D modeling on design layers, and dread plating the sheet layers because Vectorworks comes grinding to a halt. It feels like pan, wait a second. Double click, wait a second. Zoom, wait a second. That's why I thought the issue was with the graphics card but a 1080 Ti didn't help much.
  3. Thanks, Jim. This is extremely helpful, especially with all of the conjecture surrounding this issue. Last question: are there any best practices for not making this issue any worse? For example, fewer viewports on sheet layers, reduce textures, wireframe vs openGL vs hidden line, sheet layer page size, viewport DPI...? I've made a habit of dimensioning as much as possible on a Dimensions design layer (in plan view) so it's one less cause for annotating a viewport on a sheet layer. Likewise I've started annotating notes and callouts either on design layers, or on top of viewports on sheet layers---basically anything to avoid editing, panning, zooming or just plain working with a viewport on a sheet layer at all. Just stabbing in the dark here but if there's anything I can do on my end to speed things up, and make life easier by working around this issue, please advise.
  4. OK, and just for clarification: GPU won't help... until Vectorworks 2019? This limitation is not Mac-only
  5. Sorry, that must be slang for Sheet Layers: light plots, ground plans... It seems particularly slow when I have 3+ viewports on the same sheet layer: plan, front, side, iso... So I'm looking for a solution to make that part of VW go faster (until it moves to the GPU).
  6. So what's the solution for working around the issue of VW slamming on the brakes as soon as I start plating? Assuming the same maxed out GPU, RAM, SSD, would you recommend: i7 4-core 4.5Ghz W-2145 (Xeon) 8-core 3.7Ghz W-2155 (Xeon) 10-core 3.3Ghz Something else? I'm trying to find a balance between modeling, plating, and rendering speed in my workflow. I recently built a Mac Pro 5,1 12-core 3.46Ghz system with a 1080 Ti, 64GB RAM, 1GB SSD and 2x 4k displays. 3D modeling speed was great. 3D rendering speed good. Plating was as slow as ever. Assuming top/plan view etc. will move to the VGM by 2019, around the same time the Mac Pro is released, I'm really just looking for a solution for the next year or so. BTW I'm fully aware that a Windows machine would be a better solution (especially for the money) but I'm stuck on a Mac for the near future.
  7. @JimWhas top/plan view moved over to the VGM in 2018 yet?
  8. @JimWthis is super helpful. What are your thoughts on the 16GB Radeon Pro Vega 64, and the upcoming iMac Pro compared to the Windows workstation described above (other than the Mac being ridiculously overpriced)?
  9. Unibrow escape key for when I try to render on a Mac
  10. @Andrew Daviesadding to @michaelk... It's really an organizational vs. presentation distinction. I typically abbreviate viewport names to organize my drawing in a nerdy systematic hierarchy (similar to classes) for quick sorting and searching: Plan Overview Iso Left Iso Left Persp HL Iso Left Persp GL Front Stage However, I prefer to title drawings with natural language to improve readability for clients and collaborators: Overview Left Iso Left Perspective Left Perspective Render Stage Elevation
  11. @JimWwhere is the constantly visible field?
  12. Yep. Looks like they also added a subtle artistic style to the edges. However, the more salient point is that we still don't have Tyler GT truss symbols yet. Upstaging just drew their own cad blocks from scratch. Top of the wish list.
  13. Is there a way to render a projector cone with lit fog in the same manner as a light beam?
  14. @sidram Good to see you hear, Jamie. @nathansmith50 I'd love to check out those Layher scaff symbols, so I'm going to PM you. Thanks, Mark
  15. For dead-on views -- Top, Front, Back, Right, Bottom, Back -- I spend most of my time using ortho. However, for Iso views, I spend most of my time using perspective. I would never want to impose my preferences on other users' workflows but adding the option to leave a narrow perspective on would save me a lot of time and frustration by allowing me to focus on the work itself instead of constantly fiddling with the interface. Thank you for adding that feature to the wish list. It seems like that preference would be a natural fit in the main toolbar, right next to the Standard Views picker.