Jump to content

Kizza

Member
  • Posts

    994
  • Joined

  • Last visited

Posts posted by Kizza

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

     

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

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

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

  5. If auto-updating is added as a feature, it should be optional, as there are plenty of cases where you would not want the contents of a worksheet dynamically changing every time you added/edited/changed objects.

    I can't think of any reason why I wouldn't want my worksheet to be updated at all times.

    Worksheets after all, are simple spreadsheets, with data links to plug-in-objects and records. Yes you may have thumbnails of windows, doors, plants etc also, but I fail to see how including these images will affect processing power to a great degree - unless you have many, many images perhaps.

    Microsoft Excel users do not have to manually update their worksheets - they are dynamic, make a change to one worksheet and it'll update in another. I'd say Excel worksheets can be far, far more resource intensive than Vectorwork's worksheets.

    What you describe is possibly a VW performance issue. And, if there is a reluctance to implement auto updating of worksheets because of CPU performance, where does that leave other performance related enhancements, such as auto updating hidden line viewports (which I think is coming in 2017 ;) ), live updating section viewports, live updating site model sections?

    And, even if there is a performance related software issue to generating worksheets with thumbnails, these can be dealt with by background processing techniques, which have recently been introduced into VW big brother, Archicad.

  6. That is an interesting idea. The only problem would then be that you would then have to make a viewport of the viewport. But it is something to test.

    Sorry Tom, what I meant is do Detail Viewports only live on a sheet layer? Or can you create a detail viewport like a section viewport - both on a design layer and a sheet layer?

  7. JimW, are we still manually updating hidden line viewports in 2017?

    I agree with many of Altivec's observations, except that I accept that higher end rendering should be passed onto another package, but I would insist that the C4D-VW pipeline be rock solid. We as a micro studio are expected now to provide more renderings of our drawings so this becomes ever more important to us moving forward.

    I think that when you become aware of the competition and what they offer, you see more clearly where VW needs to spend their development resources. Some users here (eg Kevin McAllister) are very proficient at using VW and other packages - the shortcomings become glaringly apparent and frustration grows.

    I've played with a demo version of Archicad 20 over the last two days. VW on steroids!

×
×
  • Create New...