Jump to content

Mark Aceto

  • Content Count

  • Joined

  • Last visited

Posts posted by Mark Aceto

  1. 1 hour ago, Jim Wilson said:


    Edit: The closest modern Mac I've seen that did not suffer BADLY (but still suffered) from thermal throttle, was the iMac Pro I have here with the 8 core 3.2GHz Xeon W. It is advertised as having a turbo boost of 4.2, but it is only able to maintain 3.8 for a load under about 2 minutes before it drops to 3.6, this being with a manually overridden fan control that I have set to maximum for best possible performance. This is much less of a throttle than the other Macs in  the current range, especially the mobile options.


    Apple downlocked that chipset to avoid thermal throttling. My 10-core 3.0GHz is 3.3 on a PC.

    • Sad 1

  2. In @Kevin McAllister's examples, the root of this issue seemed to be:

    • POI errors
    • Symbol erros
    • Modeling error (software not user)

    Therefore, I would love to see those errors get fixed, so users don't have to spend more time editing in edit mode to patch the underlying problems. To me, and how I value my time, this is just one more example of how parametric POI's vs modeling is slowing me down with workarounds. That's the 2020 killer feature: clean up POI's (and their UI/UX).


  3. 16 minutes ago, Jim Wilson said:


    My experiences have also led me to agree with this entirely, the last Macs that I did not notice throttling on were the older, beloved "cheesegrater" Mac Pros from 2012 and prior. 


    My 2012 5,1 cheesegrater felt just as fast as my 2017 iMac Pro when using VW 2017 and 2018 SP2. Same amount of spinning beach ball of death too. Sounds like that's about to change for the better though very soon. Maybe even tomorrow, right?

  4. 10 minutes ago, Kevin McAllister said:

    ^ likely six cores..... since the iMac Pro starts at eight and and the new MacBook Pros have six.



    Also hoping they solve the thermal issue and improve the GPU. Then again, I also believe Jackelopes are real and hope volumetric lighting is coming back to VW 2019.

  5. 11 hours ago, Jim Wilson said:

    So i've learned something I wanted to share about the On Demand Tessellation feature I demoed: When I shot that video, ODT was using only 3 additional cores to the main core, so it was topping out at using 4 CPU cores total, even though that machine had 8. So the speed improvements going forward will be even more significant than seen in the demo. I will check with engineering and ask about the current limitation and see when it is planned to increase. This will directly affect current hardware recommendations so it interests me personally, greatly.


    This is exactly my point when comparing a 2017 iMac with a 2017 iMac Pro.


    Would also like to understand the performance usage/difference between an 8GB and 16GB GPU (not sure how to measure that).


    As of August 2018, it seems like spending over 5k on any Mac won't yield much return, so September will be very interesting... 

  6. On 8/29/2018 at 4:22 PM, Matt Overton said:

    Why should design layers always be 1:1?


    The model is the true size, the visualisation is purely for discussion with the driver.

    To me, eye on the prize work at what scale is going to get the job done and always think about what is needed to get the job done.


    Exactly. Drawing at 1/8" scale with a 0:0 at DC, positioned where I want the model on an Arch D/E page size, with fonts for dims/notes/callouts at 10/12pt... saves a ton of time annotating SLVP's. The less I have to enter an edit mode in this app, the faster I finish.

  7. This is absolutely massive, and really appreciate the interest in adding Sleep back into the Eat + Design equation. Can't wait till the triumphant return of volumetric lighting next Tuesday! 😉


    Would love to see some of the other key features found in Lightroom like:

    • Tone curve
    • Vignette (a slider not a multi-step workaround)
    • Noise (actually adding noise instead of reducing it... to help with the uncanny valley)

    Also, as @zoomer suggested: numerical controls in addition to the slider.

  8. 1 hour ago, Jim Wilson said:

    We will do both, we did it last year a bit as well, where we listed the minimum requirements and then what wed recommend from experience. So in the 2018 article the Minimum Hardware Profile is the system requirements, and then the High End Profile is what wed suggest for heavy duty work.

    If that isnt what you meant, or it wasnt clear enough, please let me know, I can directly affect how we share that info and I'm open to suggestions on how to make it as clear as possible. I know its a lot of tech jargon.


    Thanks, Jim. Looking forward to it... 

  9. First of all, thank you. Very excited to try this out on in real world tests to see if VW is significantly less CPU-constrained for those tasks.


    The name of the game has been to find the fastest single-core clock speed available, so could you elaborate on multi-core improvements in 2019? For example, what tasks will take advantage of multiple cores that didn't before? And in what views that we couldn't before: DL, SL, 2D, 3D, DLVP, SLVP...


    Would be really helpful to see a table that shows how different processes use/require CPU, GPU, RAM (particularly from year to year).

    • Like 2

  10. Using the default settings to export a DWG from either a plan or 3D view, then importing that export into a new file, lots of 3D geometry is missing from symbols and PIO's. The drawing is a fresh file with only objects that I have drawn. Exporting to 3DM has no issues whatsoever.


    Has anyone else experienced this, and found a solution?

  11. Oh, wow, looks like the WX 9100 is already compatible:




    AMD Radeon RX Vega 64, Vega Frontier Edition Air, and Radeon Pro WX 9100

    These graphics cards are based on the AMD Vega 64 architecture. Recommended graphics cards include the Sapphire Vega 64, XFX Vega 64, AMD Frontier Edition air-cooled, and AMD Radeon Pro WX 9100.


    Recommended Thunderbolt 3 chassis for these graphics cards:

     Sonnet eGFX Breakaway Box 650W3



    So that's probably as close to the 1080 ti as I could get!

  12. Thanks, @zoomer. What are the 2 GPU's? I'm only aware of the 580.


    Considering that the WX9100 costs $1600 before an enclosure, and VW can't take full advantage of GPU acceleration yet, the 580 might actually be a great solution for the next yearly cycle of Vectorworks/Apple hardware.


    BTW the baseline for me is the 1080 Ti... so whatever AMD chip will get me as close to that performance on a Mac.

  13. Assuming OpenCL and OpenGL are comparable metrics for VW use, the 580 is a budget card at best:




    And a $600 solution to a $5,000 problem computer doesn't sound like great budgeting.


    Hoping for a 16GB AMD eGPU solution (like the AMD Radeon Pro WX 9100). Does anyone know if I can make that work with a 2018 MacBook Pro or a 2017 iMac?


    As it stands, the 2017 iMac is the still the fastest Mac for VW:




    Waiting to see spec's for the 2018 iMac (hopefully no overheating/downclocking) before upgrading 2014 MacBook Pro. Assuming the 2019 Mac Pro will have a base cost of $10k, and all manner of disappointing compromises chosen by "experts"...

  14. On 2/12/2018 at 11:47 AM, JimW said:

    I had thought so initially as well until I saw how many possible problems can (and did) arise just from switching it over even when not adding new functionality. Modernizing such a deep system sometimes going back into decades-old code with huge numbers of ties to more recent systems. 

    Combined with how much slower things would have been in the meantime if we hadn't done OpenGL, then Plan editing etc in phases, it made sense to roll it out in waves. If we hadn't, we would be WAY worse off than we are now with even more major slowness across the board. Changes have happened/are happening to the Beta program so that major features like this will get way more of a shakedown than in previous releases before they go public so that in the future bigger changes could be done in bigger chunks and there wouldn't be any Day 0 nasty surprises, but the Beta program isn't done being updated yet so some features are being handled differently than others.

    Apologies if I have misled anyone here in this way. A lot of my work involves going back and forth between Engineers and Users and sometimes terminology used by both can have different definitions in different contexts.

    For Engineers, "Top/Plan" is the geometry drawn on the design layer in Top/Plan view. For a user, "Top/Plan" would also functionally include DLVPs, highlighting, control handles, but for an engineer those are different systems entirely and are handled in very different ways. The mistranslation and lack of clarification however would still rest on my shoulders, I'll try to be more clear in the future when I discuss this topic in particular. As complex as Vectorworks can be on the surface, I assure you the internal workings are an order of magnitude more so. A lot of development work like the porting of plan graphics to the VGM is part of a larger attempt to simplify and streamline it's underlying components.


    This is the only feature that matters in VW 2019. I'm sick of seeing my 10-core workstation with 16GB of VRAM maxed out at 120% CPU on the only core that VW is capable of using, so that I have to force quit the application, and lose my work. This is unacceptable. No more new features. The maintenance release is long overdue.

    • Like 2
    • Love 1

  15. Reporting back here with some findings...


    Been using an iMac Pro 3.0Ghz 10-core CPU, Vega 64 16GB GPU, 64MB RAM machine for a few weeks now. Haven't tried rendering yet but I frequently get the spinning beach ball of death "Application Not Responding" message a lot (Activity Monitor reports the good old "using 125% 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. VW is absolutely CPU-constrained on a single-core before you ever get to  rendering on multiple cores. That said, if you're on a Mac, you have to choose between clock speed (iMac) and GPU (iMac Pro) for now.

  16. @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.


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...