11/11/2022 0 Comments Moi3d tutorial![]() Then, I take the form the rest of the way using XSI’s poly tools. MoI creates a nice, workable mesh out of it, which I take into XSI via. (Sorry form*z folks, I don’t mean to jump all over your trademarks!) I can use MoI to quickly knock out a primary shape that would be tougher to make happen using poly tools. I sometimes use MoI in my XSI workflow as a “form synthesizer” of sorts. For example, when I use it, I don’t always assume a mesh is “final” inside of MoI. And, I think it’s really something that some users might undervalue. ![]() The tessellation is much better than you normally get when you export nurbs data from CAD products.Ībsolutely! MoI gets very high marks in this area. Example: IGES surfaces exported from MoI would come into Maya fine, but XSI didn’t deal with them well at all.Īnyway, I just wanted to add that to the discussion! Sometimes, the “problem” can be on the import side of things, which is out of the realm of control for MoI. You’d need to test it out with your other app to see what kinds of results you get. OBJ is probably the best export option when going into XSI, Max and Maya but LWO is there too, which I hear works well with Lightwave and Modo. It would be wonderful if MoI could “attach” tess settings to each object as an override to the global export option, which would make it easier to fine tune this stuff. Some trial and error is required and, as I mention in the review, it can be a good idea to export parts of a model individually, because sometimes the tessellation settings that work for one part, don’t work as well for another. (Kudos to Softimage for understanding this and creating “Crosswalk” for XSI.) MoI does create some very nice polygonal meshes, once you understand how the tessellation options work. (Though it does assume some understanding of NURBs in the terminologies it uses.)Īs far as output to another program goes, this is a very important consideration when using any stand-alone product in another workflow. The learning curve on MoI is also reduced because the program assumes no previously knowledge of the engineering terms and such common throughout the Rhino UI. MoI, on the other hand, seems more for those looking to create from inspiration, rather than engineering plan. ![]() Not that MoI is weak in areas of precision or that sort of thing–it’s definitely not–but I think Rhino is targeted more at those using CAD for larger scale projects. Though similar at their cores, I think Rhino and MoI are targeted at dramatically different audiences. (Thanks to redpandavfx for the kind comments!) I’m the guy who wrote that review, so I figured I’d pipe in. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |