Mz Instance Links documentation

3ds Max plugin · Version 0.9.21 · beta, being written

Getting started

Mz Instance Links links a BIM export (.fbx) into 3ds Max and replaces every instance type in it with a real 3D asset, or with a pool of assets. Revit’s grey block chair becomes one of five real chairs; a planting marker becomes one of eight trees. Re-import the .fbx and the replacements come back, on the same elements, unchanged.

This documentation is being written while the beta is prepared. It will grow with each release; see the changelog for what is new.

Requirements

  • 3ds Max: 2017 and newer
  • Input: an .fbx export from your BIM software (typically Revit)
  • Optional: Mz Asset Manager, used for merging assets when installed

The idea in four steps

  1. Export a furniture, planting or entourage view from your BIM software as .fbx.
  2. Link it into 3ds Max. Its instances are grouped by type.
  3. Pick an asset, or a pool of assets, for each type.
  4. Orient, fit and align it once; every instance of the type is placed.

Types

A type is recognised from the instance’s name. By default the BIM element id at the end of the name is removed, so these become one type each:

Inredning - Bord Matplats 800x800x720 [348920]   (Revit .fbx)
Chair_348920      Tree (12345)      Wall:9912     (other tools)

A typical Revit furniture export of 600 objects comes down to a few dozen types. If your names look different, each link can instead use the whole name, or the first fields split on a character you choose.

Mz Instance Links is a separate tool; neither needs the other. If you use both, export a category-filtered view from Revit (furniture, planting, entourage only) for Mz Instance Links, so it never overlaps the model Mz Link Manager brings in.

Installation

Mz Instance Links is distributed as a 3ds Max package. Installation instructions will be added here when the beta is released. Join the beta to get it as soon as it is ready.

Placing assets

The Instance types panel lists one row per type. Pick a row, pick an asset (from the scene or with the merge browser), and adjust how it sits. Every change re-places the type straight away.

The settings are listed in the order they are applied, so reading down the panel is reading what happens to the asset. Everything is measured in the BIM element’s own frame: “X” is always the element’s X.

1 Orient

Turn the asset in quarter turns about Z, mirror it in X or Y, or switch an asset modelled Y-up to Z-up. Use it when, say, an oven’s front faces the wrong way. The readout under Orient shows the element’s and the asset’s sizes side by side, and hints when the footprint looks swapped.

2 Fit

Match the element’s size on the axes you tick. Keep proportions turns this into one even scale that fits inside the element: tick only Z and a tree matches the height without being squashed.

3 Align

Works like 3ds Max’s Align tool, per axis: a point on the BIM element (min, centre, max or its pivot) and the point on the asset that goes onto it. A vase on a table is element Z max, asset Z min. Drop to surface lowers the asset onto the geometry below.

4 Adjust

Move, rotate and scale the asset after it has been fitted and aligned. Scale and rotation turn about the align point, so an asset aligned at its base grows from the floor.

5 Randomize

Random scale and random turn about Z, for natural variety. The random values are tied to each BIM element, so they are the same on every re-import (see Model updates).

Show or hide

  • Hide sources hides the BIM elements: with an asset set, that is a replacement. Leave them shown to place the asset alongside.
  • Hide placed hides the placed copies.
  • Hide asset hides the original asset the copies are made from.

All three are off on a new link, so it looks exactly like the .fbx that came in.

Mirroring inverts the asset’s normals; most renderers cope, some shaders do not.

Pools

A pool is a list of assets for a type. Each element of the type gets one member of the pool, chosen by weight: give a chair type five chairs and you get a mix of all five.

Instance types replaced from pools

The pool editor

Open it with Edit pool in the main panel, or from the pool helper’s Modify panel.

  • Members: the assets in the pool, with their weight. The list shows the resulting percentage of each.
  • Selected member(s): settings for the members you select, edited together.
  • Add from the scene: add selected objects as members.
  • Merge browser: merge assets from a .max file straight into the pool.

Every change re-places the types that use the pool.

Member settings

Each member can have its own turn, scale, rotation and offset, and its own random variation. They add to the type’s settings: a member’s turn adds to the type’s Orient turn, its scale multiplies the type’s Adjust scale, and its random values apply on top of the type’s Randomize. Use them for a member that faces another way or is modelled at another size.

Weights

Weights are relative. A member with weight 2 is picked twice as often as one with weight 1, whatever the others are.

Model updates

When the BIM model changes, export the .fbx again and re-import it.

What stays the same

  • Your settings stay on each type. They are matched by type name, not by position in the list, so types can be added or removed between exports.
  • Every element keeps its asset. Which pool member an element gets, and its random turn and scale, are worked out from the element’s BIM id. The same element always gets the same result.
  • New elements get new picks. Elements that were already there don’t move, so views the client has already approved stay approved.

Re-roll a type

Not happy with the mix? Re-roll a type to give its elements new picks and new random values. The other types don’t change.

Opening scenes

A scene with Mz Instance Links opens on any machine where the plugin is installed, even if nobody starts the manager there and even if the license has lapsed. The license is only needed to change links.

Something missing or unclear? Tell us, or see the changelog.