Hi Micha,
> Can you say, when v2 will be released - in days, weeks or months?
There isn't an exact fixed date yet, but it is probably something like 2 months from now.
> I remember me, that the reimported meshes was turned
> to the side allways - is it still so?
For OBJ files you mean? It may still be like this by default, but there is an option to choose the orientation for OBJ exports from MoI under Options > Import/Export > OBJ options / Orientation - you can choose between Z-Up and Y-Up.
If it is turned in the wrong direction for you, just flip that setting and it should be solved.
> Could it be possible that the imported mesh is placed
> at the original NURBS layer?
It doesn't do this currently, but this area of layer management is one of the main areas that I have left to work on to complete v2. However, I'm not quite sure if there is a way for Rhino to create layers from an OBJ file so this may not be very easy to resolve right away.
> An other idea: could it be possible that you open MOI3D
> for plugin developer, so that a plugin could be written
> by a Rhino plugin developer?
Yup, I am planning on doing this eventually. Unfortunately both documenting a plug-in system and also supporting other programmers who are using it tends to be a very time consuming area of work, so it is not easy for me to add this in currently while I still have a lot of other more basic areas that I am also working on. So it will probably be a while yet before I am able to focus much effort in this area.
I tend to have to be careful right now about entering areas of work that will consume a large amount of support time.
> I think on that the moi3D can be used per command line
> like "moi3d.exe -parameters original.3dm mesh.obj". Sounds
> quite easy for me, but I don't much about programing. ;)
Actually this type of automated command-line meshing is already possible, you can give MoI the name of a .js script file on the command line and the script file can call various functions to produce the meshed output also passing parameters such as angle, etc...
Some details on that here:
http://kyticka.webzdarma.cz/3d/moi/#Batch
Also another discussion here on how to use this mechanism to batch convert all files that can be found in a particular folder:
http://moi3d.com/forum/index.php?webtag=MOI&msg=2100.1
So I guess that actually already provides the basic stuff that you would need to make a Rhino plugin that would call moi.exe to do the meshing... The plugin would basically need to create a temporary .3dm file, and a temporary .js file with some calls in it to control what MoI does - it would call some script functions to load that .3dm file and then do a SaveAs to a polygon file (details on this are in the links above), this can either allow the UI to show or it can decide to have the UI hidden and pass specific parameters in. Then the plugin would wait until that moi.exe program ended and it would then be able to load in the generated mesh file.
> Doe's the current mesher support the option
> "max distance/error NURBS to mesh"? If not, is it planed?
There is not currently a "maximum chord height" type option, but I have been planning on adding one.
- Michael