Jump to content

Ben Beaumont

Vectorworks, Inc Employee
  • Posts

    52
  • Joined

  • Last visited

Everything posted by Ben Beaumont

  1. I do wonder why we need Level Types at all. To me it seems overly complicated to have Level Types and then Default Storey Levels and then to finally have to apply these to the actual Storey. Let's drop Level Types entirely.
  2. It seems a Material carries all the metadata that otherwise might not have a home. So it sets a project up to be measured. The fact it can also have a Texture (and by proxy a Surface Hatch) is a nice to have and - it seems - a convenient way to help visualise a project.
  3. It seems a Material carries all the metadata that otherwise might not have a home. So it sets a project up to be measured. The fact it can also have a Texture (and by proxy a Surface Hatch) is a nice to have and - it seems - a convenient way to help visualise a project.
  4. Boh, Yes, I would imagine we would be looking to use data tags and worksheets...this is - as yet - untested. It's business as usual for all other objects that don't yet use materials.
  5. We have constructed localised libraries of 100's, (pushing 1000's) of Materials. @Julian Carr has written a script to create Materials from Textures which helped enormously. There is also a Worksheet that can push other material values into Material Styles. This is a boon for building libraries with repetitive information. We have updated our Wall and Slab styles such that the external and internal components (only) use Materials. Typically the external face is textured with an associated surface hatch (eg; painted weatherboard) so the component has a discernable thickness. The weatherboard Material library has any given profile in multiple popular colours. There are around 5 common weatherboard profiles and 100+ popular exterior colours. I don't think we can reasonably use Classes to manage the attributes of 500+ weatherboard options alone. We have constructed an 'Applied Finishes' Materials library with about 150 popular and fashionable paint colours from a leading paint supplier. The Wall styles have a 0.1mm internal Component for the 'Applied finish'. The slab styles (for ceilings) have the same. The Wall Styles in our libraries have 'Natural White' associated with them, the ceilings have 'Ceiling White' associated with them. The Attributes of the other Wall and Slab components are still 'by Class'. We have a short list of (legacy?) Component Classes to control these attributes. It is a pleasure to use the Wall and Slab Styles straight from the library and to be able to simply swap out the Material with a preferred option (also straight from the library). I hear the comments about the absence of Class override type control for Materials, but for me the flatter workflow of simply applying a Material to an object is a far lesser evil than trying to do it with Classes. Considering the ease with which a model can be 'painted' in some other platforms, Materials are a welcome development.
  6. I would love to see the option to see larger thumbnail previews.
  7. Hi Dave, I take it the Beta will not run on 2021? As per the Enscape site "Download Enscape 2.7.1 to run Enscape with Vectorworks Service Pack 3 for free until October 2020". Is there a Partner Program to enable Vw Distributors to provide support? I've asked Phil Read via email...but you may already have something in place?
  8. I really enjoyed the presentation. It was candid and honest. I also appreciated the way Biplab addressed our current predicament in his opening address. Thank you Vw.
  9. @Vlado The file I received is .las. It is in MGA Zone55. The point cloud is over 5,000km from the IO. It doesn't display correctly unless it is centred on the IO on import (floating point errors I imagine). Of course centering scrubs the geolocation. Through some trickery we can firstly establish a lat/long of the center of the point cloud and then import a second time into a file with georeferencing already established. Only for the initiated though. We probably need the same 'this file contains georeferenced data' as per the .dwg/.dxf import dialogue? Mark Aceto - the .las file would supplement and be additional to other shapefiles and geodata.
  10. @Vlado Any thoughts to extend GIS support for point cloud files? They're starting to come in...
  11. Agree Tom, I was hoping Materials would rectify this...but unfortunately not. We need to be able to align a texture to a slab. For example a timber decking texture needs to be able to be turned to match a rotated section of decking.
  12. The Wall Data Cost Index System and Cost Index Code are mapped to ifc fields Classification.Name and Classification.Item Reference respectively. They don't import into Solibri - at least I can't find them in Solibri info palette Classification tab where I would expect to find them. Am I missing something here?
  13. I'm building a library of walls based on the popular CSR Redbook wall types for our Australian users of Vectorworks. How do I know which Classification I should use? Omniclass, Uniclass etc. or can they remain unclassified??? Any ideas or pointers will be helpful.
  14. @RG Architects Adrian, I take it you've seen the attached document 'Switching from SketchUp to Vectorworks'? Also downloadable here. xlth.pdf
  15. Thank you Zoomer et al., your answers help a lot...good to know there's really no way to improve the SU-VW transfer and the limitations are essentially with SU. In Australia a lot of VW architects are using SU for their conceptual modelling then VW for 2D drafting. We're trying to nudge them across to VW for the whole lot. I can see the attraction with SU...it's incredibly fast and the ability to apply a texture by face is very powerful. I'm investigating equivalent workflows in VW. So far the push/pull with sub face is as close as I'm getting to a SU like experience. But of course we produce solids this way and textures will be applied to the whole solid - not a face...so that's a fundamental difference/shortcoming. I'm interested in a continuous pathway in VW from concept solid modelling through to VW objects then (obviously) tech drawings. Using solids we can extract polygons (via the inner boundary - paint bucket) which we can then use to 'create objects from shapes' to walls, slabs etc. It's probably a conceptual ambition to work this way...and questionable as to whether it would be practicable...but it would be really good to get others thoughts and ideas on the matter.
  16. Hello Zoomer and other contributors, how do we force SU meshes to solids? Is it a fundamental shortcoming of the SU - VW workflow that SU objects come in as meshes? An architectural model imported as meshes would seem to have limited (if any) meaningful use in the VW environment...particularly if the model needs further development in VW. What do most people do in this situation?
  17. @Dave Donley Thank you for the responses. The new iPad didn't actually ship with iOS11. As soon as it installed it behaved. Very exciting new feature. I'll be showing it off at the trade show. Regards, Ben.
  18. Hi @Alex NicolBen here from OzCAD. Just got my hands on a new 10.5" iPad Pro. I don't get the option to view the model .vgx model in AR via the Nomad app. Any ideas?
×
×
  • Create New...