Model Tree Levels and Mesh Areas - Acrobat X

You can set the visibility of mesh nodes with 3D JavaScript, but the properties do not inherit - you can't set a property for the top of a tree, you have to set it on every node individually. Usually we would do that by comparing the name of every node against a pattern or an array. Here's an example function from my 3D JavaScript Tech Talk you can use as a starting point:
.
.

// Sets visibility and render mode of all meshes, using a wildcard match
// either of the object itself or the object's parent
// eg partVisW("leg","wireframe",0) affects anything with "leg" in the name (leg1, myleg...)

function partStateW(_name, _state, _vis) {
var currMesh = null;
var nN = null;
var nP = null;
for (i=0; i -1) || (nN.indexOf(_name) > -1)) {
if (_state != "") currMesh.renderMode = _state;
if (_vis != 0) currMesh.visible = (_vis>0);
}
}
}


There is no scripting access to create new 3D views, only to select views from the existing array.

In terms of custom metadata associated with a node, you can inspect the node.metadataString and node.info strings, but they won't contain all the information you can see on the Model Tree.

Uvsar,
thanks for the quick reply!
It is great to know that I can handle the mesh nodes visibility. I am using the .visible property directly in a text field rather than the 3D context level function, and it works great!
For the node.info and node.metadataString I manage to identify the node but cannot extract any information on it. Is it possible that I loose the node information while exporting the 3d model? What kind of information will these two properties give me exactly?
many thanks!
cheers,
kiara

the .info and .metadataString properties are very rarely used - some third-party applications write to them when creating 3D PDF files but there's no real expectation of content from Acrobat.