Notifications
Clear all

[Closed] Adding Custom Columns to Scene Explorer Broken in 2013?

I don’t know how many people use this feature of the scene explorer but I’ve found it quite useful or at least I did until Max 2013. The code below used to work in Max 2012 but it causes an error in the scene explorer dialog in Max 2013.

fn getAnimHandle iNode =
(
	GetHandleByAnim iNode
)

fn getObjectMaterial iNode =
(
	if isProperty iNode #material and iNode.material != undefined then iNode.material.name as name else #None
)

SceneExplorerManager.AddReadOnlyProperty "Anim Handle" getAnimHandle
SceneExplorerManager.AddReadOnlyProperty "Material" getObjectMaterial

Does anyone know what I’m doing wrong?

3 Replies

I just came across something similar. I was just going through the MAXScript docs and tried pasting the example they provided into the Listener and evaluating it:


--Define a getter function which returns the class of 
the node
fn getClass theNode = (classof theNode)
--Add aRead-OnlyProperty 
filter to the Scene Explorer Manager
--which can only get properties but 
cannot set them
SceneExplorerManager.addReadOnlyProperty "Class" getClass

Upon trying to add the newly added “Class” column to the Scene Explorer, Max crashes.

The code snippet is from here:
http://docs.autodesk.com/3DSMAX/15/ENU/MAXScript-Help/files/GUID-21B47E09-1A2E-462E-AC79-2A64B4A2BB57.htm

Is there another method I should be trying?

1 Reply
(@raytracer05)
Joined: 11 months ago

Posts: 0

No I don’t think there is another way to do this. I looks like Autodesk have broken it in 2013. After I posted here I found another similar thread on The Area.

I confirm, still broken in PU6