Hi Burr,
> (a. can this be a particular setting/setup issue with my rhino to make it match what MoI has written?
No there isn't any kind of settings or setup type things that I am aware of that would have any effect on this.
> (b. Could just be rhinos system has an issue with how I have defined and created these surfaces?
Well, it depends on the particular case - Rhino flags an object as "bad" if it the Rhino check function complains about something in the model structure. Not all of these complaints are equal in severity, some are easily ignored and others can be more significant problems.
A whole bunch of them in your case here, those rope ties, just have some very slightly wrong flag on one trimming curve: "ON_Brep.m_T[11].m_type = ON_BrepTrim::seam but m_iso is not N/E/W/S_is" - means something like the edge has a flag indicating it's a seam of a closed surface but another flag on it is not set saying that it's an isoparm curve like it should probably be. It's unlikely that will cause you any actual problem.
I don't know why that particular trim flag is not set, it could be a bug in MoI's exporter or it could be a bug in the OpenNURBS 3DM writing library that MoI uses to write 3DM files, it would unfortunately take a lot of investigation work to find out more about it.
For those particular errors it's probably best to just ignore them, it's kind of more likely that you will end up with worse results on those doing a STEP import instead because that will involve a lot of recalculation of data - basically all the UV trim curves will be thrown out and they will all be recalculated by pulling down the 3D edge curves onto the surface. That's a lot of stuff happening just to get a single not really very meaningful edge flag to get set...
> 2. Is this just a function of data exchange?
Yeah I guess so - different programs can be finicky about different particular things.
> Maybe you could speak just a little as to “why those particular objects are “bad” in rhino, though just a mirrored part from the MoI file?
Well, by definition they're bad because they don't pass the "Check" function. You can get the specific error by selecting the particular object and running the Check command on it.
> 3. would trying to export more “single items” help, as opposed to a “319 solid” file export….
I wouldn't think it would make any difference...
To me it makes more sense to look at the specific problems that Check reports.
Not sure if that helps you any... ?
- Michael
|