It would seem that this is mostly geometry related. It also seems that it is an age issue as I have some Models that were created in Soft about 5 years ago and created no problems then but are demonstrating issues now. What's more bizarre is that one mesh has topology errors that I am certain did not exist back then. It literally boils down to a simple 64x64 square grid of quads that was generated from a loft and later converted to a mesh. There is an area of about 15 or so polys that are mangled, missing, and non-manifold, kind of like you see in some DWG to mesh conversions. But there is absolutely no apparent reason for it. I have other geometry that came over from Maya that was originally NURBS and a lot of older Viewpoint geometry as well. I see the problem a lot with those models. But that isn't what surprises me. It's the custom modeling created in Maya and Softimage about 5 years ago that really doesn't make sense. It's like the entire mesh database for any geometry that exhibits the problem is unstable. The minute you delete offending points, edges or polys the problem moves to a different part of the mesh. Its as if the geometry, when read by SI, was read wrong and mangled. You have to delete the entire mesh and recreate it. Just as you said, it's a lost cause. The only thing with these models that seems to be consistent is their age and the fact that they started existence as a NURBS model and at some point converted to mesh.
-- Joey Ponthieux LaRC Information Technology Enhanced Services (LITES) MYMIC Technical Services NASA Langley Research Center __________________________________________________ Opinions stated here-in are strictly those of the author and do not represent the opinions of NASA or any other party. > -----Original Message----- > From: softimage-boun...@listproc.autodesk.com [mailto:softimage- > boun...@listproc.autodesk.com] On Behalf Of Matt Lind > Sent: Friday, July 03, 2015 11:12 AM > To: softimage@listproc.autodesk.com > Subject: Re: ERROR : 2000 - Mesh structure error (corruption) > > 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]" <j.ponthi...@nasa.gov> > Subject: ERROR : 2000 - Mesh structure error (corruption) > To: "softimage@listproc.autodesk.com" > <softimage@listproc.autodesk.com> > > 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
