3ds Max Scene Explorer Guide: Creating Custom Columns with MAXScript

Autodesk’s MAXScript documentation explains how to manage Scene Explorer with scripts using the SceneExplorerManager interface and how to create custom columns. Based on the official documentation, this guide covers creating an Explorer in 3ds Max scenes, choosing visible columns, displaying object properties as columns, and reusing configurations. The SceneExplorerManager interface is available in 3ds Max 2008 and later, but some methods require newer versions.

The code examples below are based on the MAXScript methods shown in Autodesk’s documentation. Before running any script in a production scene, check that the target version of 3ds Max supports the method and that the column names match properties in the scene.

1. Check version support and identify what you need

First, determine what you want to automate: setting up an existing column layout, making object properties visible, or saving and reloading an Explorer configuration. The methods have different version requirements. For example, CreateExplorer and SetExplorerVisibleColumns are documented for 3ds Max 2010 and later. GetExplorer is available in 3ds Max 2015 and later.

The availability of the SceneExplorerManager interface does not mean that every method in it will work in older versions. For methods whose version requirements are not explicitly stated in the documentation, no additional version limit should be assumed here. That’s why it’s important to test team scripts in the target versions before using them across different 3ds Max installations.

2. Create an Explorer and set its visible columns

1. Use CreateADefaultExplorer to create an Explorer with the default settings. The method returns True if successful and False if it fails.

2. Then use SetExplorerVisibleColumns to specify the columns to display as an array of names. In Autodesk’s example, the “Object Colors” Explorer is set to show the name, type, and color columns.

3. To create a new Explorer with specific columns, use CreateExplorer. This method takes the Explorer name and an array of column names; do not assume it creates an Explorer with the default settings.

SceneExplorerManager.CreateADefaultExplorer "Object Colors"
SceneExplorerManager.SetExplorerVisibleColumns "Object Colors" #("Name","Type","Color")

SceneExplorerManager.CreateExplorer "Geometry Counts" #("Name","Type","Faces")

The values below appear in Autodesk’s examples. They aren’t a required layout for every scene, but examples of how to use the methods.

If a name in the column array doesn’t match an existing column filter, that column may be skipped without an error. For this reason, check that the expected columns actually appear. The documentation gives an example of using a name such as “Bananas” if it has been defined as a filter; if no such custom filter exists, the column won’t be added.

3. Turn custom properties into Scene Explorer columns

You can define a column filter with addProperty to make a property on scene objects visible. The method takes a property name, a function that reads its value, and a function that sets it. In Autodesk’s example, if an object has a Radius property, the value can be read and updated.

Use an isProperty check when the property may not exist on every object. The example below accesses the Radius value only if the object has that property:

fn getRad theNode = (
    if isProperty theNode "Radius" then theNode.Radius
)

fn setRad theNode theValue = (
    if isProperty theNode "Radius" then theNode.Radius = theValue
)

SceneExplorerManager.addProperty "Radius" getRad setRad

If you only need to display information and don’t want values changed through Explorer, use addReadOnlyProperty. The example in the documentation creates a read-only filter called “Class” by returning the object’s class with classof:

fn getClass theNode = (classof theNode)
SceneExplorerManager.addReadOnlyProperty "Class" getClass

After you define a new filter, its column appears at the end of the Column Chooser list. Drag it from the list into Scene Explorer to add it. Defining a custom column doesn’t automatically add it to the visible column layout, so complete the filter definition and the step to display it in Explorer separately.

4. Save and manage Explorer configurations

You can save an Explorer configuration to a specified file with SaveExplorerConfiguration and load a previously saved configuration with LoadExplorerConfiguration. In the example below, update the file path to match the working setup on the relevant computer:

SceneExplorerManager.SaveExplorerConfiguration "Geometry Counts" "C:\\SceneExplorerConfig"
SceneExplorerManager.LoadExplorerConfiguration "C:\\SceneExplorerConfig"

Use OpenExplorer and CloseExplorer to open or close an Explorer. ExplorerExists checks whether an Explorer with the specified name exists; ExplorerIsOpen checks whether it’s open. GetExplorer returns the interface for an Explorer with the given name, or undefined if no such Explorer exists.

To make custom property filters available in later 3ds Max sessions, you can save their definitions in a script file and place it in the Scripts\Startup folder. To list multiple Explorers, GetExplorerCount returns the total number, while GetExplorerName returns a name for indices from 1 to that number. ClearAllExplorers closes all Explorers and clears the Tools>Saved Scene Explorers> menu list. Don’t use it when you intend to work with just one Explorer.

Using Scene Explorer in architecture and archviz workflows

In architectural and visualization scenes, reviewing object information in one window can help teams set up an Explorer view that fits their workflow. Columns such as name, type, color, and face count—the examples in the documentation—are a starting point. If a custom property on scene objects is important, it can also be defined as a separate column. The benefits of this approach depend on how well the data and filters match the needs of the scene.

Before sharing scripts across offices, verify the 3ds Max versions in use and the object properties that the custom filters rely on. In scenes with multiple object types, adding a property check helps avoid trying to read a value that isn’t present. Autodesk’s documentation doesn’t provide information about hardware, licensing, or product costs, so no additional requirements in these areas should be assumed.

Common mistakes

• Adding a filter name that doesn’t exist to the visible columns list: The column may be skipped without an error.

• Expecting a custom column to appear automatically after defining it: It must be dragged from the Column Chooser into Scene Explorer.

• Assuming every object has the same property: You can check with isProperty before accessing it.

• Expecting GetExplorer to always return an Explorer: If no matching name is found, the result is undefined.

• Using ClearAllExplorers to close just one Explorer: The method closes all Explorers and clears the saved menu list.