A mesh that seems to have vanished can interrupt a modeling session: you may need to inspect it, select it, or simply confirm that it is still part of the structure. Before changing anything, it helps to separate two tasks: finding mesh nodes and checking the visibility-related attributes they expose.
In SAMSON’s Node Specification Language (NSL), the mesh attribute space has the short name me and matches only mesh nodes. That makes me a useful starting point when you want a query to stay focused on meshes rather than other node types.
Start with a narrow query
To check for mesh nodes whose visible attribute is true, use:
|
1 |
me.v |
To query meshes whose visible attribute is false, negate the same condition:
|
1 |
not me.v |
These are useful companion queries: together, they let you inspect the two possible values listed for visible. If you are troubleshooting a particular object, keeping the query specific to meshes can make the result easier to interpret.
Don’t collapse similar-looking attributes
The mesh reference lists several visibility- and selection-related attributes: visible (v), hidden (h), visibilityFlag (vf), selected, and selectionFlag (sf). They are separate attributes in the reference, each with true and false as possible values. The page does not define them as interchangeable, so it is safer to query the attribute you actually want to inspect rather than assume one is a substitute for another.
For example, these expressions ask about different attributes:
me.vandnot me.v— thevisibleattribute.me.handnot me.h— thehiddenattribute.me.vfandme.vf false— thevisibilityFlagattribute.
This distinction is especially helpful when you are diagnosing an unexpected result. Check the exact property named in your question, and avoid drawing conclusions about another property unless its documentation explains their relationship.
Check selection separately
A mesh’s selection state is also distinct from its visibility attributes. You can query selected meshes with me.selected and unselected meshes with not me.selected. The reference notes that selected has no short name in the mesh attribute space, so use the full form rather than assuming that me.s is available.
If you specifically need to inspect the selection flag, the documented forms include me.sf and me.sf false. Keeping visibility and selection checks separate makes a useful troubleshooting sequence: first query the mesh’s visibility-related property, then check selection only if selection is relevant to what you are observing.
A practical query checklist
- Use
meto limit the query to mesh nodes. - Choose the precise attribute: for example,
v,h, orvf. - Use the documented true/false forms to inspect the state you care about.
- Check
me.selectedseparately if selection is part of the problem.
Mesh nodes also inherit other node attributes, including name, hasMaterial, and ownsMaterial. These can help you narrow a query when visibility alone does not identify the mesh you are looking for. For example, the reference shows name expressions such as me.n "A" and me.n "L*".
The key habit is simple: query one clearly named attribute at a time, and treat visibility, flags, and selection as distinct checks. For the complete attribute list and examples, see the SAMSON mesh attributes reference.
Note: SAMSON and all SAMSON Extensions are free for non-commercial use. Get SAMSON.
