Indeed, MOI has a very exotic UI ;) But when you get used to it, you soon realize that you can get incredible results in the shortest amount of time. I too use it in everyday production, mostly as a chamfering / filleting tool.
The one particular issue with it, is when your input files get too large - like 100 mb or so. Then it takes a significant amount of time to open them, although eventually they open up successfully. Never tried rhino though, a lot of people told me that it's a great tool.
Now to the normals issue. For me the same thing, NDA, can't show too much here unfortunately.
But i digged up one comparison. On the left is Alpha 0.72, with the broken normals issue. 1.00.01 produced the same result. Yesterday we finally bought our licenses, I will investigate further. Still, it's definetely a STEP-file issue, i rendered other PowerTranslator imports with Alpha 0.72 without any issues. Litttle spoiler: Vray renders the geometry without any issues ;). I am currently migrating my whole CAD animation workflow to Corona, it simply rocks - unbeatable in terms of tweaking time <> coffee breaks :)
CheerZ,
G.S.
Hi Gabriel,
Looks like the same issue I had here and I get it from either Solidworks, Rhino or Alias geometry:-
https://forum.corona-renderer.com/index.php/topic,6170.0.htmlIt is the bug/poly conversion issue that Ondra had stated.
The problem is two fold.
As Ondra first pointed out to me, the problem areas are where the conversion creates extremely elongated polys (seems always to be when resolving trim edges) so I believe the problem may be resolved with better mesh conversion.
But yes, somehow other software (and as you flagged the Alpha 0.6 version) is managing to resolve these nasty conversions at render time.
Inspired by ignicapillus's comment on Rhino's advanced mesh settings I went back and experimented, seem to have resolved some of my problem geometry, so thanks!