Jump to content

Mark Aceto

Member
  • Content Count

    539
  • Joined

  • Last visited

Posts posted by Mark Aceto


  1. https://www.apple.com/newsroom/2018/10/all-new-macbook-air-takes-flight/

     

    Quote

     

    Radeon Pro Vega Graphics Coming to MacBook Pro Next Month

    Apple also today announced new MacBook Pro graphics options that will bring powerful Radeon Pro Vega graphics to MacBook Pro for the first time. These new graphics options deliver up to 60 percent faster graphics performance for the most demanding video editing, 3D design and rendering workloads.

     

    Notwithstanding thermal throttling, faulty keyboard that you can't take onsite, lightbar that nobody asked for and drives the price up, a removed Escape key that has to be remapped to the Caps Lock key, reflective screen and #thatdonglelife, this is encouraging news and good reason not to buy a MBP until next month.

    • Like 1

  2. As much as I'd love to ditch Apple's tiny mirror of a display on an iMac/Pro, spending $3,000 on a 6-core (toaster) 3.2 Mac Mini + an eGPU is not something I'm interested in as a person who earns a living using VW. And the 4-core is an i3 !!!

     

    Every year, we wait and we hope, and every year we're disappointed and price gauged. The hacintosh is looking better and better all the time.

    • Like 1

  3. 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

  4. 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).

     


  5. 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?


  6. 10 minutes ago, Kevin McAllister said:

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

     KM

     

    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.


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


  8. 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.


  9. 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.


  10. 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... 


  11. 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


  12. 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?

 

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