KT exporter question to Avariant

Hi,
I have a question about your (amazing) plug-in:
do you know if there's some limitation about the mesh to be exported?

I explain: I spent the last hours trying to export a model that I "enriched" with greebles (maybe too much), and it's now a bit heavy to handle.
The exporter worked for 20 min or so on, till I decided to stop it and to re-do the job splitting the model in 3 and exporting each piece alone. The bad thing was that I had the materials repeated 3 times and I couldn't merge the new mesh on the last KT's xml as always (because material's name changed).

BTW I wanted to THANK YOU very much for your good work, because I'm able to use kerky only thanks to your plug-in.

PS: I'll soon post the render in the WIP section.

There is no specific limitation on exporters in Wings. However, unquestionably, large models take a long time to export. Part of that is undoubtedly the fault of the plugin, it's not really optimized for speed. The other part is Wings file format, at least I think so.
It's no secret that wings doesn't handle high polygon counts very well because it contains a lot of additional information that other modelers don't.

Anyway, I can try optimize the exporting for speed. There's no guarantees though. Erlang isn't my native language to say the least.

I could consider an option that exports mesh parts solely by the name of the mesh and / or material. That way KT could merge them or at least edit the materials together (the option "Apply settings to all models with the same name material")