Jump to content

Kizza

Member
  • Posts

    993
  • Joined

  • Last visited

Reputation

8 Neutral

Personal Information

  • Location
    Sydney Australia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Pat, that is so true! 😎
  2. I'm leaning towards the intel, because I need the additional ports. By the time you add a TB dock, cost would be comparable. Besides, it's an interim machine, may upgrade to M2 or M3 later... Any info on whether Intel UHD 630 integrated graphics would run VW2020 for light residential with very light modelling would be appreciated.
  3. @Zoomer, how do you know a space grey version is coming?
  4. Hello, wondering if anyone is running VW2020 on a Macbook Air M1? It's time to retire my 2012 mini (which currently runs VW2016 with Mavericks). I have a VW2020 licence which I use on Windows, but I want to transition it back to Mac. FWIW, I find I mainly use the 2012 Mini with VW2016 as I prefer the mac OS–but I can't upgrade it to a Mojave or Catalina because VW2016/Mavericks is as far as I dare to go with it for compatibility reasons. I'm also considering an Intel Mini (current) vs the M1 Mini because it has a few more ports - is that such a big deal? It seems though, that the M1 machines are very capable. I currently run 2 x Dell 24" monitors (although I plan to get two 4K monitors in the not-to-distant future). Thanks
  5. Im looking for a suitable half length graphics card for an external GPU for running Vectorworks (currently VW2017) I want to upgrade my mac mini to the 2018 version. Anyone using one presently? Im looking at this case https://www.akitio.com/expansion/node-lite
  6. And here it is in 2012.. I use scroll wheel all the time. I mainly use the zoom percentage when navigating between the sheet layers and design layers - sometimes returning to the sheet layer requires a zoom reset.
  7. Please see image, the dropdown list should be in front of the Resource Browser tab. 75% is hidden. I think this is a bug.
  8. I've been away from VW for a while due to undertaking a project based assignment outside of the industry. I took advantage of an offer to upgrade from 2012 to 2017. I must say that I am very impressed with the mac version of VW2017. The UI seems better implemented than the 2012 version. It has been stable and fast. It seems like a new program, so much to learn....might have to get some training. Looks like VW2018 was a big release as well.
  9. we're seriously considering moving to Windows. Mainly because of limited hardware options on the mac side. Other reason is that Microsoft Office is just better on Windows. Plus Outlook has features we want to use that Apple Mail doesn't (or Outlook for Mac)
  10. Depends on how Nemetschek plans to implement materials. Will VW have the inbuilt intelligence to determine if an object is cut or is in section? If so, then all of the graphical attributes of an object (2D plan, 3D, section attributes, fills, textures and hatches) could all be incuded in the class - VW then intelligently determines how to display the object depending on the view. This approach could support how users currently use classes. So essentially, "materials" is an additional feature/function of a class, which a user initiates depending on the need. But in developing materials, you also need to think about how it will work with live sections, as these two features are twins IMO.
  11. The "Convert Copy to Lines" keeps the original objects intact.
  12. Slapping on an option button doesn't really address the underlying issue does it? Apparently the reason why auto updating is presently not implemented is because VW is still single threaded... So looks like the status quo remains..
  13. When right clicking on an object and selecting "Locate Hatch in Resource Browser", I would like the selected hatch to be automatically brought to the top of the hatch list.
×
×
  • Create New...