[jvanmetre]

JD-

Hi...things have been going along pretty smoothly until this...started getting
an error message this afternoon. The message is "This mxs is obsolete or has been corrupted"

Rhino meshes the scene to 90.1% completion and the last 9.9% is a struggle. Studio does launch but the error message is immediate. None of the objects in the Rhino scene appear in studio.

jvm

[JDHill]

To be honest, you have as much chance of knowing what would cause it as I do - but if that happened to me, I would:

a) re-mesh the objects in the scene using slightly different parameters
b) check that I don't have some non-displayable rogue mesh that goes off into outer space
c) check that I don't have any microscopic trim fragments laying around
d) run the Maxwell_CheckFixAndReportBadGeometry command to see if that can find anything

If none of that was getting me anywhere (or maybe even before I tried those things), I'd start wolf-fencing the problem, i.e.:

a) select some objects, then Maxwell_Render > RenderSelectedObjects (right-click toolbar Render button)
b) if this is successful, use the Hide command and repeat with another set of objects
c) do this until you find what's causing the failure

I'd start with things that I'm pretty sure are good, since they were working before. I can usually narrow down any problem in a couple of minutes using this technique. I'm pretty sure you've got some bad mesh in the scene just by your 'the last 9.9% is a struggle' comment - at that point I'm going to be expecting to find some junk mesh that's about the size of the milky-way and is being ignored by the Rhino display system.

[jvanmetre]

JD-

Thanks for the reply...I've been going back through earlier saved files.

Something that seems to have happened is that objects that were polysurfaces and exploded earlier in my work have now come back as polysurfaces after saving them in a newer file -- I think it's causing some type of conflict. What should be coming in are single surfaces and not polysurfaces.

Jim

[jvanmetre]

Further, I've found out that when I open a file in which I have saved the objects as single surface (not polysurfaces) that if I then need to copy them as a group of single surfaces, both the original and copy automatically become polysurfaces -- this is causing a conflict with meshing. If you explode the new polysurfaces it seemingly still doesn't correct the problem.

jvm

[JDHill]

That sounds like an interesting problem, but I'm unable to duplicate it. Can you boil it down to a very simple example, say, create a cube, explode it, copy it, and it becomes a polysurface again? Because I haven't yet observed what you're referring to.

Thanks...

[jvanmetre]

JD-

I think the main issue is hardware related -- I've essentially been duplicating mxs with pack and go and I've managed to completely fill an external drive which appears to have caused the "corrupt mxs" error message. Go figure, lots of mxs files = less disk space!

The other issue of saving files with exploded surfaces and then reopening to find them as polysurfaces I'm still trying to figure that out...

jvm