Architect_073 Architect Special Interest Group July 2015 (am)

We looked at the Visibility tool, it is perfect for turning off the classes of unwanted information and it even works on classes of objects inside viewports (without entering the viewport). Holding down the V key will temporarily turn all the classes back on so you can see information that has been turned off.

We started to look at creating an office template. The issues around creating a template are the similar for a single person office and for a multi-person office. The big question os how much information should you include in the template and how much should you add to the default content (see the manual on creating your office library – 1407)? In this session we used the example of hatches (but the same issues still apply to all default content) and we looked at the options for storing hatches in the template file, a user library file, and in default content. Storing all the hatches in the the template file limits the access to the hatches to files created for the template. Storing the hatches in a user library will need extra steps to find and import the hatch or apply it to an object. Storing the hatch in the default content is faster, it works with all files, and it is consistent when it comes to assigning the hatch to an object.
We finished the session by looking at a texture that a user wanted to create from a photo. The photo an error that could be repaired in Photoshop (Lens Correction) and then we used photoshop to duplicate and bookmatch the image so that could texture correctly.
[ms-protect-content id=”34491,34492,34493, 34494, 34495, 34496, 344927″]
Architect 073 July 2015 am


Leave a Comment