The Softimage error is generally not that helpful. On these types of issues
run mental ray in full diagnostics mode to get a more verbose explanation.
mental ray will be more explicit and make it clear what the real problem is.
Just be prepared to possibly deal with object ID's instead of object names
to figure out the offending element(s).
If it's a geometry issue, I find it's best to freeze geometry construction
history as part of the solution as those types of corruptions usually come
about because one or more operators lose sync with the stack. for example,
if you have a custom plugin used by a scene object to delete polygons and
that plugin somehow no longer becomes accessible (forgot to install on the
computer doing the rendering, for example) it will have a ripple effect up
the stack as the latter operators will expect subcomponent IDs to be ordered
a specific way but won't be because the custom operator is not accessible to
do that work. Freezing the stack will take the operator out of the
equation. If the geometry issue still exists on said object, then the
integrity of the object has likely been corrupted at a level deeper than you
can access, in which case that object is a lost cause and will need to be
replaced.
Matt
Date: Wed, 1 Jul 2015 15:22:39 +0000
From: "Ponthieux, Joseph G. (LARC-E1A)[LITES]" <[email protected]>
Subject: ERROR : 2000 - Mesh structure error (corruption)
To: "[email protected]"
<[email protected]>
Has anyone found anything relevant to this error?
I read a scene and it reports this along with corrupted edge or vertex and
poly. I delete the geometry in one model then save and upon rereading it
appears again in another model.
Has anyone had issues with this?
--
Joey Ponthieux
LaRC Information Technology Enhanced Services (LITES)
MYMIC Technical Services
NASA Langley Research Center
