9

Blocks 459
3ds Max, see the Material Editor , Materials, and
Maps (page 2–1395) topic.
Multi-V iew B lock s (MV B lock s)
3ds Max accommodates both AutoCAD blocks
and Autodesk Architectural Desktop multi-view
blocks through the file linking functionality, and
for the most part the two block types behave
similarly in 3ds Max with some exceptions.
The structure of Architectural Desktop multi-view
blocks is expressed differently in 3ds Max, when
compared to AutoCAD blocks. Rather than peer
into the internal structures of multi-v iew blocks
as is done with AutoCAD blocks, 3ds Max relies
on the multi-view block’s own ability to draw its
own 3D v iew, much as it does in the A rchitectural
Desktop Object Viewer. Because of this, you w ill
notice that multi-view blocks never exhibit nesting
in their object structu re when they are file linked
into 3ds Max.
Behavior of instanced Architectural Desktop
multi-viewobjectsisdifferentfromthatof
AutoCADblocksaswell. Multipleinstances
of multi-view blocks require m ore memory in
3ds Max than multiple instances of AutoCAD
blocks. But multiple instances of multi-view
blocks are b etter behaved when being cut by live
sect ion objects than t heir AutoCAD counter p arts.
Dynamic B locks
The File Link Manager handles dy namic blocks
the same way as other blocks found in a DWG
file. When linked to a scene, the naming for the
incoming dynamic block instances are based on
the original dynamic block definition in the form
of Block: block_name where block_name is the
actual name of the dynamic block definition.
Dynamic block instances, even those that have
been grip-edited, display cer tain types of instance
behav ior such as material propagation, if the
setting is act ivated from the Material Editor
Options menu (page 2–1428).Belowisatable
showing instance b ehavior of dynamic blo cks.
Proper t y
Behavior
Modifiers Modifiers applied to one component are
applied to the same component in other
instances, but only when those instances
havethesamegrippropertyvalues.
Materials When material propagation is turned
on, mater ials are applied to all block
instances. When turned off, materials are
applied only to the current selection set.
Note:
If you use the Entity,BlocksasNode
Hierarchy Derive By setting for draw ings
containing dynamic blocks, materials may
propagate to some block instances and not
to others.
Node
Properties
Changestonodepropertiesarenot
propagated to block instances.
Transforms (on
components)
Transforms, lik e move, rotate and scale,
of one component will affect that same
component in other block instance only
when those i nstances have the same grip
property values.
Keep in mind that elements of a dynamic block
canbeturnedonandoffbycertaingrip-edit
operations depending on the way the dynamic
block is defined. When one instance has a
component and another doesn’t, instance
behaviors cannot o ccur between them because
they are treated as instances of one another.
Modifier behavior of Dynamic Blocks during a
File Link R eload
There is no change in modifier behavior for
dynamic blocks that have not been grip-edited
between one Reload and the next. All properties
(materials, modifiers, node properties) are
preserved. Dynamic blocks that have been
grip-edited preserve their node name, node
properties, scene-applied transform, and
materials, but may lose applied modifiers and/or
may inherit modifiers. This table shows the