Jump to content

Mark Aceto

Member
  • Content Count

    248
  • Joined

  • Last visited

Everything posted by Mark Aceto

  1. 2nd the BenQ 32" antiglare monitors. Been using them for years, and turned many people onto them. That said, my dream monitor would be a 40" curved display because: 32" is not large enough to view at full 4k (see attached screenshot) > 32" you have to physically roll your chair from side to side, so curved is nice (the trick is tilting it exactly 90º to your eyeballs) > 40" starts to pixelate 4k
  2. While that is true, none of the previous Mac Pro's were priced so out of reach for professionals. Rationalizing that this version "isn't for us" is to forget that every prior version was. As someone who's getting ridding of my iMac Pro (all in one is not for me), my options are Mac Pro, Mac Mini, and MistakeBook Pro. So, unless they're about to surprise us with a new modular desktop, they just hosed most of their pro users.
  3. Unless you want an all-in-one, there's a huge gap between the Mac Pro and the Mac Mini. All we wanted was a user serviceable machine that we can upgrade with our own components, including NVIDA GPU's and AMD CPU's. Instead we got a FU on wheels. Clearly, their POV is "if you want to put your own guts in it, we're gonna charge you more for the base. How do you like them Apples?" And the monitor is a joke. So many better options for CAD pro's... Would be nice if they brought back an antiglare screen to the Mac lineup though.
  4. Exactly. The CPU is socketed, so I wish they had a placeholder throwaway option. It's absolutely beyond me--yet so completely inline with Apple nonsense--that they refuse to work with NVIDIA and also insist on using Intel CPU's. Why not just go all-in on AMD? Probably because of some 10-year deal Tim Apple made with Intel 7 years ago... The storage is modular, so we could bring our own... on top of the 6k base price. @JuanP it's probably too soon to tease VW 2020 but: What's the current multi-core limit? Is it still 4 cores? Is there a plan to use Metal? Netmetshek-owned Maxxon/Cinema, Redshift, Epic/Unreal/TwinMotion, and VW competitors like AutoDesk are onboard... I've never pushed VW beyond 12GB of VRAM--any updates to the VGM that will make use of 32GB or more? How's the project of revising legacy code coming along? Is there a target completion date? After dropping $9k on an iMac Pro, and watching the spinning beach ball of death (VW 2018), I'm not eager to drop $10k on a Mac Pro, and get that same sinking feeling of buyer's remorse in the pit of my stomach. That said, VW 2019 made huge strides to improve that, so fingers crossed for VW 2020...
  5. So... I'll be the first to ask for a status update on VW and Metal. On that note, when will VW's 4-core limit will be increased, and to how many cores? 8? 12? 16? 24? 28? Convection has been around since Newtown but at least we didn't have to sit through Sir Jony Ive mansplaining it to us. Or Phil gaslighting us about how leaving 1micron of space between modules is "courageous" (and won't box them/us in 5 years from now). Except that they pulled their favorite dirty trick of using 256GB storage--same as an iPhone--and a 2-year old budget-GPU in the baseline model, so guess how much those upgrades will be? Based on current pricing models, and a $1k monitor *****ing stand, I'm guessing in the magnitude of thousands, quickly turning the step-up config into a $10k build that turbos at a theoretical 4.4Ghz. Isn't the point of that whole proprietary graphics contraption Apple's version of SLI, enabling 2 cards to be used as 1? Even so, I would be shocked if VW could max out even one of those 32GB cards anytime in the next 5 years (would be an excellent problem to have though). Honestly, what I really want right now is a 2019 iMac without a screen. That would be solid for VW for the next 2 years. The Mac Pro is future-proof in it's modularity but totally over-engineered in ways that won't help us VW users. Plus, who wants to drop $10k on a machine that's still gonna get a spinning beachball of death because of all the legacy code in VW? Now that the cat's out of the bag, and Apple increased the width of something--that overpriced monitor--for the first time in their history, this gives hope for the mythical 16" MacBook Pro in 2020...
  6. A machine with a dedicated Vega 20 would feel twice as fast as the same machine with an integrated GPU for everything except rendering (which is mostly CPU intensive; particularly the number cores). That will only continue to be the case. However, you might get more bang for your buck by using an eGPU with your current machine. You could even use a Vega 64 with 16GB VRAM, and ride out this generation of MBP until the mythical 16" MacBook Escape with scissor keys appears in the next year or so. Considering, Windows laptops are now available with 16GB NVIDIA GPU's, hopefully Apple will offer at least an 8GB GPU by then (instead of a paltry 4GB).
  7. With all due respect to VW, you might wanna check out Rhino for this type modeling
  8. I think it's still sinking in for a lot of users that buying the base GPU, and then adding an eGPU is the 2019 version of modular upgradability. They've just moved the guts to the exterior (like it's on life support because it basically is at this point). It feels wrong to buy the cheapest (discreet) GPU in a disposable machine but... That was also the promise of TB3. Cloud storage is another workaround to overpriced SSD upgrades that aren't modular / can't be upgraded.
  9. Mojave is trash (in general not just VW). You can add an eGPU to the 13" for the best of both worlds (and have modular upgradability in the future). Plus, if you're running HS, you can use a NVIDIA GPU if you prefer.
  10. @Jim W , sad to see you leave but massively appreciative of everything you've accomplished. Tons of respect for choosing to spend more time with family - perhaps the most important tech support lesson for so many of us here. Break a leg in your next endeavor! @JuanP , in the search for the new voice of videos and tutorials, I propose H. Jon Benjamin (reading a script prepared by someone as knowledgable as Jim). Because he's the hero Forum deserves but not the one it needs right now.
  11. What a pleasant surprise to come home from a gig and find 3.1 waiting for me! @PVA - Jim Really really really happy with this new incremental "point" upgrade path!
  12. Upgraded to Mojave yesterday. Downgrading to High Sierra today. Not worth the overall bugginess (in general) for a half-baked dark mode UI and a few bells and whistles. High Sierra runs smoother, is compatible with NVIDIA drivers, and is less locked down. As with all things Apple lately, it seems like 10.13 is the "last good version" before Apple replace features with gimmicks. And my "legacy" software (Office 2011, Things 2, Wunderlist, Yojimbo, Bento, Neat) all run on it just fine. Also, it's nice to stay logged into all of my work Gmail accounts in Mail and Calendar...
  13. Apple Releases Macbook Pro 8-Core, "Fixes" Keyboard: http://www.loopinsight.com/2019/05/21/apple-releases-macbook-pro-8-core-fixes-keyboard/ Year old pricing on year old GPU/RAM/storage components/upgrades in spite of the cost lowering year over year Single core base clock speed is down from 3.5ghz (2017 13") to 2.4ghz not good for modeling in Vectorworks “Up to 5.0GHz Turbo Boost” lies “Experience smooth real-time performance when rendering 3D models in Cinema 4D” more lies Other than reducing the base clock speed, not sure what Apple or Intel have done to improve thermal throttling Possibility of a GPU bump to 6gb in the fall (similar to last year). Otherwise, this is probably as good as it's gonna get for this generation (before they screw up the next generation). @JuanP , do we have any updates on the reality of using an eGPU with a MBP? I'm still on High Sierra since Mojave is still a half-baked buggy mess (in general) so they can push subscriptions "services", which means I also have the option to go with NVIDIA.
  14. Really frustrated with SP3 performance. Super slow, lots of spinning beachball of death, seems to be graphics related, switching modes doesn't solve it. From the outside looking in, it sure seems like the new features created new bugs. 2.1 was solid, and I'd roll back if I wasn't going to be onsite building this project for the next two weeks (past the point of no return to pivot mid-project).  Going forward, guess I'll wait for .1 updates... I would also request that we have more of those minor stability updates in between the big features updates. I'm sure hundreds of bugs were fixed in SP3 but there was a huge gap in between 2.1 and 3.0, and I wish I was using a super stable 2.2 or 2.3 right now, and skipping the big Lumion update until 3.1 or so. Even Mac OS 10.14.4 is having graphics issues because that was mostly a big push for their new services features subscriptions, so I'm staying on 10.13.6 for now.
  15. Maxon Acquires Redshift Rendering Technologies Well that's an interesting development in the Nemetschek universe.
  16. Specifically, when Vectorworks is running. The solution is to have more of a heads up arrangement of palettes like Cinema or Unreal vs going down a rabbit hole of buried palette tabs, dialogs, windows, preferences and advanced settings just to do something simple like setting attributes and textures. It's like every time I use a worksheet, I'm harnessing the incredible power of a relational database... that was designed by someone in the 90's and hasn't been updated since.
  17. Definitely experiencing file size bloat again which is pretty typical this time of year. After this project, it's time for a clean install of SP3.1 Same. Also, the Screen Plane keeps activating and abducting objects that belong on the Layer Plane, which I've never experienced before. Frankly, I wish I could disable Screen Plane altogether. This isn't MiniCAD. I think maybe the key learning with 2019 is to wait for the .1 incremental updates (praying for 3.1).
  18. On the topic of streamlining continuity, it's one thing to have the option to enter class/viewport/drawing info in multiple places: OIP top OIP bottom OIP render tab Resource library symbol Symbol within a symbol Navigation pallette Tool/organization/class settings Attributes palette class settings and on and on... ...but to have to enter that info consistently in all places is insane. It would be nice if checking the "Use at creation" box actually worked but it doesn't, so I have to keep a mental checklist of all the places I need to hunt down to get a stick of truss to display the texture I set for that class. And VW2019 just added more options (many of which were not announced or documented, so they're just easter eggs of counter productivity). I spend so much time: Hunting for where an object class hasn't been updated Naming viewports Renaming viewports Manually reentering title block revision data over and over again on multiple plates And why is the title block dialog forked into 2 options (screenshot attached)??? ...that I'm not actually working; just playing a game of Whac-A-Mole. I don't want disappearing AI context menu options. I want fewer options, and consistent choices that simply work. We don't need 3 different tree tools. We need 1 that does the job of all 3. If I update the class somewhere, I expect it to update everywhere. Dr. Frankenstein is turning this into bloatware, and I honestly just want the interface to get out of my way. Solution: Less Friction, More Productivity While we're at it, can we please make Service Select a monthly bill like every other service subscription?
  19. "This is hi-fi. High fidelity. Know what that means? That means this is the highest quality fidelity."
  20. OK, so what's the recommendation here? Is the high setting a decoy? All things considered, should we all just use the middle setting? Would we really notice a hit to graphics performance if the tradeoff is improved stability? How much of my time drawing is really taking advantage of that high setting? 20%? I dream of a VW with a single unified workspace for all disciplines (with Menus for each modality) and no GPU settings to fiddle with (just minimum/recommended GPU requirements), and it all just works.
  21. For clarification, Tech Support asking me to set Navigation Graphics to Best Compatibility was not a troubleshooting step related to section viewports. Rather, it was myriad other issues.
  22. Lumion narrator: "It's hard to explain, but if you get there, come find me. Nothing will be able to tear us apart then."

 

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