Architect Special Interest Group June 2016 (pm)

Architect_094_Jun_16_pm

In this session we looked at what information should be stored in a tempalte file and what should be stored in Default Content.

Topics Covered:

  • 0:00   What should be stored in a template file and what should be stored in a the default content
  • 00:50   There is no difference in speed to get a hatch from the active file rather that getting the hatch from the default content
  • 02:09   Some things have to be stored in the template file because they cannot be stored it the default content, such as dimension standards and tool preferences.
  • 02:40   Walls can be stored in the default content and managed in different folders and files, but you need to remove wall styles and files from the default content that are not required
  • 08:51   Saving classes in default content makes it easy to use standard classes – it makes class names and class settings consistent
  • 10:01   Storing your standard classes in default content
  • 16:38   Stories, Layers, and Levels should be stored in your template file, we also looked and an explanation of what these concepts are
  • 31:58   Where should details be stored? There could be a huge number of details for various projects with different cladding, internal linings, and foundations.
  • 33:45   Textures can be stored in the default content
  • 34:36   Custom Dimension standards should be sorted in the default content
  • 35:18   Using the Eyedropper tool to set up tool preferences, which can be saved in the template.

Architect June 2016 pm

There is some great protected information here that is only available to paying subscribers. You must be an active paying subscriber to see it, but you can  Subscribe here.

One thought on “Architect Special Interest Group June 2016 (pm)

Leave a Reply