Unhandled exception exporting animation with version 1.8

I have a model using Physique and when I try to export it using the latest oFusion CE version I get an unhanled exception message from the exporter and the mesh reverts to its non-weighted form (undoing can't revert the effect). The same happens when I activate the oFusion viewport.

The exact same model works perfectly fine with version 1.6.

You can download the max file if you want to run some tests form this link: http://www.oniricgames.com/Extra/Soldie ... 20Walk.max

[UPDATE] I erased the biped and the Physique modifier and started from scratch (new biped, new modifier) and now it exported without errors...

Apparently, it's not as easy as that... It depends on how you assign the vertices. With some assignments it works just fine, but with others it doesn't.

Any clues?

Could you provide more details on "With some assignments it works just fine, but with others it doesn't", what exactly are the results with the different vertex assigments?

Actually this is the same problem i'm having.
Instead of changing the size of the envelopes in the physique rollout, I assign vertices to an especific bone.
The difference is that I've always had the same result (failure), so I don't know what should I change

---EDIT---

I've solved the problem !!

This exception occurs when vertices are assigned to bones, but they are actually outside envelope.
In my post I had an issue with a Troll who held a club in his arm. What I've been doing is to assing the club vertices to his bone hand. Now, instead of doing that, I enlarged the outer envelope until it covered the whole club.
Exported it, and voila

Could you provide more details on "With some assignments it works just fine, but with others it doesn't", what exactly are the results with the different vertex assigments?

With some assignmets it exports the file and with others it gives the unhandled exception error.

I enlarged the outer envelope until it covered the whole club. Exported it, and voila

Thanks for the tip, Ridhan!
However, this is more a workaround than a solution...

Of course, but what can I do beside that

Just paciently wait Lioric for a complete solution

@Lioric:

Did you manage to take a look at the file I uploaded? Any news regarding this problem?

I will review it in the next hours