Jump to content

Diamond

Member
  • Content Count

    723
  • Joined

  • Last visited

Community Reputation

137 Spectacular

1 Follower

About Diamond

  • Rank
    500 Club

Personal Information

  • Occupation
    Architecture + Design
  • Location
    Australia

Recent Profile Visitors

2,183 profile views
  1. Related to the philosophical side of architecture, on the trxl podcast this week… Special guest Reg Prentice joins the podcast to talk about the value of an architect, how and why we document decisions, the network effect, how designers are decision factories, and much more. https://podcasts.apple.com/au/podcast/trxl/id1519377425?i=1000492068230 What caught my attention was Reg's description of an architect's role – that is, designers are decision makers that create certainty from uncertainty (and needing to be comfortable with uncertainty, which software / tools is a part of). And then he speaks of wicked vs tamed problems. Good stuff to help us understand the real issues of the architectural profession. Yes, I feel this as, after many years, I have recently changed architectural firms, and nearly ended up using ArchiCAD. It is very hard for me to grow as an architect remaining on the Vectorworks Architect platform. Knowing there are parts of Vectorworks that are taking such great leaps forward and are much beloved makes the Vw Architect product stagnation all the more challenging / frustrating. I suspect this reflects the general stagnation of the architectural software space. If architects had clients / customers / suppliers / technologies forcing complex standards upon them (as lighting designers do), I think AEC software would be far more leading edge. Ironically much of the push to better solutions is coming from clients and developers requiring better project outcomes at the big end of town. But Vectorworks doesn't generally play in that space in Australia. I am thankful for the increased stability of the last couple of releases. I hope now that those holes are plugged, Vectorworks Inc. can also plug the holes in tools that have been around for many years but have gone unloved. I would love see Vectorworks Inc. to take advantage of the industry discontent that Autodesk / Revit has created, and not to be lumped in with them as part of the problem.
  2. 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. 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.
  3. +1 I would also love to know this.
  4. Yes. 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. 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
  5. 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 – : 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). 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. 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). 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). 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). Create a separate site/terrain model file. 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). I find hybrid objects such as walls often don't play nice in symbols. Test design layer viewports first. 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? 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.
  6. 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.
  7. Hi Dom, Amazing work. Any chance of English versions? My Deutsch is not that good. 😃
  8. 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.
  9. 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.
  10. The other rendering engine that makes complete sense for Mac is AMD Radeon ProRender. It is a CPU and GPU rendering solution, and would be both Mac and PC compatible. It is also already in C4D so should be readily compatible with Vectorworks. https://www.amd.com/en/technologies/radeon-prorender
  11. Redshift are about to release a Mac version that is Metal 2 based. That is, Radeon graphics compatible. They have been showing demos of this at recent Mac events running beta versions on the new Mac Pro. Apparently it is screaming (faster than CUDA) fast.
  12. Another PC only rendering option. Why was not a Mac version given higher priority, when Lumion already existed?
  13. Thanks for the comments At least the new solids modelling history negate the need for such long Undo history.
  14. Before reading this article it never occurred to me that Undo history could be causing (m)any of my issues. Cheers.
  15. 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?

 

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