Hi blackhoney - importing mesh objects tends to bring about a large cascade of various UI issues, since they have a much different structure than NURBS objects, so it is difficult to have the existing toolset work directly on them (stuff like booleans, trimming, etc...).

That leads to a situations where you could open an file, and see that it appeared to open correctly, but then not have any of the regular tools work on it. That can tend to cause significant confusion - people think: hey this file seems to have loaded ok but now why does it not behave normally, is it a bug?

So I'm still not sure at this point about implementing that in a near time frame - it still needs more thought about how it could be implemented without leading to that kind of confusion about not being able to do regular modeling actions on the imported data.

It's hard to give a time frame on issues that may need to have a good UI design around them to prevent confusion. That could pretty easily not fit in to the v3 time frame.

In addition to this issue, just implementing importers in general tends to be a fairly time consuming area of work so that's an additional complication.

- Michael