Jump to content

Diamond

Member
  • Content Count

    703
  • Joined

  • Last visited

Posts posted by Diamond


  1. Hello @jmanganelli,

     

    Thanks for the heads-up regarding workflows for large projects on other platforms. What you are saying had definitely been my experience when working with complex Revit models.

     

    On 6/25/2020 at 11:57 AM, jmanganelli said:

    how Bentley in particular organizes models

    The Bentley video example showing the referencing of storeys for different residential layouts makes sense (even though I would typically split this into interiors vs architectural).

     

    The one main amendment I would make for a Vectorworks workflow is to prevent references within references for IFC export. Other than that (and other typical Vectorworks best practice workflows), file structure comes down the project requirements.

     

    Cheers.

    • Like 1

  2. 1 hour ago, Markus Barrera-Kolb said:

    Makes sense that you model each building in its own file; do you then create the corresponding drawing sheets in those respective files as well?

    Yes.

     

    1 hour ago, Markus Barrera-Kolb said:

    If you do generate sheets within multiple files, do you create your drawing index manually, or is there a way to pull information for sheet layers from multiple files into one index?

    I had thought the title block object could help you with this. I have never used it as we have used a different system at the day job.

     

    1 hour ago, Markus Barrera-Kolb said:

    Do you repeat identical interior layouts for dwelling units as multiple copies of design-layer viewports or do you create a symbol for each of these? It makes sense that these would only comprise the interior walls and that the shell would be modeled separately.

    You would need to reverse engineer this for what schedules you need to produce on the other end. But once again, use layer viewports inserted of symbols. Or if the levels are the same, why do you need to show anything but the exterior facade? (One plan for multiple levels?).

    Okay, for sections I can see why – but create your information once and reuse as much as possible.

    Create a typical level design layer that contains a floor layout sans exteriors. Keep each referenced layout (either unit or level made up of units) on their own layer (Vectorworks doesn't like cropping viewports in 3D).

     

    Each project requires a custom solution for your requirements. Test as you go.

     

    Cheers


  3. Hello @Markus Barrera-Kolb

     

    I have plenty of experience on these size projects (and bigger – mostly on established education sites, but I started in residential and multi-res). This workflow depends on the experience of the team. I am presuming you are the lead documenter?

     

    The size of projects I deal with normally means I am in charge of base build (that is, structure, external fabric, facade, elevations and sections, landscape, and so on). With my base build team (normally one or two others) we divide the tasks up with each responsible for their set of drawings (if you don't make people responsible for their tasks that relate to deliverables, things get missed). Deliverable packages might include –

    • General arrangement plans.
    • Elevations and sections.
    • Detailing, especially facade.
    • Integrating, interrogating and modelling the structure and mechanical services, and the integrity of the model.

    While this is happening we are collaborating with and having input into interiors.

     

    Regarding the setup of the Vectorworks model/drawing set – :

    1. Regarding referencing, I find layer referencing more stable and reliable, but unless the origins and orientations are set correctly in the building model files, it won't work in your site file (see below).
    2. Local Origin points need to be rigorously maintained. Often team members can move them without knowing. Also you need to make sure there are no odd objects way off in space (more than about 5kms away). This breaks Vw' (or any other BIM software's) mathematical engine.
    3. I normally treat each building as a separate entity (as the projects I work with are normally staged), with it's own plan/model file with it's own sheet layers (make sure your drawing numbers and deliverables are sorted out first).
    4. Each building file uses storeys, and set to correct elevation heights (this keeps the size of each building file down, and only need to change orientation in site model file).
    5. If your interiors team is separate, for the sake of ownership and to prevent project sharing clashes, add extra layers per storey for interiors (floor finishes, interiors, ceiling, and so on).
    6. Create a separate site/terrain model file.
    7. I (design layer viewport) reference the building models into the site terrain model, and rotate to the correct orientation (this can then be used for sun studies, street elevations, and so on).
    8. I find hybrid objects such as walls often don't play nice in symbols. Test design layer viewports first.
    9. For unit layouts (unless there is a very specific reason) I would keep the exterior walls and base build separate to the interior for each unit. Perhaps you could place where the windows are meant to go on a Guides class, and whoever is doing the facade can place them in the exterior walls?
    10. For large projects, I will often use a separate library file that contains all of the latest resources for the project, and reference these into each file. Each project is a bit different, so you need to test as you go.

    Hope that helps.

    • Like 3

  4. Redshift AMD support arrives as soon as the new Metal based version arrives, which should be in the next couple of months. Macs have been all AMD for years.

     

    It sounds as if they are looking to support as widely as possible, but Vega minimum was mentioned as a possibility on the Redshift forums. 

     

    PS Apple still has bad blood towards Nvidia over a bad batch of GPUs they supplied years ago. Additionally Apple has a similar approach to GPUs as Nvidia does - they both want to add value by getting down to the ‘metal’ – hence CUDA and Apple’s Metal APIs. And that is why Maxon is so excited about the new Mac Pros that link up to 4 GPUs with 128GB of VRAM. 

     

    PPS If you want to run Nvidia you need to use older OS versions. 

    • Like 1

  5. 23 hours ago, Zeno said:


    so the demo version for mac on redshift site could be allow us to test redshift on mac? If you read requests there are no mention about metal, but request 10.14 or older macOs with CUDA driver 🤷🏻‍♂️


    I don’t believe MacOS Catalina supports Nvidia GPUs, so until the new Metal compatible version arrives Radeon cards and Metal is off limits.

     

    The think current Mac Redshift version only supports older machines and/or eGPUs with Nvidia cards to get CUDA. 

    • Like 1

  6. 11 minutes ago, Amorphous - Julian said:

    I’m honestly my current wish to get GPU renderers for Mac Users will not also take 11 years.

    If you look over on the Redshift Forums (sign-up required) there, an employee making it known there is keen back and forth between Apple and Maxon in getting C4D optimised for Metal 2. Maxon typically loves the MacOS platform, and it think it will be a point of pride for them to have one of, if not the fastest rendering workstation solutions available.

    The Mac rendering scene has been lean on options for years, and thankfully with the release of the Mac Pro, that is changing.

    • Like 2

  7. Regarding today's blog post…

     

    http://blog.vectorworks.net/020620archpreferences?

    "Session > Maximum number of Undos > 42

    Vectorworks tech support recommends a maximum of 25 undos, but I like to live on the edge, so I have mine set to 42 (fellow Douglas Adams fans might appreciate this). For my needs, I also have “Undo View Changes” set to “Grouping Similar View Changes.”"

     

    I was not aware of this recommendation. Why is this? Beyond memory usage, is there another reason such as stability?

     


  8. 11 hours ago, Amorphous - Julian said:

    Now, as far as I'm concerned, BIM means BIM. There is no half-way point.


    This is where I am going to have to disagree. What you are producing needs to be fit-for-purpose, not BIM for the sake of BIM.
     

    And what part of BIM, are you referring to? Information, or the model? After all, the model is just another form of data. That is why there are LOD definitions for modelling, because modelling every extruded profile, screw and rivet brings most BIM packages to their knees (although maybe not ArchiCAD, and Vw 2020 is much better with large models). Why explain with extensive modelling what a spreadsheet can do more simply?

     

    And regarding detailing, how do you convey flashings and elements that are so thin that they are lost in a model? (Maybe there might be UI improvements to be able to display this within an exploded model view - but once again, why model the whole building when one detail would do) You need to understand each data medium (model, 2D drawing, schedule, spreadsheet, and so on) and what each does well to suit each purpose.

     

    Architecture is hard. There is rarely one size fits all (unless your work is extremely repetitive - and then maybe Revit would be more appropriate.) Vectorworks is mostly a design-BIM tool, that can also document. Revit’s strength is as a documentation tool. Hope that wasn’t too rambling.

    • Like 3

  9. Over the timeline of any project, 2D and 3D will each be given more attention. For our workflows and any hybrid 2D/3D workflow (which Vectorworks is), live updating can be both a blessing and a curse. 

    • When focusing on 3D it is a blessing, because the elevations and sections reflect the direct inputs of the model.
    • When focusing mostly on 2D it can be a curse, because 2D work often breaks model integrity.

    I have seen this recently on a large Revit based project where the (AutoCAD based) 2D plans, sections and elevations are a month behind the model. Working on the model meant that the plans, elevations and sections would be broken. I realise there may be a world where we transition to 3D documentation, but until that day arrives, we still need to produce 2D drawings.

     

    For this reason I would want viewports to have the option to be either live or static.


  10. Hello,

     

    In our (North) Sydney studio we are currently looking for architectural documenters / technicians / draftspersons, or experienced architects with sound construction and documentation knowledge. High Vectorworks proficiency is preferred, but exceptions might be made depending on fit. Candidates must be willing to learn Vectorworks to a high degree of proficiency. 

     

    Some information about us…
    We are a medium sized design firm (~ 60 team members across 3 studios).
    We work across three key disciplines: Architecture. Interior Design. Masterplanning.
    We focus on the following market sectors, bringing diverse expertise and experience:
      • Consumer: retail, leisure, hospitality, entertainment.
      • Community: education, residential, community, leisure, retirement.
      • Commercial: workplace, commercial.
     
    If you are interested, please contact me via private message (hover over my user name and select message).
     
    Warm regards,
    Troy

 

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