Oh Michael, please don't take any of what I wrote as a slight!
I'm a super enthusiastic evangelist for MOI wherever I get an ear that hasn't heard it already. I do also use it extensively for modelling the "simpler" stuff (deceptive terminology there as it's FAR more preferable than any parametric modeler I've ever come across, even for very intricate work).
As to conversion stuff: my workflow when I get the enormous data sets in is generally to explode them as much as necessary in Rhino and then bring them into MOI as parts (working individually, save and load the next part etc). I do a lot of Previs and marketing stuff though, so ultimately it ends up in Maya, which is where the other side of MOI comes in. As I've mentioned before there's NOTHING on the market comparable to MOI's poly conversion algorithms. Rhino's mesh output is laughably bad, MOI's is perfect. I can't overstate that. MOI's poly output is PERFECT.
Danny - thank you for the words there, much appreciated. Unfortunately it's ME putting in the threads etc where nescessary ;)
The engineers just leave annotations for that kind of thing because even they're not that mad ;). Again, MOI enables me to put that stuff in with ease, though of course in isolation. The close-up zooms of a lot of the stuff I do needs to be accurate for the photo-real side of things.
Again, I have no complaints about MOI. I honestly don't know if I'd take on some of the jobs I do without it.
I was just trying to bolster the enthusiasm for a 64bit version ( if it was genuinely being considered.)
:) /Rico
|