The macro works only on the trimesh, through meshOp methods: theObj = selection[1].mesh The whole topology check is based on that. It also makes an ex…

BINGO! The compile error is gone! And also the other problem with the double drop (?!). Thanks a ton Denis. Especially for insisting and keeping up w…

Thanks for that, Denis. I’ve sent a new .mzp with your corrections both in install.ms and in the macro to one of the guys with the error. I first tri…

I’ll have the test done later tonight so won’t post the result before tomorrow. In the meantime to answer your question, let me put it this way. How …

I had that test in earlier versions (though in the form of testing the class of modPanel.getCurrentObject()) and the error was already there. I remove…

Denis, are you pulling my leg?

If you copy the macro and run it without having an object selected with an unwrap on it, you get an error. Try it. The menuMan part is not the issue s…

It’s the exact same file than the one I’ve attached. Nothing’s encrypted.

Nope. Setting the default heap size higher didn’t solve the problem. Any other idea, people? And how about the 1st problem, the need to drop the .mz…

I will definitely try that (I’m ready to try anything at his point)! Thanks Io. But shouldn’t the error be ‘out of memory’ or something similar, intea…

Denis, I’m not sure I’m following. If it’s the first evaluation of the macro (during installation), install.ms does just that: it creates a temporary…

That’s not a problem. Since the macro is run from the mapping menu in the Edit UVWs dialog, the current modifier cannot not be an unwrap uvw modifier….

I use the unwrap methods. I started first by using the meshop methods for testing the topology, retrieving the coordinates, etc, and only the setVerte…